From: Andi Kleen <ak@suse.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org,
Chuck Ebbert <76306.1226@compuserve.com>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: smp/up alternatives crash when CONFIG_HOTPLUG_CPU
Date: 20 Apr 2006 09:45:16 +0200 [thread overview]
Message-ID: <p73hd4o3d2r.fsf@bragg.suse.de> (raw)
In-Reply-To: <20060420052954.GA5524@elte.hu>
Ingo Molnar <mingo@elte.hu> writes:
>
> but ... a more fundamental question is, where does the SMP-alternatives
> code flush the icache? I dont think it's generally guaranteed on x86
> CPUs that MESI updates to code get propagated into the icache of other
> CPUs/cores.
Are you sure? I thought it was. Of course there can be bugs in this,
but I'm not aware of any on K8 or recent Intel CPUs. If that didn't
work much more things would be broken too (program/module loading,
JITs)
-Andi
next prev parent reply other threads:[~2006-04-20 7:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-19 9:46 smp/up alternatives crash when CONFIG_HOTPLUG_CPU Ingo Molnar
2006-04-20 5:29 ` Ingo Molnar
2006-04-20 7:45 ` Andi Kleen [this message]
2006-04-20 15:14 ` Linus Torvalds
2006-04-20 15:26 ` Ingo Molnar
2006-04-21 7:48 ` Ingo Molnar
2006-05-05 8:40 ` as bug (was: Re: smp/up alternatives crash when CONFIG_HOTPLUG_CPU) Denis Vlasenko
2006-05-05 8:45 ` Denis Vlasenko
2006-05-05 12:20 ` Alan Modra
2006-05-05 13:13 ` Denis Vlasenko
2006-05-06 3:11 ` Alan Modra
-- strict thread matches above, loose matches on Subject: below --
2006-04-21 23:31 smp/up alternatives crash when CONFIG_HOTPLUG_CPU Chuck Ebbert
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=p73hd4o3d2r.fsf@bragg.suse.de \
--to=ak@suse.de \
--cc=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@osdl.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