diff options
| author | Sean Christopherson <[email protected]> | 2024-10-01 05:00:44 +0000 |
|---|---|---|
| committer | Sean Christopherson <[email protected]> | 2025-02-25 15:23:07 +0000 |
| commit | b50cb2b1555d8714e12a566b9b49fcac56a04a3f (patch) | |
| tree | 08676d48c466cbf38e0f0528cbf9c26d80339d53 /tools/testing/selftests/net/lib/py/utils.py | |
| parent | KVM: x86: Rename and invert async #PF's send_user_only flag to send_always (diff) | |
| download | kernel-b50cb2b1555d8714e12a566b9b49fcac56a04a3f.tar.gz kernel-b50cb2b1555d8714e12a566b9b49fcac56a04a3f.zip | |
KVM: x86: Use a dedicated flow for queueing re-injected exceptions
Open code the filling of vcpu->arch.exception in kvm_requeue_exception()
instead of bouncing through kvm_multiple_exception(), as re-injection
doesn't actually share that much code with "normal" injection, e.g. the
VM-Exit interception check, payload delivery, and nested exception code
is all bypassed as those flows only apply during initial injection.
When FRED comes along, the special casing will only get worse, as FRED
explicitly tracks nested exceptions and essentially delivers the payload
on the stack frame, i.e. re-injection will need more inputs, and normal
injection will have yet more code that needs to be bypassed when KVM is
re-injecting an exception.
No functional change intended.
Signed-off-by: Xin Li (Intel) <[email protected]>
Tested-by: Shan Kang <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Sean Christopherson <[email protected]>
Diffstat (limited to 'tools/testing/selftests/net/lib/py/utils.py')
0 files changed, 0 insertions, 0 deletions