linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zachary Amsden <zamsden@redhat.com>
To: Glauber Costa <glommer@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, avi@redhat.com
Subject: Re: [PATCH v2 0/7] Pvclock fixes , version two
Date: Tue, 04 May 2010 17:57:18 -1000	[thread overview]
Message-ID: <4BE0EC9E.3040508@redhat.com> (raw)
In-Reply-To: <1272901927-829-1-git-send-email-glommer@redhat.com>

On 05/03/2010 05:52 AM, Glauber Costa wrote:
> Here is a new version of this series.
>
> I am definitely leaving any warp calculations out, as Jeremy wisely
> points out that Chuck Norris should perish before we warp.
>
> Also, in this series, I am using KVM_GET_SUPPORTED_CPUID to export
> our features to userspace, as avi suggets. (patch 4/7), and starting
> to use the flag that indicates possible tsc stability (patch 7/7), although
> it is still off by default.
>
> Glauber Costa (7):
>    Enable pvclock flags in vcpu_time_info structure
>    Add a global synchronization point for pvclock
>    change msr numbers for kvmclock
>    export paravirtual cpuid flags in KVM_GET_SUPPORTED_CPUID
>    Try using new kvm clock msrs
>    don't compute pvclock adjustments if we trust the tsc
>    Tell the guest we'll warn it about tsc stability
>
>   arch/x86/include/asm/kvm_para.h    |   13 ++++++++
>   arch/x86/include/asm/pvclock-abi.h |    4 ++-
>   arch/x86/include/asm/pvclock.h     |    1 +
>   arch/x86/kernel/kvmclock.c         |   56 ++++++++++++++++++++++-------------
>   arch/x86/kernel/pvclock.c          |   37 +++++++++++++++++++++++
>   arch/x86/kvm/x86.c                 |   37 +++++++++++++++++++++++-
>   6 files changed, 125 insertions(+), 23 deletions(-)
>
>    
Acked-by: Zachary Amsden <zamsden@redhat.com>

I'll rebase on top of these if they get pulled.

And obviously, there is no point in checking for warp if Chuck Norris 
has perished.  I happen to have a special place in my heart for nunchaku 
masters despite the fact that this created a generation of teenagers who 
insisted they were called numb-chucks.

      parent reply	other threads:[~2010-05-05  3:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-03 15:52 [PATCH v2 0/7] Pvclock fixes , version two Glauber Costa
2010-05-03 15:52 ` [PATCH v2 1/7] Enable pvclock flags in vcpu_time_info structure Glauber Costa
2010-05-03 15:52   ` [PATCH v2 2/7] Add a global synchronization point for pvclock Glauber Costa
2010-05-03 15:52     ` [PATCH v2 3/7] change msr numbers for kvmclock Glauber Costa
2010-05-03 15:52       ` [PATCH v2 4/7] export paravirtual cpuid flags in KVM_GET_SUPPORTED_CPUID Glauber Costa
2010-05-03 15:52         ` [PATCH v2 5/7] Try using new kvm clock msrs Glauber Costa
2010-05-03 15:52           ` [PATCH v2 6/7] don't compute pvclock adjustments if we trust the tsc Glauber Costa
2010-05-03 15:52             ` [PATCH v2 7/7] Tell the guest we'll warn it about tsc stability Glauber Costa
2010-05-05  8:28             ` [PATCH v2 6/7] don't compute pvclock adjustments if we trust the tsc Avi Kivity
2010-05-05  8:23         ` [PATCH v2 4/7] export paravirtual cpuid flags in KVM_GET_SUPPORTED_CPUID Avi Kivity
2010-05-05  8:29   ` [PATCH v2 1/7] Enable pvclock flags in vcpu_time_info structure Avi Kivity
2010-05-05  3:57 ` Zachary Amsden [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=4BE0EC9E.3040508@redhat.com \
    --to=zamsden@redhat.com \
    --cc=avi@redhat.com \
    --cc=glommer@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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).