From: john stultz <johnstul@us.ibm.com>
To: Zwane Mwaikambo <zwane@arm.linux.org.uk>
Cc: "Mathias Fröhlich" <Mathias.Froehlich@web.de>,
lkml <linux-kernel@vger.kernel.org>,
"Mark Haverkamp" <markh@osdl.org>, "Dave Jones" <davej@suse.de>
Subject: Re: [RFC][PATCH] linux-2.6.0-test2_mtrr-race-fix_A0
Date: 06 Aug 2003 13:24:55 -0700 [thread overview]
Message-ID: <1060201495.10732.75.camel@cog.beaverton.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0308061423080.7244@montezuma.mastecende.com>
On Wed, 2003-08-06 at 11:31, Zwane Mwaikambo wrote:
> The intel manual (10-36 Memory Cache Control - vol3) actually recommends
> the following procedure I was a bit anal about explicitely setting and
> clearing flags and used the specific TLB flush via cr3->reg->cr3. John
> could you give this a spin on your afflicted systems?
I'm not quite sure I follow. Really I've never looked at the mtrr code
before, so forgive my daftness. I just found a deadlock that was
locking my box caused by the synchronization between ipi_handler() and
set_mtrr() (which Mark's patch seems to properly fix).
How does this change affect the deadlock? Is this just a separate issue?
thanks
-john
next prev parent reply other threads:[~2003-08-06 20:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 8:52 Mathias Fröhlich
2003-08-06 17:15 ` 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 [this message]
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=1060201495.10732.75.camel@cog.beaverton.ibm.com \
--to=johnstul@us.ibm.com \
--cc=Mathias.Froehlich@web.de \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=markh@osdl.org \
--cc=zwane@arm.linux.org.uk \
/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
all inboxes | Powered by JetHome®