diff options
| author | Marc Zyngier <maz@kernel.org> | 2025-11-20 17:25:17 +0000 |
|---|---|---|
| committer | Oliver Upton <oupton@kernel.org> | 2025-11-24 14:29:13 -0800 |
| commit | 3cfd59f81e0f3fbdf8a1b2f576bdc63ab6cc3277 (patch) | |
| tree | 5d93f1e53e7a707c979f0ba7ac70a0f495cead86 /scripts/generate_rust_analyzer.py | |
| parent | a69e2d6f8934bdb9d08a6740ca6c7a44525e2e95 (diff) | |
KVM: arm64: GICv3: Handle LR overflow when EOImode==0
Now that we can identify interrupts that have not made it into the LRs,
it becomes relatively easy to use EOIcount to walk the overflow list.
What is a bit odd is that we compute a fake LR for the original
state of the interrupt, clear the active bit, and feed into the existing
logic for processing. In a way, this is what would have happened if
the interrupt was in an LR.
Tested-by: Fuad Tabba <tabba@google.com>
Signed-off-by: Marc Zyngier <maz@kernel.org>
Tested-by: Mark Brown <broonie@kernel.org>
Link: https://msgid.link/20251120172540.2267180-28-maz@kernel.org
Signed-off-by: Oliver Upton <oupton@kernel.org>
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions
