diff options
author | Marc Zyngier <marc.zyngier@arm.com> | 2014-07-08 12:09:04 +0100 |
---|---|---|
committer | Christoffer Dall <christoffer.dall@linaro.org> | 2014-09-18 18:48:57 -0700 |
commit | c3c918361adcceb816c92b21dd95d2b46fb96a8f (patch) | |
tree | 055024f1f93ec5fce6851aac87f9f22bb79a0a4d /fs | |
parent | fc675e355e705a046df7b635d3f3330c0ad94569 (diff) | |
download | linux-stable-c3c918361adcceb816c92b21dd95d2b46fb96a8f.tar.gz linux-stable-c3c918361adcceb816c92b21dd95d2b46fb96a8f.tar.bz2 linux-stable-c3c918361adcceb816c92b21dd95d2b46fb96a8f.zip |
arm/arm64: KVM: vgic: handle out-of-range MMIO accesses
Now that we can (almost) dynamically size the number of interrupts,
we're facing an interesting issue:
We have to evaluate at runtime whether or not an access hits a valid
register, based on the sizing of this particular instance of the
distributor. Furthermore, the GIC spec says that accessing a reserved
register is RAZ/WI.
For this, add a new field to our range structure, indicating the number
of bits a single interrupts uses. That allows us to find out whether or
not the access is in range.
Reviewed-by: Christoffer Dall <christoffer.dall@linaro.org>
Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions