diff options
| author | Wanpeng Li <[email protected]> | 2022-04-26 01:25:51 -0700 |
|---|---|---|
| committer | Paolo Bonzini <[email protected]> | 2022-05-25 05:07:09 -0400 |
| commit | e0ac535178ad32c2a4898e2309dcc49ad546e96e (patch) | |
| tree | 6099689e24e37fab4612ef2e949b26424ca71ffa /lib/test_fortify/write_overflow-strlcpy-src.c | |
| parent | 6ba1e04fa60787ced4c9049cf7bd6cd0f1b80764 (diff) | |
KVM: LAPIC: Trace LAPIC timer expiration on every vmentry
In commit ec0671d5684a ("KVM: LAPIC: Delay trace_kvm_wait_lapic_expire
tracepoint to after vmexit", 2019-06-04), trace_kvm_wait_lapic_expire
was moved after guest_exit_irqoff() because invoking tracepoints within
kvm_guest_enter/kvm_guest_exit caused a lockdep splat.
These days this is not necessary, because commit 87fa7f3e98a1 ("x86/kvm:
Move context tracking where it belongs", 2020-07-09) restricted
the RCU extended quiescent state to be closer to vmentry/vmexit.
Moving the tracepoint back to __kvm_wait_lapic_expire is more accurate,
because it will be reported even if vcpu_enter_guest causes multiple
vmentries via the IPI/Timer fast paths, and it allows the removal of
advance_expire_delta.
Signed-off-by: Wanpeng Li <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strlcpy-src.c')
0 files changed, 0 insertions, 0 deletions