lwn.git/arch/arm64/include/asm/kvm_host.h, branch v5.10-rc2

KVM: arm64: Fix AArch32 handling of DBGD{CCINT,SCRext} and DBGVCR

2020-10-29T19:49:03+00:00

The DBGD{CCINT,SCRext} and DBGVCR register entries in the cp14 array are missing their target register, resulting in all accesses being targetted at the guard sysreg (indexed by __INVALID_SYSREG__). Point the emulation code at the actual register entries. Fixes: bdfb4b389c8d ("arm64: KVM: add trap handlers for AArch32 debug registers") Signed-off-by: Marc Zyngier Cc: stable@vger.kernel.org Link: https://lore.kernel.org/r/20201029172409.2768336-1-maz@kernel.org

Merge branch 'kvm-arm64/hyp-pcpu' into kvmarm-master/next

2020-09-30T13:05:35+00:00

Signed-off-by: Marc Zyngier

Merge remote-tracking branch 'arm64/for-next/ghostbusters' into kvm-arm64/hyp-pcpu

2020-09-30T08:48:30+00:00

Signed-off-by: Marc Zyngier

kvm: arm64: Create separate instances of kvm_host_data for VHE/nVHE

2020-09-30T07:37:13+00:00

Host CPU context is stored in a global per-cpu variable `kvm_host_data`. In preparation for introducing independent per-CPU region for nVHE hyp, create two separate instances of `kvm_host_data`, one for VHE and one for nVHE. Signed-off-by: David Brazdil Signed-off-by: Marc Zyngier Acked-by: Will Deacon Link: https://lore.kernel.org/r/20200922204910.7265-9-dbrazdil@google.com

KVM: arm64: Get rid of kvm_arm_have_ssbd()

2020-09-29T15:08:17+00:00

kvm_arm_have_ssbd() is now completely unused, get rid of it. Signed-off-by: Marc Zyngier Signed-off-by: Will Deacon

arm64: Rewrite Spectre-v2 mitigation code

2020-09-29T15:08:15+00:00

The Spectre-v2 mitigation code is pretty unwieldy and hard to maintain. This is largely due to it being written hastily, without much clue as to how things would pan out, and also because it ends up mixing policy and state in such a way that it is very difficult to figure out what's going on. Rewrite the Spectre-v2 mitigation so that it clearly separates state from policy and follows a more structured approach to handling the mitigation. Signed-off-by: Will Deacon

Merge branch 'kvm-arm64/pmu-5.9' into kvmarm-master/next

2020-09-29T14:12:54+00:00

Signed-off-by: Marc Zyngier

KVM: arm64: Add PMU event filtering infrastructure

2020-09-29T13:19:39+00:00

It can be desirable to expose a PMU to a guest, and yet not want the guest to be able to count some of the implemented events (because this would give information on shared resources, for example. For this, let's extend the PMUv3 device API, and offer a way to setup a bitmap of the allowed events (the default being no bitmap, and thus no filtering). Userspace can thus allow/deny ranges of event. The default policy depends on the "polarity" of the first filter setup (default deny if the filter allows events, and default allow if the filter denies events). This allows to setup exactly what is allowed for a given guest. Note that although the ioctl is per-vcpu, the map of allowed events is global to the VM (it can be setup from any vcpu until the vcpu PMU is initialized). Reviewed-by: Andrew Jones Signed-off-by: Marc Zyngier

KVM: arm64: Use event mask matching architecture revision

2020-09-29T13:19:38+00:00

The PMU code suffers from a small defect where we assume that the event number provided by the guest is always 16 bit wide, even if the CPU only implements the ARMv8.0 architecture. This isn't really problematic in the sense that the event number ends up in a system register, cropping it to the right width, but still this needs fixing. In order to make it work, let's probe the version of the PMU that the guest is going to use. This is done by temporarily creating a kernel event and looking at the PMUVer field that has been saved at probe time in the associated arm_pmu structure. This in turn gets saved in the kvm structure, and subsequently used to compute the event mask that gets used throughout the PMU code. Signed-off-by: Marc Zyngier

Merge branch 'kvm-arm64/nvhe-hyp-context' into kvmarm-master/next

2020-09-16T09:59:17+00:00

Signed-off-by: Marc Zyngier