All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Tiejun Chen <tiejun.chen@intel.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] Documentation: virtual: kvm: correct one bit description in APF case
Date: Sat, 11 Oct 2014 06:08:25 +0200	[thread overview]
Message-ID: <5438AD39.9080307@redhat.com> (raw)
In-Reply-To: <1412990394-7948-1-git-send-email-tiejun.chen@intel.com>

Il 11/10/2014 03:19, Tiejun Chen ha scritto:
> When commit 6adba5274206 (KVM: Let host know whether the guest can
> handle async PF in non-userspace context.) is introduced, actually
> bit 2 still is reserved and should be zero. Instead, bit 1 is 1 to
> indicate if asynchronous page faults can be injected when vcpu is
> in cpl == 0, and also please see this,
> 
> in the file kvm_para.h, #define KVM_ASYNC_PF_SEND_ALWAYS (1 << 1).
> 
> Signed-off-by: Tiejun Chen <tiejun.chen@intel.com>
> ---
>  Documentation/virtual/kvm/msr.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/virtual/kvm/msr.txt b/Documentation/virtual/kvm/msr.txt
> index 6d470ae..2a71c8f 100644
> --- a/Documentation/virtual/kvm/msr.txt
> +++ b/Documentation/virtual/kvm/msr.txt
> @@ -168,7 +168,7 @@ MSR_KVM_ASYNC_PF_EN: 0x4b564d02
>  	64 byte memory area which must be in guest RAM and must be
>  	zeroed. Bits 5-2 are reserved and should be zero. Bit 0 is 1
>  	when asynchronous page faults are enabled on the vcpu 0 when
> -	disabled. Bit 2 is 1 if asynchronous page faults can be injected
> +	disabled. Bit 1 is 1 if asynchronous page faults can be injected
>  	when vcpu is in cpl == 0.
>  
>  	First 4 byte of 64 byte memory location will be written to by
> 

Thanks, applying locally.

Paolo

      reply	other threads:[~2014-10-11  4:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-11  1:19 [PATCH] Documentation: virtual: kvm: correct one bit description in APF case Tiejun Chen
2014-10-11  4:08 ` Paolo Bonzini [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=5438AD39.9080307@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=tiejun.chen@intel.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 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.