From: "Dan Magenheimer" <dan.magenheimer@oracle.com>
To: John Levon <levon@movementarian.org>
Cc: Ian Pratt <Ian.Pratt@eu.citrix.com>,
"Xen-Devel (E-mail)" <xen-devel@lists.xensource.com>,
Dave Winchell <dwinchell@virtualiron.com>,
Keir Fraser <keir.fraser@eu.citrix.com>
Subject: RE: RE: [PATCH] rendezvous-based local time calibration WOW!
Date: Tue, 5 Aug 2008 15:27:55 -0600 [thread overview]
Message-ID: <20080805152755062.00000008444@djm-pc> (raw)
In-Reply-To: <20080805211251.GA27007@totally.trollied.org.uk>
> No, as it would be incredibly slow on Solaris (I dread to imagine).
Could be. On my box (Conroe), trapping tsc in an hvm is faster
than reading pit or hpet in the hypervisor or in a native OS.
> -----Original Message-----
> From: John Levon [mailto:levon@movementarian.org]
> Sent: Tuesday, August 05, 2008 3:13 PM
> To: Dan Magenheimer
> Cc: Ian Pratt; Xen-Devel (E-mail); Dave Winchell; Keir Fraser
> Subject: Re: [Xen-devel] RE: [PATCH] rendezvous-based local time
> calibration WOW!
>
>
> On Tue, Aug 05, 2008 at 02:49:25PM -0600, Dan Magenheimer wrote:
>
> > The algorithm used to compute the timestamp information
>
> Thanks.
>
> > I'm not sure its possible to guarantee monotonicity in
> > PV domains (without a global lock) except by doing a trap
> > or hypercall at each "get time".
>
> That's a shame.
>
> > I've thought about implementing softtsc for PV domains for
> > this reason. (Softtsc was just added at 4.0 for hvm domains
> > and causes all hvm tsc reads to trap.) Would this be of
> > interest?
>
> No, as it would be incredibly slow on Solaris (I dread to imagine).
>
> regards,
> john
>
next prev parent reply other threads:[~2008-08-05 21:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-03 16:50 [PATCH] rendezvous-based local time calibration WOW! Dan Magenheimer
2008-08-03 17:24 ` Keir Fraser
2008-08-04 15:24 ` Dan Magenheimer
2008-08-04 15:36 ` Keir Fraser
2008-08-04 17:10 ` Keir Fraser
2008-08-04 17:37 ` Dan Magenheimer
2008-08-04 19:40 ` Dan Magenheimer
2008-08-04 19:47 ` Keir Fraser
2008-08-05 18:56 ` John Levon
2008-08-05 20:49 ` Dan Magenheimer
2008-08-05 21:12 ` John Levon
2008-08-05 21:27 ` Dan Magenheimer [this message]
2008-08-05 21:43 ` Keir Fraser
2008-08-06 13:25 ` Dan Magenheimer
2008-08-06 13:38 ` John Levon
2008-08-06 15:09 ` Dan Magenheimer
2008-08-06 15:21 ` John Levon
2008-08-06 15:34 ` Dan Magenheimer
2008-08-09 14:47 ` Nils Nieuwejaar
2008-08-09 20:55 ` Dan Magenheimer
2008-08-11 14:37 ` John Levon
2008-08-11 14:38 ` Keir Fraser
2008-08-11 14:43 ` John Levon
2008-08-11 14:46 ` Keir Fraser
2008-08-11 14:49 ` John Levon
2008-08-11 14:50 ` Keir Fraser
2008-08-11 18:41 ` John Levon
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=20080805152755062.00000008444@djm-pc \
--to=dan.magenheimer@oracle.com \
--cc=Ian.Pratt@eu.citrix.com \
--cc=dwinchell@virtualiron.com \
--cc=keir.fraser@eu.citrix.com \
--cc=levon@movementarian.org \
--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.