diff options
| author | Marc Zyngier <maz@kernel.org> | 2026-04-14 17:05:28 +0100 |
|---|---|---|
| committer | Marc Zyngier <maz@kernel.org> | 2026-04-18 09:07:13 +0100 |
| commit | f05799491d6a2a29d8e15f4451e685c4a6e13d8f (patch) | |
| tree | e04a4f0dcc9c234182800369e19e2b5b0e2c0c98 /scripts/dummy-tools/python3 | |
| parent | ccab51d69b1478b549ad0bbb38f556ab3bfb47ab (diff) | |
KVM: arm64: pkvm: Adopt MARKER() to define host hypercall ranges
The EL2 code defines ranges of host hypercalls that are either
enabled at boot-time only, used by [nh]VHE KVM, or reserved to pKVM.
The way these ranges are delineated is error prone, as the enum symbols
defining the limits are expressed in terms of actual function symbols.
This means that should a new function be added, special care must be
taken to also update the limit symbol.
Improve this by reusing the mechanism introduced for the vcpu_sysreg
enum, which uses a MARKER() macro and some extra trickery to make
the limit symbol standalone. Crucially, the limit symbol has the
same value as the *following* symbol.
The handle_host_hcall() function is then updated to make use of
the new limit definitions and get rid of the brittle default
upper limit. This allows for some more strict checks at build
time, and the removal of an comparison at run time.
Tested-by: Fuad Tabba <tabba@google.com>
Reviewed-by: Fuad Tabba <tabba@google.com>
Link: https://patch.msgid.link/20260414160528.2218858-1-maz@kernel.org
Signed-off-by: Marc Zyngier <maz@kernel.org>
Diffstat (limited to 'scripts/dummy-tools/python3')
0 files changed, 0 insertions, 0 deletions
