diff options
author | Sean Christopherson <seanjc@google.com> | 2022-11-19 01:34:50 +0000 |
---|---|---|
committer | Paolo Bonzini <pbonzini@redhat.com> | 2022-12-02 13:22:35 -0500 |
commit | bb056c0f080a3d15c2a9ad9057a8b542d45e4ba0 (patch) | |
tree | a7231d2f04e11798c35e848bcfbddb4db0bc098b /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | 36293352ff433061d45d52784983e44950c09ae3 (diff) |
tools: KVM: selftests: Convert clear/set_bit() to actual atomics
Convert {clear,set}_bit() to atomics as KVM's ucall implementation relies
on clear_bit() being atomic, they are defined in atomic.h, and the same
helpers in the kernel proper are atomic.
KVM's ucall infrastructure is the only user of clear_bit() in tools/, and
there are no true set_bit() users. tools/testing/nvdimm/ does make heavy
use of set_bit(), but that code builds into a kernel module of sorts, i.e.
pulls in all of the kernel's header and so is already getting the kernel's
atomic set_bit().
Signed-off-by: Sean Christopherson <seanjc@google.com>
Message-Id: <20221119013450.2643007-10-seanjc@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions