diff options
| author | Marc Zyngier <[email protected]> | 2023-06-07 15:38:44 +0100 |
|---|---|---|
| committer | Marc Zyngier <[email protected]> | 2023-06-07 16:38:25 +0100 |
| commit | 1caa71a7a600f7781ce05ef1e84701c459653663 (patch) | |
| tree | 792606cd47251d79e7568a6131c2e6a4384af9ed /scripts/bpf_doc.py | |
| parent | 0c2f9acf6ae74118385f7a7d48f4b2d93637b628 (diff) | |
KVM: arm64: Restore GICv2-on-GICv3 functionality
When reworking the vgic locking, the vgic distributor registration
got simplified, which was a very good cleanup. But just a tad too
radical, as we now register the *native* vgic only, ignoring the
GICv2-on-GICv3 that allows pre-historic VMs (or so I thought)
to run.
As it turns out, QEMU still defaults to GICv2 in some cases, and
this breaks Nathan's setup!
Fix it by propagating the *requested* vgic type rather than the
host's version.
Fixes: 59112e9c390b ("KVM: arm64: vgic: Fix a circular locking issue")
Reported-by: Nathan Chancellor <[email protected]>
Tested-by: Nathan Chancellor <[email protected]>
Signed-off-by: Marc Zyngier <[email protected]>
link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'scripts/bpf_doc.py')
0 files changed, 0 insertions, 0 deletions