From: Ingo Molnar <mingo@elte.hu>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] kmemcheck updates for tip/kmemcheck
Date: Sat, 6 Sep 2008 19:16:54 +0200 [thread overview]
Message-ID: <20080906171646.GI4856@elte.hu> (raw)
In-Reply-To: <20080829211921.GA1135@localhost.localdomain>
* Vegard Nossum <vegard.nossum@gmail.com> wrote:
> Hi Ingo,
>
> A rather large update, most of it is implementing the correct REP
> MOVS/STOS handling on P4s. I've tested it on both 32-bit and 64-bit
> and everything seems good! Also included is the DMA API hooks which
> prevents false-positive reports from reads in DMA-able memory.
pulled, thanks Vegard. Great progress on a rather difficult aspect of
kmemcheck!
Ingo
next prev parent reply other threads:[~2008-09-06 17:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-29 21:19 [GIT PULL] kmemcheck updates for tip/kmemcheck Vegard Nossum
2008-09-06 17:16 ` Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-09-07 20:09 Vegard Nossum
2008-09-08 15:17 ` Ingo Molnar
2008-09-08 15:24 ` Vegard Nossum
2008-09-08 15:26 ` Vegard Nossum
2008-09-08 17:08 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080906171646.GI4856@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=vegard.nossum@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox