diff options
| author | Sean Christopherson <seanjc@google.com> | 2026-06-30 15:56:18 -0700 |
|---|---|---|
| committer | Sean Christopherson <seanjc@google.com> | 2026-07-08 13:41:14 -0700 |
| commit | 09dd4de361dcb60a4097a4483d0203954c9755c3 (patch) | |
| tree | 08a4bb19427ee1cfc8561693b1ba651624184f5c /tools/perf/scripts/python/task-analyzer.py | |
| parent | 53ce2c773f0007bd3c74deb45049e152fcd88f2f (diff) | |
KVM: x86/hyperv: Use {READ,WRITE}_ONCE for cross-task synic->active accesses
When activating Hyper-V's Synthetic Interrupt Controller (SynIC), mark it
active with WRITE_ONCE() and query it using READ_ONCE() in synic_get(),
the only known cross-task reader, to document that the flag is accessed
without holding the vCPU's mutex.
Note, there are no data dependencies on the SynIC being marked active,
e.g. the vector read by synic_set_irq() is set (usually in response to
guest activity) long after the SynIC is initially activated, and a false
negative on the SynIC being active would be benign (ignoring that such a
race is likely to be problematic for the guest irrespective of what KVM
does).
Link: https://patch.msgid.link/20260630225619.511632-12-seanjc@google.com
Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'tools/perf/scripts/python/task-analyzer.py')
0 files changed, 0 insertions, 0 deletions
