From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>,
"Xen-Devel (xen-devel@lists.xensource.com)"
<xen-devel@lists.xensource.com>,
Ian Pratt <Ian.Pratt@eu.citrix.com>
Subject: Re: [RFC] Physical hot-add cpus and TSC
Date: Wed, 26 May 2010 22:26:10 +0100 [thread overview]
Message-ID: <C8235082.15F50%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <6b217ece-8fcf-430e-bb76-9883f798750d@default>
On 26/05/2010 20:46, "Dan Magenheimer" <dan.magenheimer@oracle.com> wrote:
>> It depends how physical CPU hotplug is implemented doesn't it. I expect
>> there's sufficient firmware involved in such an operation that TSCs
>> could
>> get synced up before host software gets a look in. I don't think we can
>> comment on whether or not there is an issue here without more
>> information.
>> Also, one reason Intel pushed the CPU hotplug logic is for RAS, and
>> offlining CPUs that throw errors, which can clearly be supported with
>> no concerns over TSC sync.
>
> OK, then would you accept a patch that disables physical cpu-hot-add
> (but not delete) unless enabled with a boot option, if the patch
> includes sufficient commenting and dmesg to explain the ramifications?
> Then in future if it turns out that TSC syncing is mostly always
> handled by firmware (doubtful but possible), the default for the
> boot option can be reversed.
If the patch will be acked by the Intel authors of the cpu hotplug stuff
then yes.
-- Keir
next prev parent reply other threads:[~2010-05-26 21:26 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 15:19 [RFC] Physical hot-add cpus and TSC Dan Magenheimer
2010-05-26 15:45 ` Keir Fraser
2010-05-26 16:44 ` Dan Magenheimer
2010-05-26 17:02 ` Ian Pratt
2010-05-26 17:29 ` Keir Fraser
2010-05-26 17:39 ` Dan Magenheimer
2010-05-26 17:51 ` Keir Fraser
2010-05-26 18:01 ` Keir Fraser
2010-05-26 19:46 ` Dan Magenheimer
2010-05-26 21:26 ` Keir Fraser [this message]
2010-05-27 6:15 ` Jiang, Yunhong
2010-05-27 6:57 ` Keir Fraser
2010-05-27 7:09 ` Jiang, Yunhong
2010-05-27 7:15 ` Jiang, Yunhong
2010-05-27 19:55 ` Dan Magenheimer
2010-05-27 8:44 ` Keir Fraser
2010-05-27 9:31 ` Jiang, Yunhong
2010-05-27 15:08 ` Dan Magenheimer
2010-05-28 5:39 ` Jiang, Yunhong
2010-05-28 5:47 ` Keir Fraser
2010-05-28 6:29 ` Jiang, Yunhong
2010-05-28 7:03 ` Keir Fraser
2010-05-28 14:35 ` Dan Magenheimer
2010-05-28 15:33 ` Jiang, Yunhong
2010-05-28 16:25 ` Dan Magenheimer
2010-05-31 8:56 ` Jiang, Yunhong
2010-05-28 16:08 ` Keir Fraser
2010-05-28 16:36 ` Dan Magenheimer
2010-05-28 17:19 ` Keir Fraser
2010-05-28 14:52 ` Dan Magenheimer
2010-05-28 15:05 ` Jiang, Yunhong
2010-05-28 20:24 ` Dan Magenheimer
2010-05-31 7:54 ` Jiang, Yunhong
2010-06-01 0:30 ` Dan Magenheimer
2010-06-01 1:40 ` Jiang, Yunhong
2010-06-01 17:07 ` Jeremy Fitzhardinge
2010-06-02 9:17 ` Jiang, Yunhong
2010-06-10 6:55 ` Dong, Eddie
2010-06-10 13:15 ` Dan Magenheimer
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=C8235082.15F50%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=Ian.Pratt@eu.citrix.com \
--cc=dan.magenheimer@oracle.com \
--cc=xen-devel@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;
as well as URLs for NNTP newsgroup(s).