diff options
author | Paolo Bonzini <pbonzini@redhat.com> | 2015-05-17 13:58:53 +0200 |
---|---|---|
committer | Paolo Bonzini <pbonzini@redhat.com> | 2015-06-05 17:26:34 +0200 |
commit | 8e73485c7959fd25650761eab04db1e72ea14c23 (patch) | |
tree | 0d320ef4d69626499d4294637f5d833349df8f34 /Documentation/dynamic-debug-howto.txt | |
parent | 660a5d517aaab9187f93854425c4c63f4a09195c (diff) | |
download | talos-obmc-linux-8e73485c7959fd25650761eab04db1e72ea14c23.tar.gz talos-obmc-linux-8e73485c7959fd25650761eab04db1e72ea14c23.zip |
KVM: add vcpu-specific functions to read/write/translate GFNs
We need to hide SMRAM from guests not running in SMM. Therefore, all
uses of kvm_read_guest* and kvm_write_guest* must be changed to use
different address spaces, depending on whether the VCPU is in system
management mode. We need to introduce a new family of functions for
this purpose.
For now, the VCPU-based functions have the same behavior as the
existing per-VM ones, they just accept a different type for the
first argument. Later however they will be changed to use one of many
"struct kvm_memslots" stored in struct kvm, through an architecture hook.
VM-based functions will unconditionally use the first memslots pointer.
Whenever possible, this patch introduces slot-based functions with an
__ prefix, with two wrappers for generic and vcpu-based actions.
The exceptions are kvm_read_guest and kvm_write_guest, which are copied
into the new functions kvm_vcpu_read_guest and kvm_vcpu_write_guest.
Reviewed-by: Radim Krčmář <rkrcmar@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'Documentation/dynamic-debug-howto.txt')
0 files changed, 0 insertions, 0 deletions