From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xensource.com,
Adi Kriegisch <adi@cg.tuwien.ac.at>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: Dom0 ACPI S3 patches
Date: Wed, 14 Sep 2011 10:44:12 -0700 [thread overview]
Message-ID: <4E70E7EC.4030809@goop.org> (raw)
In-Reply-To: <4E7084C30200007800055FBE@nat28.tlf.novell.com>
On 09/14/2011 01:41 AM, Jan Beulich wrote:
>>>> On 14.09.11 at 10:11, Adi Kriegisch <adi@cg.tuwien.ac.at> wrote:
>> * The DomUs do not resync their clock after Dom0 waking up. They're
>> basically continue to count the time as if the sleep never happened.
>> I have to run 'ntpdate' on resume on all the DomUs. I am not sure if
>> there are any side effects of this; probably there is a more simple way
>> to tell a DomU to reread clock from Dom0?
> This is a more fundamental problem - upstream pv-ops doesn't make
> use of XENFP_settime (or its bogus alias DOM_SETTIME) at all; only
> Jeremy's 2.6.32.x tree has this so far.
I was confused grepping for those: XEN*PF*_settime, or DOM*0*_SETTIME.
Yeah, thanks for the reminder. I've queued that up for the next merge
window.
J
next prev parent reply other threads:[~2011-09-14 17:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-14 8:11 Dom0 ACPI S3 patches Adi Kriegisch
2011-09-14 8:41 ` Jan Beulich
2011-09-14 17:44 ` Jeremy Fitzhardinge [this message]
2011-09-14 10:21 ` Konrad Rzeszutek Wilk
2011-09-14 13:17 ` Adi Kriegisch
[not found] ` <20110914112718.GG3079@vrvis.at>
2011-09-14 14:28 ` Konrad Rzeszutek Wilk
2011-09-14 15:09 ` Adi Kriegisch
2011-09-14 15:47 ` Konrad Rzeszutek Wilk
2011-09-15 13:18 ` Adi Kriegisch
2011-09-27 14:50 ` Adi Kriegisch
2011-09-27 22:26 ` Konrad Rzeszutek Wilk
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=4E70E7EC.4030809@goop.org \
--to=jeremy@goop.org \
--cc=JBeulich@suse.com \
--cc=adi@cg.tuwien.ac.at \
--cc=konrad.wilk@oracle.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 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).