diff options
author | Marc Zyngier <marc.zyngier@arm.com> | 2017-10-27 16:28:53 +0200 |
---|---|---|
committer | Christoffer Dall <christoffer.dall@linaro.org> | 2017-11-10 09:45:02 +0100 |
commit | d3d83f7fef9dfa8bf5a279497dcaa3dd690bce2f (patch) | |
tree | c13c5b6350df78d55e2f663cd7b8c5f6b0c1c053 /.gitattributes | |
parent | KVM: arm/arm64: GICv4: Prevent a VM using GICv4 from being saved (diff) | |
download | linux-d3d83f7fef9dfa8bf5a279497dcaa3dd690bce2f.tar.xz linux-d3d83f7fef9dfa8bf5a279497dcaa3dd690bce2f.zip |
KVM: arm/arm64: GICv4: Prevent userspace from changing doorbell affinity
We so far allocate the doorbell interrupts without taking any
special measure regarding the affinity of these interrupts. We
simply move them around as required when the vcpu gets scheduled
on a different CPU.
But that's counting without userspace (and the evil irqbalance) that
can try and move the VPE interrupt around, causing the ITS code
to emit VMOVP commands and remap the doorbell to another redistributor.
Worse, this can happen while the vcpu is running, causing all kind
of trouble if the VPE is already resident, and we end-up in UNPRED
territory.
So let's take a definitive action and prevent userspace from messing
with us. This is just a matter of adding IRQ_NO_BALANCING to the
set of flags we already have, letting the kernel in sole control
of the affinity.
Acked-by: Christoffer Dall <christoffer.dall@linaro.org>
Reviewed-by: Eric Auger <eric.auger@redhat.com>
Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
Diffstat (limited to '.gitattributes')
0 files changed, 0 insertions, 0 deletions