summaryrefslogtreecommitdiff
path: root/kernel
diff options
context:
space:
mode:
authorPaolo Bonzini <pbonzini@redhat.com>2026-04-27 04:24:34 -0400
committerPaolo Bonzini <pbonzini@redhat.com>2026-04-27 04:24:34 -0400
commit909eac682c984c3cb02485d5950c2a8d573c1667 (patch)
tree87c3b8f221ff4b5dfd2e8658a532a26a7234078c /kernel
parent1101baca98669833fb3ad2dcd24bc06f9e70e66b (diff)
parent4ce98bf0865c349e7026ad9c14f48da264920953 (diff)
Merge tag 'kvmarm-fixes-7.1-1' of git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm into HEAD
KVM/arm64 fixes for 7.1, take #1 - Allow tracing for non-pKVM, which was accidentally disabled when the series was merged - Rationalise the way the pKVM hypercall ranges are defined by using the same mechanism as already used for the vcpu_sysreg enum - Enforce that SMCCC function numbers relayed by the pKVM proxy are actually compliant with the specification - Fix a couple of feature to idreg mappings which resulted in the wrong sanitisation being applied - Fix the GICD_IIDR revision number field that could never been written correctly by userspace - Make kvm_vcpu_initialized() correctly use its parameter instead of relying on the surrounding context - Enforce correct ordering in __pkvm_init_vcpu(), plugging a potential pin leak at the same time - Move __pkvm_init_finalise() to a less dangerous spot, avoiding future problems - Restore functional userspace irqchip support after a four year breakage (last functional kernel was 5.18...). This is obviously ripe for garbage collection. - ... and the usual lot of spelling fixes
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions