On 18/09/12 22:53, Christoffer Dall wrote:
On Tue, Sep 18, 2012 at 5:04 PM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
On Sat, Sep 15, 2012 at 11:34:36AM -0400, Christoffer Dall wrote:
From: Marc Zyngier marc.zyng...@arm.com
The KVM hypervisor mmu code requires access to the
On Thu, Sep 20, 2012 at 6:01 AM, Marc Zyngier marc.zyng...@arm.com wrote:
On 18/09/12 22:53, Christoffer Dall wrote:
On Tue, Sep 18, 2012 at 5:04 PM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
On Sat, Sep 15, 2012 at 11:34:36AM -0400, Christoffer Dall wrote:
From: Marc Zyngier
On Sat, Sep 15, 2012 at 04:34:36PM +0100, Christoffer Dall wrote:
From: Marc Zyngier marc.zyng...@arm.com
The KVM hypervisor mmu code requires access to the mem_type prot_pte
field when setting up page tables pointing to a device. Unfortunately,
the mem_type structure is opaque.
Add an
On Tue, Sep 18, 2012 at 8:23 AM, Will Deacon will.dea...@arm.com wrote:
On Sat, Sep 15, 2012 at 04:34:36PM +0100, Christoffer Dall wrote:
From: Marc Zyngier marc.zyng...@arm.com
The KVM hypervisor mmu code requires access to the mem_type prot_pte
field when setting up page tables pointing to
On Sat, Sep 15, 2012 at 11:34:36AM -0400, Christoffer Dall wrote:
From: Marc Zyngier marc.zyng...@arm.com
The KVM hypervisor mmu code requires access to the mem_type prot_pte
field when setting up page tables pointing to a device. Unfortunately,
the mem_type structure is opaque.
Add an
On Tue, Sep 18, 2012 at 5:04 PM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
On Sat, Sep 15, 2012 at 11:34:36AM -0400, Christoffer Dall wrote:
From: Marc Zyngier marc.zyng...@arm.com
The KVM hypervisor mmu code requires access to the mem_type prot_pte
field when setting up page
From: Marc Zyngier marc.zyng...@arm.com
The KVM hypervisor mmu code requires access to the mem_type prot_pte
field when setting up page tables pointing to a device. Unfortunately,
the mem_type structure is opaque.
Add an accessor (get_mem_type_prot_pte()) to retrieve the prot_pte
value.