| commit | 98047888bb9fd57734028c44ec17413ddd623958 | |
| author | Christoffer Dall <christoffer.dall@linaro.org> | |
| Tue, 19 Aug 2014 10:18:04 +0000 (19 12:18 +0200) | ||
| committer | Christoffer Dall <christoffer.dall@linaro.org> | |
| Wed, 27 Aug 2014 20:46:09 +0000 (27 22:46 +0200) | ||
| tree | 976048e835e2f88df23b73aad4e0591102ab8c6e | treesnapshot (tar.gz zip) |
| parent | 64d831269ccbca1fc6d739a0f3c8aa24afb43a5e | commitdiff |
arm/arm64: KVM: Support KVM_CAP_READONLY_MEM
When userspace loads code and data in a read-only memory regions, KVM
needs to be able to handle this on arm and arm64. Specifically this is
used when running code directly from a read-only flash device; the
common scenario is a UEFI blob loaded with the -bios option in QEMU.
Note that the MMIO exit on writes to a read-only memory is ABI and can
be used to emulate block-erase style flash devices.
Acked-by: Marc Zyngier <marc.zyngier@arm.com>
Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
When userspace loads code and data in a read-only memory regions, KVM
needs to be able to handle this on arm and arm64. Specifically this is
used when running code directly from a read-only flash device; the
common scenario is a UEFI blob loaded with the -bios option in QEMU.
Note that the MMIO exit on writes to a read-only memory is ABI and can
be used to emulate block-erase style flash devices.
Acked-by: Marc Zyngier <marc.zyngier@arm.com>
Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
| arch/arm/include/uapi/asm/kvm.h | diffblobblamehistory | |
| arch/arm/kvm/arm.c | diffblobblamehistory | |
| arch/arm/kvm/mmu.c | diffblobblamehistory | |
| arch/arm64/include/uapi/asm/kvm.h | diffblobblamehistory |