From: Keir Fraser <keir.xen@gmail.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Xen-devel <xen-devel@lists.xen.org>
Cc: Paul Durrant <paul.durrant@citrix.com>, Jan Beulich <JBeulich@suse.com>
Subject: Re: [Patch v3] x86/time: Update wallclock in shared info when altering domain time offset
Date: Wed, 17 Jul 2013 17:32:08 +0100 [thread overview]
Message-ID: <CE0C8598.5876B%keir.xen@gmail.com> (raw)
In-Reply-To: <1374059155-14647-1-git-send-email-andrew.cooper3@citrix.com>
On 17/07/2013 12:05, "Andrew Cooper" <andrew.cooper3@citrix.com> wrote:
> domain_set_time_offset() udpates d->time_offset_seconds, but does not correct
> the wallclock in the shared info, meaning that it is incorrect until the next
> XENPF_settime hypercall from dom0 which resynchronises the wallclock for all
> domains.
>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> CC: Keir Fraser <keir@xen.org>
> CC: Jan Beulich <JBeulich@suse.com>
> CC: Paul Durrant <Paul.Durrant@citrix.com>
Acked-by: Keir Fraser <keir@xen.org>
prev parent reply other threads:[~2013-07-17 16:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 11:05 [Patch v3] x86/time: Update wallclock in shared info when altering domain time offset Andrew Cooper
2013-07-17 16:32 ` Keir Fraser [this message]
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=CE0C8598.5876B%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=paul.durrant@citrix.com \
--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 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).