On Thu, Aug 14, 2014 at 04:46:20PM +0100, Marc Zyngier wrote:
On Thu, Jul 10 2014 at 3:42:31 pm BST, Christoffer Dall
christoffer.d...@linaro.org wrote:
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
On 15 August 2014 10:15, Christoffer Dall christoffer.d...@linaro.org wrote:
On Thu, Aug 14, 2014 at 04:46:20PM +0100, Marc Zyngier wrote:
So the consequence of a write to a ROM region would be to do an IO
emulation? That seems a bit weird. Shouldn't we have a separate error
path for this
On Fri, Aug 15 2014 at 10:15:50 am BST, Christoffer Dall
christoffer.d...@linaro.org wrote:
On Thu, Aug 14, 2014 at 04:46:20PM +0100, Marc Zyngier wrote:
On Thu, Jul 10 2014 at 3:42:31 pm BST, Christoffer Dall
christoffer.d...@linaro.org wrote:
When userspace loads code and data in a
On Thu, Jul 10 2014 at 3:42:31 pm BST, Christoffer Dall
christoffer.d...@linaro.org wrote:
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
On Thu, Jul 10, 2014 at 07:42:31AM -0700, Christoffer Dall wrote:
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
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.
To avoid looking
