From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>,
"Jiang, Yunhong" <yunhong.jiang@intel.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 09:36:59 -0700 (PDT) [thread overview]
Message-ID: <681ea80b-75c6-41cc-a13d-3c7e25721f99@default> (raw)
In-Reply-To: <C825A914.16417%keir.fraser@eu.citrix.com>
> Linux doesn't make strong
> guarantees to applications about TSC semantics, by synthesising TSC, or
> anything like that.
Working on that ;-) IMHO, any non-privileged use of rdtsc,
even under the control of the kernel (e.g. vsyscall) has
potential issues in a virtual machine. Except a VMware
VM, where the problem is completely solved.
But, as you know, many Linux kernel developers aren't too
interested in solving problems for Xen, so there's an
uphill battle :-(
> Anyhow, retreading this argument is not going to be fruitful
> It's fair to
> say that your definition is now also Xen's definition.
Sorry, I'm not trying to beat a dead horse. I'm just
playing whack-a-mole and repeating arguments for a
new audience and a new corner case. If you prefer, I
can take that offlist.
next prev parent reply other threads:[~2010-05-28 16:36 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 [this message]
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=681ea80b-75c6-41cc-a13d-3c7e25721f99@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).