public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Gerd Knorr <kraxel@suse.de>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Xen merge mainline list <xen-merge@lists.xensource.com>
Subject: Re: [patch] SMP alternatives for i386
Date: Tue, 13 Dec 2005 15:58:02 +0000	[thread overview]
Message-ID: <1134489482.11732.87.camel@localhost.localdomain> (raw)
In-Reply-To: <439EE742.5040909@suse.de>

The SMP problems with self modifying code are very real but the hotplug
architecture for CPU already deals with these synchronizations and you
can use the SMP cross calls to 'capture' the other processors. The x86
case of processors with differing feature sets is extremely common on
PII/PIII systems and can also occur on other platforms where features
like SSE3 were introduced in later steppings. Clean alternatives support
for such platforms automatically would be good.

Other than that it looks sane to me (well the CPU hotplug case is silly
but the rest makes sense). The various CPU errata come out ok that I can
see as well because they use rmb/wmb/etc and those don't change
behaviour so still maintain store order against the bus.


  parent reply	other threads:[~2005-12-13 15:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-13 15:22 [patch] SMP alternatives for i386 Gerd Knorr
2005-12-13 15:36 ` [Xen-merge] " Zachary Amsden
2005-12-13 16:32   ` Gerd Knorr
2005-12-13 15:58 ` Alan Cox [this message]
2005-12-14 19:35 ` Zwane Mwaikambo
2005-12-14 20:15   ` [Xen-merge] " Keir Fraser
2005-12-15  1:20     ` Zwane Mwaikambo
2005-12-15 13:44       ` Gerd Knorr

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=1134489482.11732.87.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=kraxel@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xen-merge@lists.xensource.com \
    /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