linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vegard Nossum <vegard.nossum@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Ingo Molnar <mingo@elte.hu>,
	Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: [PATCH] kmemcheck: disable fast string operations on P4 CPUs
Date: Sun, 22 Feb 2009 11:51:33 +0100	[thread overview]
Message-ID: <19f34abd0902220251w4ec0485bp3eaa6092c60447a6@mail.gmail.com> (raw)
In-Reply-To: <49A0C2D4.20009@zytor.com>

2009/2/22 H. Peter Anvin <hpa@zytor.com>:
> Vegard Nossum wrote:
>> This patch may allow us to remove the REP emulation code from
>> kmemcheck.
>
>> +#ifdef CONFIG_KMEMCHECK
>> +     /*
>> +      * P4s have a "fast strings" feature which causes single-
>> +      * stepping REP instructions to only generate a #DB on
>> +      * cache-line boundaries.
>> +      *
>> +      * Ingo Molnar reported a Pentium D (model 6) and a Xeon
>> +      * (model 2) with the same problem.
>> +      */
>> +     if (c->x86 == 15) {
>
> If this is supposed to refer to the Intel P4 core, you should exclude
> the post-P4 cores that also have x86 == 15 (e.g. Core 2 and Core i7).
> If those are affected, too, they should be mentioned in the comment.

Thanks for the review!

This is supposed to happen only for those machines where the "fast
string ops" is enabled by default.

We have a test for that in the part that you snipped -- and since the
MSR is architectural, I believe it would exist (i.e. not cause an
error if we read it, but just be cleared by default or hard-wired to
clear) on those post-P4 cores you mentioned too?


Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2009-02-22 10:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-21 13:36 Vegard Nossum
2009-02-21 13:36 ` [PATCH] kmemcheck: disable fast string operations on P4 CPUs Vegard Nossum
2009-02-21 16:21   ` Pekka Enberg
2009-02-22  3:13   ` H. Peter Anvin
2009-02-22 10:51     ` Vegard Nossum [this message]
2009-02-21 13:36 ` [PATCH] kmemcheck: rip out REP instruction emulation Vegard Nossum
2009-02-21 16:21   ` Pekka Enberg
2009-02-21 13:36 ` [PATCH] kmemcheck: add hooks for page- and sg-dma-mappings Vegard Nossum
2009-02-21 16:22   ` Pekka Enberg
2009-02-21 17:13     ` Vegard Nossum
2009-02-21 17:15       ` Pekka Enberg
2009-02-21 13:36 ` [PATCH] kmemcheck: add hooks for the page allocator Vegard Nossum
2009-02-21 15:23   ` Ingo Molnar
2009-02-21 16:34   ` Pekka Enberg

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=19f34abd0902220251w4ec0485bp3eaa6092c60447a6@mail.gmail.com \
    --to=vegard.nossum@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@elte.hu \
    --cc=penberg@cs.helsinki.fi \
    /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