On Tue, 10 May 2022 09:57:06 +0000, Fuad Tabba wrote:
> This series changes the way KVM communicates host pmu event changes to the
> hypervisor in nvhe and protected mode. Instead of accessing hyp data directly
> from the host, the data is passed to hyp via the loaded vcpu. This provides
> more isolation between the host and the hypervisor, and allows us to use pmu in
> protected mode.
>
> This series is based on kvmarm/next (8c22fd2d4cfa).
>
> [...]
Applied to next, thanks!
[1/4] KVM: arm64: Wrapper for getting pmu_events
commit: 3cb8a091a7016be0ee5420ff6c1928972e3ce23e
[2/4] KVM: arm64: Repack struct kvm_pmu to reduce size
commit: e987a4c60f9755b2f7a19bf1b5ef2eb74c90579b
[3/4] KVM: arm64: Pass pmu events to hyp via vcpu
commit: 84d751a019a9792f5b4884e1d598b603c360ec22
[4/4] KVM: arm64: Reenable pmu in Protected Mode
commit: 722625c6f4c5b6a9953d6af04c7bb1a6e12830b3
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
kvmarm mailing list
kvmarm@xxxxxxxxxxxxxxxxxxxxx
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
