From: Avi Kivity <avi@redhat.com>
To: Glauber Costa <glommer@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, zamsden@redhat.com
Subject: Re: [PATCH 0/9] pvclock misc fixes - v4.
Date: Tue, 11 May 2010 21:25:04 +0300 [thread overview]
Message-ID: <4BE9A100.1060207@redhat.com> (raw)
In-Reply-To: <1273594667-17175-1-git-send-email-glommer@redhat.com>
On 05/11/2010 07:17 PM, 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.
>
Looks good.
> As a side effect, this patch removes the time-travel feature
> in kvm guests.
>
Too many reports of users accidentally killing their grandparents anyway.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2010-05-11 18:25 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 ` Avi Kivity [this message]
2010-05-12 3:33 ` [PATCH 0/9] pvclock misc fixes - v4 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
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=4BE9A100.1060207@redhat.com \
--to=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).