Hi Fuad,
On 2022-05-10 10:57, Fuad Tabba wrote:
Hi,
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).
In the future, please don't do that. *Always* base your patches
on something stable (preferably an early -rc, as I usually start
pulling stuff in around -rc3).
kvmarm/next is a moving target, and basing things on top of it
results in an uncontrolled dependency chain. If your series depends
on something and makes it impossible to base your patches on an rc,
please state so (this isn't the case here).
Thanks,
M.
--
Jazz is not dead. It just smells funny...
_______________________________________________
kvmarm mailing list
kvmarm@xxxxxxxxxxxxxxxxxxxxx
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
