diff options
| author | Marc Zyngier <[email protected]> | 2022-09-26 14:51:16 +0000 |
|---|---|---|
| committer | Marc Zyngier <[email protected]> | 2022-09-29 09:23:08 +0000 |
| commit | 17601bfed909fa080fcfd227b57da2bd4dc2d2a6 (patch) | |
| tree | 79e7babcef9a32617591bd2147206b00dab25714 /lib/zstd/common/compiler.h | |
| parent | KVM: Use acquire/release semantics when accessing dirty ring GFN state (diff) | |
| download | kernel-17601bfed909fa080fcfd227b57da2bd4dc2d2a6.tar.gz kernel-17601bfed909fa080fcfd227b57da2bd4dc2d2a6.zip | |
KVM: Add KVM_CAP_DIRTY_LOG_RING_ACQ_REL capability and config option
In order to differenciate between architectures that require no extra
synchronisation when accessing the dirty ring and those who do,
add a new capability (KVM_CAP_DIRTY_LOG_RING_ACQ_REL) that identify
the latter sort. TSO architectures can obviously advertise both, while
relaxed architectures must only advertise the ACQ_REL version.
This requires some configuration symbol rejigging, with HAVE_KVM_DIRTY_RING
being only indirectly selected by two top-level config symbols:
- HAVE_KVM_DIRTY_RING_TSO for strongly ordered architectures (x86)
- HAVE_KVM_DIRTY_RING_ACQ_REL for weakly ordered architectures (arm64)
Suggested-by: Paolo Bonzini <[email protected]>
Signed-off-by: Marc Zyngier <[email protected]>
Reviewed-by: Gavin Shan <[email protected]>
Reviewed-by: Peter Xu <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'lib/zstd/common/compiler.h')
0 files changed, 0 insertions, 0 deletions