From: David Vrabel <david.vrabel@citrix.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: <xen-devel@lists.xen.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
<linux-kernel@vger.kernel.org>,
John Stultz <john.stultz@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCHv5 0/4] xen: maintain an accurate persistent clock in more cases
Date: Thu, 20 Jun 2013 20:18:00 +0100 [thread overview]
Message-ID: <51C35568.5050600@citrix.com> (raw)
In-Reply-To: <1371755619-25348-1-git-send-email-david.vrabel@citrix.com>
On 20/06/13 20:13, David Vrabel wrote:
> Xen guests use the Xen wallclock as their persistent clock. This is a
> software only clock in the hypervisor that is used by guests instead
> of a real hardware RTC.
Sorry, I accidentally specified the wrong revision range and only
include 2 out 4 of the patches in the series.
I have resent the complete series.
David
next prev parent reply other threads:[~2013-06-20 19:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 19:13 [PATCHv5 0/4] xen: maintain an accurate persistent clock in more cases David Vrabel
2013-06-20 19:13 ` [PATCH 1/2] hrtimers: provide a hrtimers_late_resume() call David Vrabel
2013-06-20 19:13 ` David Vrabel
2013-06-20 19:13 ` [PATCH 2/2] time: add a notifier chain for when the system time is stepped David Vrabel
2013-06-20 19:13 ` David Vrabel
2013-06-20 19:18 ` David Vrabel [this message]
2013-06-20 19:18 ` [PATCHv5 0/4] xen: maintain an accurate persistent clock in more cases David Vrabel
-- strict thread matches above, loose matches on Subject: below --
2013-06-20 19:16 David Vrabel
2013-06-20 20:03 ` John Stultz
2013-06-20 20:03 ` John Stultz
2013-06-21 18:31 ` Konrad Rzeszutek Wilk
2013-06-21 18:31 ` Konrad Rzeszutek Wilk
2013-06-20 19:16 David Vrabel
2013-06-20 19:13 David Vrabel
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=51C35568.5050600@citrix.com \
--to=david.vrabel@citrix.com \
--cc=john.stultz@linaro.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=xen-devel@lists.xen.org \
/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.