All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ashok Raj <ashok.raj@intel.com>
To: Shaohua Li <shaohua.li@intel.com>
Cc: lkml <linux-kernel@vger.kernel.org>, akpm <akpm@osdl.org>,
	Ashok Raj <ashok.raj@intel.com>,
	Zwane Mwaikambo <zwane@linuxpower.ca>, ak <ak@muc.de>
Subject: Re: [PATCH]x86-x86_64 flush cache for CPU hotplug
Date: Fri, 10 Jun 2005 09:30:51 -0700	[thread overview]
Message-ID: <20050610093051.A25536@unix-os.sc.intel.com> (raw)
In-Reply-To: <1118374208.7510.6.camel@linux-hp.sh.intel.com>; from shaohua.li@intel.com on Fri, Jun 10, 2005 at 11:30:08AM +0800

On Fri, Jun 10, 2005 at 11:30:08AM +0800, Shaohua Li wrote:
> Hi,
> 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?

Yes, we need that for IA64 as well. i did put that in my notes tbd, but 
didnt turn around doing it yet. 

Think we also need to define the same for asm-ia64/acpi.h FLUSH_CPU_CACHE
i will try updating both in next.

If you have a targetted test that causes the corruption that would be great
so we can add to our stress test senarios.

Cheers,
ashok
> 
> Thanks,
> Shaohua
> 
> Signed-off-by: Shaohua.li<shaohua.li@intel.com>
> ---
> 
>  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(+)
> 

  reply	other threads:[~2005-06-10 16:35 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 [this message]
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

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=20050610093051.A25536@unix-os.sc.intel.com \
    --to=ashok.raj@intel.com \
    --cc=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaohua.li@intel.com \
    --cc=zwane@linuxpower.ca \
    /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.