[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e2e108260805100404h63f02194r62e53f79ae2a403f@mail.gmail.com>
Date: Sat, 10 May 2008 13:04:03 +0200
From: "Bart Van Assche" <bart.vanassche@...il.com>
To: "Pekka Enberg" <penberg@...helsinki.fi>
Cc: "Vegard Nossum" <vegard.nossum@...il.com>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
"Ingo Molnar" <mingo@...e.hu>,
"Peter Zijlstra" <a.p.zijlstra@...llo.nl>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
"Christoph Lameter" <clameter@....com>,
"Daniel Walker" <dwalker@...sta.com>,
"Andi Kleen" <andi@...stfloor.org>,
"Randy Dunlap" <randy.dunlap@...cle.com>,
"Josh Aune" <luken@...er.org>, "Pekka Paalanen" <pq@....fi>
Subject: Re: [ANNOUNCE] kmemcheck v7
On Sat, May 10, 2008 at 11:06 AM, Pekka Enberg <penberg@...helsinki.fi> wrote:
> Bart Van Assche wrote:
>>
>> It's a bit late but I finally found out about your announcement of
>> kmemcheck version 7. Are you familiar with the patch that adds support
>> to Valgrind for User Mode Linux ? I'm not sure what the best approach
>> is -- letting the kernel do its own checking like kmemcheck or extend
>> Valgrind such that it supports UML. Anyway, the techniques applied in
>> Valgrind may be useful for kmemcheck too, such as the algorithms used
>> in Valgrind to compress the memory state information.
>
> It's better to do it with the native kernel so you can "valgrind" all the
> interesting driver code.
That's right. This is the paper I was referring to that details how to
minimize the memory consumption when tracking state information:
http://www.valgrind.org/docs/shadow-memory2007.pdf
Bart.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists