From: David Vrabel <david.vrabel@citrix.com>
To: John Stultz <john.stultz@linaro.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
linux-kernel@vger.kernel.org, xen-devel@lists.xen.org
Subject: Re: [PATCHv3 0/2] xen: maintain an accurate persistent clock in more cases
Date: Fri, 31 May 2013 10:56:09 +0100 [thread overview]
Message-ID: <51A873B9.4000407__20013.1626254462$1369994304$gmane$org@citrix.com> (raw)
In-Reply-To: <51A7E709.9080309@linaro.org>
On 31/05/13 00:55, John Stultz wrote:
> On 05/30/2013 07:25 AM, David Vrabel wrote:
>>
>> These series fixes the above limitations and depends on "x86: increase
>> precision of x86_platform.get/set_wallclock()" which was previously
>> posted.
>
> This is the only area that will need some coordination cross the Xen
> tree and tip/timers/core (once that patch and the fix for it I have
> queued lands in -tip). The options here are:
>
> * I queue these two patches with proper Xen maintainer's acks/review
I'm happy for this to be queues for 3.11. Although the series does fix
a bug it's one that I don't think affects that many people (I don't
think I seen any bug reports from anyone else).
We're only rarely seeing the problem in our automated test system which
is not a typical setup.
David
next prev parent reply other threads:[~2013-05-31 9:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 14:25 [PATCHv3 0/2] xen: maintain an accurate persistent clock in more cases David Vrabel
2013-05-30 14:25 ` [PATCH 1/2] x86/xen: sync the wallclock when the system time changes David Vrabel
2013-05-31 0:30 ` John Stultz
2013-05-31 0:30 ` John Stultz
2013-05-31 9:49 ` David Vrabel
2013-05-31 9:49 ` David Vrabel
2013-05-31 20:21 ` John Stultz
2013-05-31 20:21 ` John Stultz
2013-05-30 14:25 ` David Vrabel
2013-05-30 14:25 ` [PATCH 2/2] x86/xen: sync the CMOS RTC as well as the Xen wallclock David Vrabel
2013-05-30 14:25 ` David Vrabel
2013-05-30 23:55 ` [PATCHv3 0/2] xen: maintain an accurate persistent clock in more cases John Stultz
2013-05-31 7:52 ` [Xen-devel] " Jan Beulich
2013-05-31 7:52 ` Jan Beulich
2013-05-31 9:56 ` David Vrabel [this message]
2013-05-31 9:56 ` David Vrabel
2013-05-30 23:55 ` John Stultz
-- strict thread matches above, loose matches on Subject: below --
2013-05-30 14:25 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='51A873B9.4000407__20013.1626254462$1369994304$gmane$org@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.