From: George Dunlap <george.dunlap@eu.citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Diana Crisan <dcrisan@flexiant.com>,
xen-devel@lists.xen.org, Keir Fraser <keir@xen.org>,
Alex Bligh <alex@alex.org.uk>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [PATCH v3] x86/vtsc: update vcpu_time in hvm_set_guest_time
Date: Thu, 6 Jun 2013 09:45:01 +0100 [thread overview]
Message-ID: <51B04C0D.3080902@eu.citrix.com> (raw)
In-Reply-To: <51B0545102000078000DBC7C@nat28.tlf.novell.com>
On 06/06/13 08:20, Jan Beulich wrote:
>>>> On 06.06.13 at 08:59, Alex Bligh <alex@alex.org.uk> wrote:
>> --On 5 June 2013 14:06:09 +0100 George Dunlap <george.dunlap@eu.citrix.com> wrote:
>>
>>>> I have tested this patch and I have not been able to reproduce the
>>>> guest stuck-clock problem we were seeing before (see *HVM Migration of
>>>> domU on Qemu-upstream DM causes stuck system clock with ACPI* for
>>>> details of the problem).
>>>> Note: this was tested without the temporary fix to our problem ( which
>>>> is specifying tsc_mode='native_paravirt').
>>> Great, thanks Diana.
>> I see this has made master: commit 32c864a35ece2c24a336d183869a546798a4b241.
>>
>> Do you plan to backport this to 4.2? Diana has verified it applies and
>> fixes the same issue there.
> Yes, I have this on my list of pending backports, but currently there's
> no rush.
...but thank you for chasing it to make sure that it was on somebody's
list and didn't get forgotten. :-)
-George
next prev parent reply other threads:[~2013-06-06 8:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 15:32 [PATCH v3] x86/vtsc: update vcpu_time in hvm_set_guest_time Roger Pau Monne
2013-06-04 16:29 ` George Dunlap
2013-06-05 12:02 ` Diana Crisan
2013-06-05 13:06 ` George Dunlap
2013-06-05 13:35 ` Diana Crisan
2013-06-06 6:59 ` Alex Bligh
2013-06-06 7:20 ` Jan Beulich
2013-06-06 8:45 ` George Dunlap [this message]
2013-06-06 9:36 ` Alex Bligh
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=51B04C0D.3080902@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=alex@alex.org.uk \
--cc=dcrisan@flexiant.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.