From: Paolo Bonzini <pbonzini@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>, Andrew Jones <drjones@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2 v2] x86: kvm: global clock updates
Date: Tue, 04 Mar 2014 12:34:45 +0100 [thread overview]
Message-ID: <5315BA55.4070202@redhat.com> (raw)
In-Reply-To: <20140228145234.GA13771@amt.cnet>
Il 28/02/2014 15:52, Marcelo Tosatti ha scritto:
> On Fri, Feb 28, 2014 at 12:52:53PM +0100, Andrew Jones wrote:
>> This patch series addresses two issues with global clock updates.
>> The first fixes a bug found on hosts that have a tsc marked as
>> unstable. As global clock updates get triggered on every vcpu load
>> in these cases, guests with a large number of vcpus have their
>> progress nearly halted. The fix for that bug should also go to
>> stable. The second patch in this series ensures that NTP corrections
>> on the host, as well as on guests with all vcpus pinned, will be
>> propagated periodically. That patch improves things, but doesn't
>> fix a bug, thus it can be merged at a later time than the first.
>> I've posted them together as a series, as the second one builds
>> on the first.
>>
>> Andrew Jones (2):
>> x86: kvm: rate-limit global clock updates
>> x86: kvm: introduce periodic global clock updates
>>
>> arch/x86/include/asm/kvm_host.h | 2 +
>> arch/x86/kvm/x86.c | 92 +++++++++++++++++++++++++++++++++++++++--
>> 2 files changed, 90 insertions(+), 4 deletions(-)
>>
>> --
>> 1.8.1.4
>
> Looks good.
>
Applied to kvm/queue, thanks to both.
Paolo
prev parent reply other threads:[~2014-03-04 11:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 11:52 [PATCH 0/2 v2] x86: kvm: global clock updates Andrew Jones
2014-02-28 11:52 ` [PATCH 1/2 v2] x86: kvm: rate-limit " Andrew Jones
2014-02-28 11:52 ` [PATCH 2/2 v2] x86: kvm: introduce periodic " Andrew Jones
2014-02-28 14:52 ` [PATCH 0/2 v2] x86: kvm: " Marcelo Tosatti
2014-03-04 11:34 ` Paolo Bonzini [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=5315BA55.4070202@redhat.com \
--to=pbonzini@redhat.com \
--cc=drjones@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.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).