From: Andi Kleen <andi@firstfloor.org>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: Andi Kleen <andi@firstfloor.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Richard Knutsson <ricknu-0@student.ltu.se>,
Christoph Lameter <clameter@sgi.com>
Subject: Re: [PATCH 1/2] kmemcheck v3
Date: Fri, 8 Feb 2008 14:20:32 +0100 [thread overview]
Message-ID: <20080208132032.GA6115@one.firstfloor.org> (raw)
In-Reply-To: <19f34abd0802080418o75969480v3286da7a83ebc178@mail.gmail.com>
On Fri, Feb 08, 2008 at 01:18:37PM +0100, Vegard Nossum wrote:
> On 2/8/08, Andi Kleen <andi@firstfloor.org> wrote:
> > Your assumption that only the string instructions can take
> > multiple page faults seems a little dangerous too.
>
> Yes, this is true. I cannot guarantee that there are no other
> instructions that could access more than one memory location but only
> take one page fault. However, since the kernel does boot, we at least
> know that these instructions are not very frequently used. (If you
> know of any other instructions we might be missing, I'll be happy to
> know about it!)
Pretty much all in the right circumstances.
e.g. consider a segment reload in tracked memory.
Also there are various instructions which do all kinds of complicated
things internally; like IRET or INT: often with many memory accesses.
Just page through a instruction manual and look at the pseudo code
describing what the various instructions do.
>
> There is also the point that if kmemcheck doesn't handle all the
> faulting addresses, it will simply fault again and again, without
> making any progress. I mean, it won't go unnoticed for very long :-)
>
> This is also why we depend on M386 and !X86_GENERIC, to avoid those
> MMX, etc. instructions, as we have no support for those currently
I would not expect problems from MMX/SSE here (except for the generic
ones all instructions have)
-Andi
next prev parent reply other threads:[~2008-02-08 12:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 21:36 [PATCH 1/2] kmemcheck v3 Vegard Nossum
2008-02-07 21:39 ` [PATCH 2/2] " Vegard Nossum
2008-02-07 21:53 ` [PATCH 1/2] " Christoph Lameter
2008-02-07 22:12 ` Vegard Nossum
2008-02-07 22:53 ` Christoph Lameter
2008-02-07 23:18 ` Vegard Nossum
2008-02-07 23:32 ` Christoph Lameter
2008-02-08 6:40 ` Pekka Enberg
2008-02-08 8:09 ` Ingo Molnar
2008-02-08 6:30 ` Pekka Enberg
2008-02-08 6:33 ` Pekka Enberg
2008-02-08 7:10 ` Christoph Lameter
2008-02-08 7:48 ` Pekka Enberg
2008-02-08 11:55 ` Andi Kleen
2008-02-08 11:31 ` Pekka Enberg
2008-02-08 12:10 ` Andi Kleen
2008-02-08 11:39 ` Pekka Enberg
2008-02-08 11:37 ` Pekka Enberg
2008-02-08 12:15 ` Andi Kleen
2008-02-08 11:43 ` Pekka Enberg
2008-02-08 12:18 ` Vegard Nossum
2008-02-08 13:20 ` Andi Kleen [this message]
2008-02-08 12:59 ` Vegard Nossum
2008-02-08 13:48 ` Andi Kleen
2008-02-09 9:33 ` 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=20080208132032.GA6115@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=ricknu-0@student.ltu.se \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.