From: "Michael S. Tsirkin" <mst@redhat.com>
To: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>
Cc: Gleb Natapov <gleb@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, Rob Landley <rob@landley.net>,
mtosatti@redhat.com
Subject: Re: [PATCH V2] Documentation/kvm: Update cpuid documentation for steal time and pv eoi
Date: Thu, 12 Sep 2013 08:44:53 +0300 [thread overview]
Message-ID: <20130912054453.GA13116@redhat.com> (raw)
In-Reply-To: <1378284526-863-1-git-send-email-raghavendra.kt@linux.vnet.ibm.com>
On Wed, Sep 04, 2013 at 02:18:46PM +0530, Raghavendra K T wrote:
> Signed-off-by: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>
> ---
> Changes in V2:
> Correction in the description of steal time and added msr info (Michael S Tsirkin)
Thanks. Some comments below:
> Documentation/virtual/kvm/cpuid.txt | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/Documentation/virtual/kvm/cpuid.txt b/Documentation/virtual/kvm/cpuid.txt
> index 22ff659..6c4fb20 100644
> --- a/Documentation/virtual/kvm/cpuid.txt
> +++ b/Documentation/virtual/kvm/cpuid.txt
> @@ -43,6 +43,16 @@ KVM_FEATURE_CLOCKSOURCE2 || 3 || kvmclock available at msrs
> KVM_FEATURE_ASYNC_PF || 4 || async pf can be enabled by
> || || writing to msr 0x4b564d02
> ------------------------------------------------------------------------------
> +KVM_FEATURE_STEAL_TIME || 5 || Steal time available at msr
> + || || 0x4b564d03. The feature is enabled
> + || || by guest when host has schedstat
> + || || or task delay accounting support.
Well I think we really should be documenting the host/guest interface
here.
After all it starts out
A guest running on a kvm host, can check some of its features using
cpuid.
And guests really should not try to guess whether host
has schedstat or task delay accounting support based on this bit.
So I would just say:
"steal time can be enabled by writing to msr 0x4b564d02"
just like async pf.
> +------------------------------------------------------------------------------
> +KVM_FEATURE_PV_EOI || 6 || overrides the generic EOI
> + || || implementation with a
> + || || paravirtualized version. Available
> + || || at msr 0x4b564d04.
Actually there's no override: guest can still use the
standard EOI even if PV EOI MSR is enabled.
There's a detailed explanation of PV EOI in
Documentation/virtual/kvm/msr.txt
I think the following would be enough:
"paravirtualized end of interrupt handler can be enabled by writing to msr 0x4b564d04"
> +------------------------------------------------------------------------------
> KVM_FEATURE_PV_UNHALT || 7 || guest checks this feature bit
> || || before enabling paravirtualized
> || || spinlock support.
> --
> 1.7.11.7
next prev parent reply other threads:[~2013-09-12 5:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 8:48 [PATCH V2] Documentation/kvm: Update cpuid documentation for steal time and pv eoi Raghavendra K T
2013-09-12 5:21 ` Raghavendra K T
2013-09-12 5:44 ` Michael S. Tsirkin [this message]
2013-09-12 7:10 ` Raghavendra K T
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=20130912054453.GA13116@redhat.com \
--to=mst@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=raghavendra.kt@linux.vnet.ibm.com \
--cc=rob@landley.net \
/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