From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
"Xen-Devel (E-mail)" <xen-devel@lists.xensource.com>,
"Dugger, Donald D" <donald.d.dugger@intel.com>,
Keir Fraser <keir.fraser@eu.citrix.com>,
Jan Beulich <JBeulich@novell.com>
Subject: Re: pvclock in userland (reprise)
Date: Thu, 17 Sep 2009 12:24:14 -0700 [thread overview]
Message-ID: <4AB28CDE.4020208@goop.org> (raw)
In-Reply-To: <0B53E02A2965CE4F9ADB38B34501A3A19411DC3F@orsmsx505.amr.corp.intel.com>
On 09/17/09 12:13, Nakajima, Jun wrote:
> Maybe you can write a device driver in the guest that sets up mapping against the (virtual) physical memory, then use mmap() in the app?
>
Dan is trying to avoid making guest kernel changes, on the grounds that
waiting for enterprise distros to catch up would take too long.
Once you're making kernel changes then you can update the pvclock
mechanism to use the xen clock algorithm, obviating the need for
usermode ABI changes.
However, if its really the case that the tsc is guaranteed synchronized,
then the guest can determine that for itself by looking at cpuid and/or
/proc/cpuinfo (and presumably doing some sanity checking) and then just
directly use rdtsc, with no need to change either Xen or the kernel.
J
next prev parent reply other threads:[~2009-09-17 19:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-17 17:58 pvclock in userland (reprise) Dan Magenheimer
2009-09-17 19:03 ` Keir Fraser
2009-09-17 19:13 ` Nakajima, Jun
2009-09-17 19:23 ` Keir Fraser
2009-09-17 19:24 ` Jeremy Fitzhardinge [this message]
2009-09-17 19:45 ` Dan Magenheimer
2009-09-17 20:13 ` Jeremy Fitzhardinge
2009-09-17 20:57 ` Dan Magenheimer
2009-09-18 7:29 ` Jan Beulich
2009-09-18 8:06 ` Keir Fraser
2009-09-19 0:33 ` Jeremy Fitzhardinge
2009-09-19 10:47 ` Keir Fraser
2009-09-21 8:20 ` Jan Beulich
2009-09-21 18:54 ` Jeremy Fitzhardinge
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=4AB28CDE.4020208@goop.org \
--to=jeremy@goop.org \
--cc=JBeulich@novell.com \
--cc=dan.magenheimer@oracle.com \
--cc=donald.d.dugger@intel.com \
--cc=jun.nakajima@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.