From: George Dunlap <george.dunlap@eu.citrix.com>
To: Roger Pau Monne <roger.pau@citrix.com>
Cc: Keir Fraser <keir@xen.org>, Jan Beulich <jbeulich@suse.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH] x86/vtsc: update vcpu_time after hvm_set_guest_time
Date: Tue, 4 Jun 2013 10:47:16 +0100 [thread overview]
Message-ID: <51ADB7A4.2000503@eu.citrix.com> (raw)
In-Reply-To: <1370337050-2444-1-git-send-email-roger.pau@citrix.com>
On 06/04/2013 10:10 AM, Roger Pau Monne wrote:
> When using a vtsc, hvm_set_guest_time changes hvm_vcpu.stime_offset,
> which is used in the vcpu time structure to calculate the
> tsc_timestamp, so after updating stime_offset we need to propagate the
> change to vcpu_time in order for the guest to get the right time if
> using the PV clock.
>
> This was not done correctly, since in context_switch
> update_vcpu_system_time was called before vmx_do_resume, which caused
> the vcpu_info time structure to be updated with the wrong values. This
> patch fixes this by calling update_vcpu_system_time after the call to
> hvm_set_guest_time has happened.
Would it make more sense to actually do this in hvm_set_guest_time()
instead, so that this window where the vcpu system_time is closed for
all callers, not just hvm_do_resume?
You could gate calling update_vcpu_system_time on:
1. Whether stime_offset actually changed
2. Whether v is currently running
-George
next prev parent reply other threads:[~2013-06-04 9:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 9:10 [PATCH] x86/vtsc: update vcpu_time after hvm_set_guest_time Roger Pau Monne
2013-06-04 9:24 ` Jan Beulich
2013-06-04 9:46 ` Roger Pau Monné
2013-06-04 9:56 ` George Dunlap
2013-06-04 10:41 ` Jan Beulich
2013-06-04 9:47 ` George Dunlap [this message]
2013-06-04 9:58 ` Roger Pau Monné
2013-06-04 10:00 ` George Dunlap
2013-06-04 10:12 ` Roger Pau Monné
2013-06-04 11:15 ` Roger Pau Monné
2013-06-04 11:45 ` Jan Beulich
2013-06-04 12:48 ` Roger Pau Monné
2013-06-04 10:24 ` Alex Bligh
2013-06-04 10:28 ` George Dunlap
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=51ADB7A4.2000503@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=roger.pau@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).