From: Avi Kivity <avi@redhat.com>
To: Glauber Costa <glommer@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] expose kvmclock upper msr set.
Date: Mon, 28 Feb 2011 15:30:06 +0200 [thread overview]
Message-ID: <4D6BA35E.6060504@redhat.com> (raw)
In-Reply-To: <1298899495.15736.321.camel@mothafucka.localdomain>
On 02/28/2011 03:24 PM, Glauber Costa wrote:
> On Sun, 2011-02-27 at 14:16 +0200, Avi Kivity wrote:
> > On 02/23/2011 07:44 PM, Glauber Costa wrote:
> > > We've been supporting kvmclock MSRs in the 0x4b564d00-0x4b564dff range
> > > for a while now, but we're not exposing it yet, meaning nobody is using it.
> > > This simple patch takes care of that.
> >
> > We're exposing them via KVM_GET_SUPPORTED_CPUID, leaf KVM_CPUID_FEATURES.
> >
> Our userspace does not really use it, and rely on the capability list.
> Historically, we've been relying on the capabilities mechanism to
> indicate what exists and what does not.
Yes. I believe this bit marked the change point.
Anyway, it's exposed, and it's a lot better for userspace to make use of
KVM_GET_SUPPORTED_CPUID since it will work on more kernels.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-02-28 13:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 17:44 [PATCH] expose kvmclock upper msr set Glauber Costa
2011-02-24 23:24 ` Steven Rostedt
2011-02-24 23:48 ` Glauber Costa
2011-02-24 23:54 ` Steven Rostedt
2011-02-25 13:11 ` Glauber Costa
2011-02-27 9:29 ` Avi Kivity
2011-02-27 12:16 ` Avi Kivity
2011-02-28 13:24 ` Glauber Costa
2011-02-28 13:30 ` Avi Kivity [this message]
2011-02-28 13:30 ` Avi Kivity
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=4D6BA35E.6060504@redhat.com \
--to=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 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.