* Andi Kleen <andi@firstfloor.org> wrote:
quoted text > > Yes, this is true. Then our task is to make sure that this memory is
> > never allocated from tracked caches. We do have some changes in this
> > area, for instance we never track task structs. Keep in mind that
> > only slab objects are tracked currently, so things like stacks never
> > catch page faults. I am not sure if this is exactly what you had in
> > mind, but I don't know other kernel code very well enough to come up
> > with perhaps more relevant examples :-)
>
> Given that you don't seem to handle networking yet I wonder how many
> cases you really tested so far.
you are wrong about no networking support: i have booted up a full
distro config on real hardware with full networking, etc.
Ingo
--
unsubscribe notice To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
majordomo@vger.kernel.org
More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
http://www.tux.org/lkml/
Messages in current thread:
Re: [PATCH 1/2] kmemcheck v3 , Ingo Molnar , (Sat Feb 9, 5:33 am)