From: "Mathias Fröhlich" <Mathias.Froehlich@web.de>
To: johnstul@us.ibm.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] linux-2.6.0-test2_mtrr-race-fix_A0
Date: Wed, 6 Aug 2003 10:52:18 +0200 [thread overview]
Message-ID: <200308061052.18550.Mathias.Froehlich@web.de> (raw)
Hi,
You should not remove the barrier past mtrr change. If you do that, it is
possible that cpu's run with inconsistent mtrrs. This can have bad
sideeffects since at least the cache snooping protocol used by intel uses
assumptions about the cachability of memory regions. Those information about
the cachability is also taken from the mtrrs as far as I remember.
This intel cpu developer manual, which documented the early PII and PPro
chips, recommended this algorithm. Since actual intel cpus use the same old
cpu to chipset bus protocol, this old documentation most propably still
applies.
So the conclusion is that as far as you don't know the exact way all those SMP
protocols between chipsets and CPUs with all the possible sideeffects very
well, dont't change this behavour.
But I'm shure that fixes to the stack allocated variable problem are welcome
:)
Greetings
Mathias Fröhlich
--
Mathias Fröhlich, email: Mathias.Froehlich@web.de
old email was: frohlich@na.uni-tuebingen.de
next reply other threads:[~2003-08-06 8:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 8:52 Mathias Fröhlich [this message]
2003-08-06 17:15 ` [RFC][PATCH] linux-2.6.0-test2_mtrr-race-fix_A0 john stultz
2003-08-06 18:05 ` Mark Haverkamp
2003-08-06 18:02 ` john stultz
2003-08-07 14:38 ` [PATCH] linux-2.6.0-test2_mtrr-race-fix_A0 Mark Haverkamp
2003-08-06 18:31 ` [RFC][PATCH] linux-2.6.0-test2_mtrr-race-fix_A0 Zwane Mwaikambo
2003-08-06 20:24 ` john stultz
2003-08-07 5:06 ` Zwane Mwaikambo
-- strict thread matches above, loose matches on Subject: below --
2003-08-06 2:17 john stultz
2003-08-06 17:02 ` Mark Haverkamp
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=200308061052.18550.Mathias.Froehlich@web.de \
--to=mathias.froehlich@web.de \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
/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