From: Andi Kleen <ak@suse.de>
To: "Sowadski, Craig Harold (UMR-Student)" <sowadski@umr.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.20 amd speculative caching
Date: 19 Feb 2003 18:53:33 +0100 [thread overview]
Message-ID: <p73u1f0xile.fsf@amdsimf.suse.de> (raw)
In-Reply-To: "Sowadski, Craig Harold's message of "19 Feb 2003 17:39:31 +0100"
"Sowadski, Craig Harold (UMR-Student)" <sowadski@umr.edu> writes:
> I have recently upgraded to an AMD processor that is exhibiting the
> problems with the AMD speculative caching bug. Kernel 2.4.19 seems to
It's actually not an AMD bug, but an Linux bug that assumed undefined x86
behaviour to behave well.
> fix the problem with the temporary work-around (adv-spec-cache patch). I
> have noticed that the patch has been removed from 2.4.20 and I am
> wondering if there is some other mechanism that is supposed to address
> this issue. Currently I have a 2.4.20 kernel with same configuration as
Yes, there is a new mechanism to address the problem the adv-spec-cache
patch solved. It enforces that there are not conflicting cache attributes
for memory mappings.
> my 2.4.19 and the problem seems to have reappeared.
What problem exactly? And does mem=nopentium help ?
-Andi
next parent reply other threads:[~2003-02-19 17:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A5D66E6B6F478B48A3CEF22AA4B9FCA3012E54@umr-mail1.umr.edu.suse.lists.linux.kernel>
2003-02-19 17:53 ` Andi Kleen [this message]
2003-02-24 19:32 2.4.20 amd speculative caching Sowadski, Craig Harold (UMR-Student)
[not found] <99F2150714F93F448942F9A9F112634C013857BF@txexmtae.amd.com.suse.lists.linux.kernel>
2003-02-22 5:25 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2003-02-22 0:11 richard.brunner
2003-02-20 18:48 Sowadski, Craig Harold (UMR-Student)
2003-02-20 17:07 Alastair Stevens
2003-02-20 16:49 Randal, Phil
2003-02-19 19:13 Sowadski, Craig Harold (UMR-Student)
2003-02-20 16:53 ` Dave Jones
2003-02-19 16:28 Sowadski, Craig Harold (UMR-Student)
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=p73u1f0xile.fsf@amdsimf.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sowadski@umr.edu \
/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.