kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Glauber Costa <glommer@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	avi@redhat.com, zamsden@redhat.com
Subject: Re: [PATCH 0/9] pvclock misc fixes - v4.
Date: Wed, 12 May 2010 17:33:52 -0300	[thread overview]
Message-ID: <20100512203352.GA19423@amt.cnet> (raw)
In-Reply-To: <1273594667-17175-1-git-send-email-glommer@redhat.com>

On Tue, May 11, 2010 at 12:17:38PM -0400, Glauber Costa wrote:
> This is the fourth version ov kvmclock fixes.
> 
> Just two minor changes in patch 5, per avi request, and
> the addition of cpuid.txt file, documenting all cpuid flags
> we use.
> 
> As a side effect, this patch removes the time-travel feature
> in kvm guests.
> 
> Glauber Costa (9):
>   Enable pvclock flags in vcpu_time_info structure
>   Add a global synchronization point for pvclock
>   change msr numbers for kvmclock
>   add new KVMCLOCK cpuid feature
>   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
>   Add cpuid.txt file
> 
>  Documentation/kvm/cpuid.txt        |   44 ++++++++++++++++++++++++++++
>  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                 |   44 +++++++++++++++++++++++++++-
>  7 files changed, 176 insertions(+), 23 deletions(-)
>  create mode 100644 Documentation/kvm/cpuid.txt

Applied all, thanks.


      parent reply	other threads:[~2010-05-12 20:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-11 16:17 [PATCH 0/9] pvclock misc fixes - v4 Glauber Costa
2010-05-11 16:17 ` [PATCH 1/9] Enable pvclock flags in vcpu_time_info structure Glauber Costa
2010-05-11 16:17   ` [PATCH 2/9] Add a global synchronization point for pvclock Glauber Costa
2010-05-11 16:17     ` [PATCH 3/9] change msr numbers for kvmclock Glauber Costa
2010-05-11 16:17       ` [PATCH 4/9] add new KVMCLOCK cpuid feature Glauber Costa
2010-05-11 16:17         ` [PATCH 5/9] export paravirtual cpuid flags in KVM_GET_SUPPORTED_CPUID Glauber Costa
2010-05-11 16:17           ` [PATCH 6/9] Try using new kvm clock msrs Glauber Costa
2010-05-11 16:17             ` [PATCH 7/9] don't compute pvclock adjustments if we trust the tsc Glauber Costa
2010-05-11 16:17               ` [PATCH 8/9] Tell the guest we'll warn it about tsc stability Glauber Costa
2010-05-11 16:17                 ` [PATCH 9/9] Add cpuid.txt file Glauber Costa
2010-05-11 18:25 ` [PATCH 0/9] pvclock misc fixes - v4 Avi Kivity
2010-05-12  3:33 ` Zachary Amsden
2010-05-12  5:47   ` Alexander Graf
2010-05-12  6:33     ` Avi Kivity
2010-05-12  6:35       ` Alexander Graf
2010-05-12 17:04     ` Glauber Costa
2010-05-12 20:33 ` Marcelo Tosatti [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=20100512203352.GA19423@amt.cnet \
    --to=mtosatti@redhat.com \
    --cc=avi@redhat.com \
    --cc=glommer@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zamsden@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).