Messages in this thread | | | Date | Mon, 1 Sep 2008 11:47:43 -0400 | From | Jeff Dike <> | Subject | Re: [PATCH 1/6] base: Valgrind headers and Kconfig |
| |
On Mon, Sep 01, 2008 at 04:22:19PM +0200, Andi Kleen wrote: > > Kernel code can't get headers from the system, unless you're thinking > > #include "/usr/include/valgrind.h" > > or something similar. > > Some um files at least least include sys/* files which are surely > user space? If they can include that why not valgrind.h?
The userspace side of UML can (and, indeed must) use the system headers. Here, we can just #include <valgrind.h>.
However, the kernel side of UML, where the allocator annotations are, can't use system headers. The kernel side of things has to be self-contained within the kernel tree.
Jeff
-- Work email - jdike at linux dot intel dot com
| |