diff options
author | 2019-12-18 13:54:52 -0800 | |
---|---|---|
committer | 2020-01-24 09:18:55 +0100 | |
commit | a9dd6f09d7e54d3f58be32d7d051196f7a00e69e (patch) | |
tree | 5878449542dac778cd20368045b5f693d86821df /tools/perf/scripts/python/mem-phys-addr.py | |
parent | KVM: SVM: Use direct vcpu pointer during vCPU create/free (diff) | |
download | linux-dev-a9dd6f09d7e54d3f58be32d7d051196f7a00e69e.tar.xz linux-dev-a9dd6f09d7e54d3f58be32d7d051196f7a00e69e.zip |
KVM: x86: Allocate vcpu struct in common x86 code
Move allocation of VMX and SVM vcpus to common x86. Although the struct
being allocated is technically a VMX/SVM struct, it can be interpreted
directly as a 'struct kvm_vcpu' because of the pre-existing requirement
that 'struct kvm_vcpu' be located at offset zero of the arch/vendor vcpu
struct.
Remove the message from the build-time assertions regarding placement of
the struct, as compatibility with the arch usercopy region is no longer
the sole dependent on 'struct kvm_vcpu' being at offset zero.
Signed-off-by: Sean Christopherson <sean.j.christopherson@intel.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/mem-phys-addr.py')
0 files changed, 0 insertions, 0 deletions