diff options
| author |   Joerg Roedel <joro@8bytes.org> | 2015-10-14 15:10:54 +0200 |
|---|---|---|
| committer |   Paolo Bonzini <pbonzini@redhat.com> | 2015-10-16 10:32:17 +0200 |
| commit | 6092d3d3e6db983048469d424a8f2221915a8dd3 (patch) | |
| tree | ba6b6b6bc3fc5359267dfe695d7fcd13420b2f22 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | KVM: x86: manually unroll bad_mt_xwr loop (diff) | |
| download | wireguard-linux-6092d3d3e6db983048469d424a8f2221915a8dd3.tar.xz wireguard-linux-6092d3d3e6db983048469d424a8f2221915a8dd3.zip | |
kvm: svm: Only propagate next_rip when guest supports it
Currently we always write the next_rip of the shadow vmcb to
the guests vmcb when we emulate a vmexit. This could confuse
the guest when its cpuid indicated no support for the
next_rip feature.
Fix this by only propagating next_rip if the guest actually
supports it.
Cc: Bandan Das <bsd@redhat.com>
Cc: Dirk Mueller <dmueller@suse.com>
Tested-By: Dirk Mueller <dmueller@suse.com>
Signed-off-by: Joerg Roedel <jroedel@suse.de>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions