From: Andi Kleen <andi@firstfloor.org>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
Arjan van de Ven <arjan@linux.intel.com>
Subject: Re: [PATCH] kmemcheck: support for x86_64
Date: Sun, 18 May 2008 12:17:44 +0200 [thread overview]
Message-ID: <48300248.7050701@firstfloor.org> (raw)
In-Reply-To: <20080517230458.GA18588@damson.getinternet.no>
> Most of them look something like this:
>
> kmemcheck: Caught 8-bit read from freed memory (ffff81000780a904)
> ifffffffifffffffifffffffifffffffifffffffifffffffifffffffifffffff
> ^
>
> and my theory so far is that X86_64 uses some currently unhandled
> instruction set extensions like MMX, SSE, etc. (Not 3DNow! because we
> have a dependency for that), for a fairly common operation
No it shouldn't. Only SSE users are in the (broken) MD RAID code
Most likely you don't decode REX correctly in some cases.
[haven't read the patch sorry]
=Andi
next prev parent reply other threads:[~2008-05-18 10:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-17 23:04 [PATCH] kmemcheck: support for x86_64 Vegard Nossum
2008-05-18 10:17 ` Andi Kleen [this message]
2008-05-18 11:31 ` Vegard Nossum
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=48300248.7050701@firstfloor.org \
--to=andi@firstfloor.org \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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