From: Shaohua Li <shaohua.li@intel.com>
To: Zwane Mwaikambo <zwane@arm.linux.org.uk>
Cc: lkml <linux-kernel@vger.kernel.org>, akpm <akpm@osdl.org>,
Ashok Raj <ashok.raj@intel.com>, ak <ak@muc.de>
Subject: Re: [PATCH]x86-x86_64 flush cache for CPU hotplug
Date: Mon, 13 Jun 2005 09:18:44 +0800 [thread overview]
Message-ID: <1118625524.3822.12.camel@linux-hp.sh.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0506101310120.31175@montezuma.fsmlabs.com>
On Fri, 2005-06-10 at 13:11 -0600, Zwane Mwaikambo wrote:
> Hello Shaohua,
>
> On Fri, 10 Jun 2005, Shaohua Li wrote:
>
> > We should flush cache at CPU hotplug. An error has been observed data is
> > corrupted after CPU hotplug in CPUs with bigger cache.
> > I guess IA64 requires similar change, Ashok?
>
> Interesting, which processor was this?
It's a kind of Pentium M.
> >
> > linux-2.6.12-rc6-mm1-root/arch/i386/kernel/process.c | 1 +
> > linux-2.6.12-rc6-mm1-root/arch/x86_64/kernel/process.c | 1 +
> > 2 files changed, 2 insertions(+)
> >
> > diff -puN arch/i386/kernel/process.c~flush_cache_cpuhotplug arch/i386/kernel/process.c
> > --- linux-2.6.12-rc6-mm1/arch/i386/kernel/process.c~flush_cache_cpuhotplug 2005-06-10 10:56:05.082247160 +0800
> > +++ linux-2.6.12-rc6-mm1-root/arch/i386/kernel/process.c 2005-06-10 11:05:10.597316264 +0800
> > @@ -155,6 +155,7 @@ static inline void play_dead(void)
> > {
> > /* This must be done before dead CPU ack */
> > cpu_exit_clear();
> > + wbinvd();
> > mb();
>
> We shouldn't need that mb() there anymore then, ditto for the other
> location.
Indead. How about just leave it here for clearness?
Thanks,
Shaohua
prev parent reply other threads:[~2005-06-13 1:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-10 3:30 [PATCH]x86-x86_64 flush cache for CPU hotplug Shaohua Li
2005-06-10 16:30 ` Ashok Raj
2005-06-10 16:34 ` Ashok Raj
2005-06-10 17:21 ` Andi Kleen
2005-06-13 1:13 ` Shaohua Li
2005-06-10 19:11 ` Zwane Mwaikambo
2005-06-13 1:18 ` Shaohua Li [this message]
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=1118625524.3822.12.camel@linux-hp.sh.intel.com \
--to=shaohua.li@intel.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=ashok.raj@intel.com \
--cc=linux-kernel@vger.kernel.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