summaryrefslogtreecommitdiff
path: root/Makefile.am
AgeCommit message (Expand)AuthorFilesLines
2006-11-13Initial import15.6-2Tobias Klauser1-0/+6
> authorMarc Zyngier <marc.zyngier@arm.com>2016-05-25 15:26:38 +0100 committerChristoffer Dall <christoffer.dall@linaro.org>2016-05-31 16:12:17 +0200 commita057001e9e446f2195c34bc55c57e5cf353c99d6 (patch) tree82f88a4890ffae9c4555e898b2e3ac8964c0b547 parentb34f2bcbf59fe2d27c37d6553c33611754677103 (diff)
arm64: KVM: vgic-v3: Prevent the guest from messing with ICC_SRE_EL1
Both our GIC emulations are "strict", in the sense that we either emulate a GICv2 or a GICv3, and not a GICv3 with GICv2 legacy support. But when running on a GICv3 host, we still allow the guest to tinker with the ICC_SRE_EL1 register during its time slice: it can switch SRE off, observe that it is off, and yet on the next world switch, find the SRE bit to be set again. Not very nice. An obvious solution is to always trap accesses to ICC_SRE_EL1 (by clearing ICC_SRE_EL2.Enable), and to let the handler return the programmed value on a read, or ignore the write. That way, the guest can always observe that our GICv3 is SRE==1 only. Reviewed-by: Christoffer Dall <christoffer.dall@linaro.org> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com> Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
Diffstat