From: George Dunlap <george.dunlap@eu.citrix.com>
To: Alex Bligh <alex@alex.org.uk>
Cc: Diana Crisan <dcrisan@flexiant.com>,
xen-devel@lists.xen.org, Keir Fraser <keir@xen.org>,
Jan Beulich <jbeulich@suse.com>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [PATCH] x86/vtsc: update vcpu_time after hvm_set_guest_time
Date: Tue, 4 Jun 2013 11:28:05 +0100 [thread overview]
Message-ID: <51ADC135.3050200@eu.citrix.com> (raw)
In-Reply-To: <2FCD40715DE006ED58FDA5F6@Ximines.local>
On 06/04/2013 11:24 AM, Alex Bligh wrote:
> Roger,
>
> --On 4 June 2013 11:10:50 +0200 Roger Pau Monne <roger.pau@citrix.com>
> 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.
>
> I think this is the 'proper' fix to the bug Diana reported about
> stuck clock - can you confirm? If so, we're happy to test this on
> 4.3 and/or do try our hand at a backport to 4.2.
Yes, and I was going to reply cc'ing you and Diana, but we're still
having a technical discussion about where the best place is to put the
fix. You may wish to wait until we have that resolved before testing
the patch.
-George
prev parent reply other threads:[~2013-06-04 10:28 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
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 [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=51ADC135.3050200@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=alex@alex.org.uk \
--cc=dcrisan@flexiant.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 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.