diff options
| author | Jan Kiszka <jan.kiszka@siemens.com> | 2015-03-09 20:27:43 +0100 |
|---|---|---|
| committer | Marcelo Tosatti <mtosatti@redhat.com> | 2015-03-13 13:27:54 -0300 |
| commit | b34a80517bfcd917bc59d9670d8f465a564af3b9 (patch) | |
| tree | 62ef3413dcba6273b8e59c892308ef8c5292e29c /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | 5e57518d99725e8b4ee34cc94669afb79e4cfe4e (diff) | |
KVM: x86: Fix re-execution of patched vmmcall
For a very long time (since 2b3d2a20), the path handling a vmmcall
instruction of the guest on an Intel host only applied the patch but no
longer handled the hypercall. The reverse case, vmcall on AMD hosts, is
fine. As both em_vmcall and em_vmmcall actually have to do the same, we
can fix the issue by consolidating both into the same handler.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions