xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: "Jiang, Yunhong" <yunhong.jiang@intel.com>,
	Keir Fraser <keir.fraser@eu.citrix.com>,
	"Xen-Devel (xen-devel@lists.xensource.com)"
	<xen-devel@lists.xensource.com>, Ian Pratt <Ian.Pratt@e>
Subject: RE: [RFC] Physical hot-add cpus and TSC
Date: Fri, 28 May 2010 13:24:50 -0700 (PDT)	[thread overview]
Message-ID: <2d0b4e25-6fa9-4d66-9efe-a1b9e27612f5@default> (raw)
In-Reply-To: <789F9655DD1B8F43B48D77C5D30659731E78DA70@shsmsx501.ccr.corp.intel.com>

> >> b) With the patch:
> >> After add:
> >> (XEN) TSC marked as reliable, warp = 407 (count=12)
> >> (XEN) TSC marked as reliable, warp = 444 (count=17)
> >> (XEN) TSC marked as reliable, warp = 525 (count=19)
> >
> >Hi Yunhong --
> >
> >Does this continue to grow?  I'm concerned that
> >the hot-added CPU might be skewing as well?
> >I didn't think this was possible with an Invariant
> >TSC machine but maybe something in the hot-add
> >isolation electronics changes the characteristics
> >of the clock signal?
> >Please try:
> >
> >for i in {0..1000}; do xm debug-key t; sleep 3; done; \
> >xm dmesg | tail
> >
> >then wait an hour, and see how large the warp is.
> >Hopefully the trend (407,444,525) is a coincidence.
> 
> I just looped 10 times, I will try with 1000 loops next Monday.
> I suspect there are any isolation electronics for hot-add. Basically
> each CPU can be hot-added except socket 0. But yes, I can have a look
> on it.

Hmmm... I'm not a system hardware expert, but the more I think
about this, the more likely it seems that any hot-plug
board must have separate QPI buses that are driven by separate
crystals.  And there would be some kind of bus bridge/repeater
to connect the two with a forwarding protocol.  That would
certainly explain a growing TSC skew.

If so, even two single socket boards connected like that at
initial boot (no hot-add) are really a "big NUMA" system due
to higher cross-node latencies and might deserve a separate
boot option anyway... this is really NOT a single system...
it is multiple systems glued together with a fast interconnect.
Xen (and users) should be warned that there is no free
lunch here and the performance degradation from TSC emulation
may be only a small part of the problem.

Some boot option like "multiboard_interconnect" (but shorter)
might be appropriate?  Or is there some way at boot-time
to determine that this box does, or might (via hot-add), or
definitely does not, go beyond point-to-point interconnect?
A boot-time decision on TSC emulation could be driven off
of that if it existed.

  reply	other threads:[~2010-05-28 20:24 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
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 [this message]
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=2d0b4e25-6fa9-4d66-9efe-a1b9e27612f5@default \
    --to=dan.magenheimer@oracle.com \
    --cc=Ian.Pratt@e \
    --cc=keir.fraser@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=yunhong.jiang@intel.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).