diff options
author | Jing Zhang <[email protected]> | 2023-10-03 23:03:57 +0000 |
---|---|---|
committer | Oliver Upton <[email protected]> | 2023-10-04 17:09:39 +0000 |
commit | 3f9cd0ca848413fd368278310d2cdd6c2bef48b2 (patch) | |
tree | 265822519f53eb381120bb0ec40ab905dd558033 /lib/test_fortify/write_overflow-memset.c | |
parent | 6465e260f48790807eef06b583b38ca9789b6072 (diff) |
KVM: arm64: Allow userspace to get the writable masks for feature ID registers
While the Feature ID range is well defined and pretty large, it isn't
inconceivable that the architecture will eventually grow some other
ranges that will need to similarly be described to userspace.
Add a VM ioctl to allow userspace to get writable masks for feature ID
registers in below system register space:
op0 = 3, op1 = {0, 1, 3}, CRn = 0, CRm = {0 - 7}, op2 = {0 - 7}
This is used to support mix-and-match userspace and kernels for writable
ID registers, where userspace may want to know upfront whether it can
actually tweak the contents of an idreg or not.
Add a new capability (KVM_CAP_ARM_SUPPORTED_FEATURE_ID_RANGES) that
returns a bitmap of the valid ranges, which can subsequently be
retrieved, one at a time by setting the index of the set bit as the
range identifier.
Suggested-by: Marc Zyngier <[email protected]>
Suggested-by: Cornelia Huck <[email protected]>
Signed-off-by: Jing Zhang <[email protected]>
Reviewed-by: Cornelia Huck <[email protected]>
Reviewed-by: Marc Zyngier <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Oliver Upton <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-memset.c')
0 files changed, 0 insertions, 0 deletions