Documentation: virtual: kvm: correct one bit description in APF case
When commit 6adba52742
(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>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
This commit is contained in:
parent
16f8a6f979
commit
91690bf32e
|
@ -168,7 +168,7 @@ MSR_KVM_ASYNC_PF_EN: 0x4b564d02
|
||||||
64 byte memory area which must be in guest RAM and must be
|
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
|
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
|
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.
|
when vcpu is in cpl == 0.
|
||||||
|
|
||||||
First 4 byte of 64 byte memory location will be written to by
|
First 4 byte of 64 byte memory location will be written to by
|
||||||
|
|
Loading…
Reference in New Issue