diff options
author | Sean Christopherson <sean.j.christopherson@intel.com> | 2019-08-27 14:40:38 -0700 |
---|---|---|
committer | Paolo Bonzini <pbonzini@redhat.com> | 2019-09-24 14:34:00 +0200 |
commit | 60fc3d02d5b8829b91b7b443ef6c7e8f0bbae868 (patch) | |
tree | 76d02e255b881d3e21b7ab872fdf854a2626796a /Documentation/w1/slaves | |
parent | 8fff2710eaf50aff1e6a7aa0607fe5288b619404 (diff) | |
download | linux-60fc3d02d5b8829b91b7b443ef6c7e8f0bbae868.tar.bz2 |
KVM: x86: Remove emulation_result enums, EMULATE_{DONE,FAIL,USER_EXIT}
Deferring emulation failure handling (in some cases) to the caller of
x86_emulate_instruction() has proven fragile, e.g. multiple instances of
KVM not setting run->exit_reason on EMULATE_FAIL, largely due to it
being difficult to discern what emulation types can return what result,
and which combination of types and results are handled where.
Now that x86_emulate_instruction() always handles emulation failure,
i.e. EMULATION_FAIL is only referenced in callers, remove the
emulation_result enums entirely. Per KVM's existing exit handling
conventions, return '0' and '1' for "exit to userspace" and "resume
guest" respectively. Doing so cleans up many callers, e.g. they can
return kvm_emulate_instruction() directly instead of having to interpret
its result.
Signed-off-by: Sean Christopherson <sean.j.christopherson@intel.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'Documentation/w1/slaves')
0 files changed, 0 insertions, 0 deletions