Re: [PATCH] arm/arm64: KVM: Support KVM_CAP_READONLY_MEM

2014-08-15 Thread Marc Zyngier
On Fri, Aug 15 2014 at 10:15:50 am BST, Christoffer Dall 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 >> wrote: >> > When userspace loads code and data in a read-only memory regions, KVM >> > needs to be able to

Re: [PATCH] arm/arm64: KVM: Support KVM_CAP_READONLY_MEM

2014-08-15 Thread Peter Maydell
On 15 August 2014 10:15, Christoffer Dall 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 (possibly ignoring the wr

Re: [PATCH] arm/arm64: KVM: Support KVM_CAP_READONLY_MEM

2014-08-15 Thread Christoffer Dall
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 > 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 run

Re: [PATCH] arm/arm64: KVM: Support KVM_CAP_READONLY_MEM

2014-08-14 Thread Marc Zyngier
On Thu, Jul 10 2014 at 3:42:31 pm BST, 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

Re: [PATCH] arm/arm64: KVM: Support KVM_CAP_READONLY_MEM

2014-08-04 Thread Christoffer Dall
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