Re: [PATCH 1/6] base: Valgrind headers and Kconfig

From: Jeff Dike
Date: Mon Sep 01 2008 - 11:48:35 EST


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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/