xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Keir Fraser <Keir.Fraser@eu.citrix.com>, xen-devel@lists.xensource.com
Subject: Concern about c/s 21404: Remove special-case paths for start-of-day SMP bringup
Date: Wed, 19 May 2010 09:24:39 -0700 (PDT)	[thread overview]
Message-ID: <771369f4-b30f-4b0e-bae2-69758df0d89e@default> (raw)

"Notably ganged TSC calibration is removed"

Really?  We have recently seen machines which generated
the removed message "CPUX had N usecs TSC skew, fixed it up."

I'm not sure I fully understand the scope or the purpose
of all the patches, but since the TSC is the foundation for
Xen system time which is the foundation for virtually all time
handling in all guests (because even the non-TSC emulated
timers are built on Xen system time), I think you are introducing
a big risk here for an unknown number of existing systems.
Some of the problems may be obvious because a guest often
won't boot when clocks are screwy, but other problems may
not manifest until "later" when under a heavy load that
causes more frequent vcpu->pcpu switching and may not
be at all obviously related to clock problems.  (We've
recently seen that also with a Solaris HV guest running
on a pre-4.0 Xen where rdtsc is not yet emulated.)

Note that Linux is *adding* code to attempt to make TSC more
reliable, while it appears this Xen patch is taking code away.

If I understand, the purpose is to provide a better
way to online CPUs so as to handle CPU hotplug better?
While hotplug is a nice feature, am I correct that the
feature is supported in a very small number of
systems?  And is actually used in an even smaller
number?

My two cents: Doesn't seem like a good tradeoff to me...

             reply	other threads:[~2010-05-19 16:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-19 16:24 Dan Magenheimer [this message]
2010-05-19 19:15 ` Concern about c/s 21404: Remove special-case paths for start-of-day SMP bringup Keir Fraser

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=771369f4-b30f-4b0e-bae2-69758df0d89e@default \
    --to=dan.magenheimer@oracle.com \
    --cc=Keir.Fraser@eu.citrix.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).