On Tue, Jul 02, 2013 at 11:15:16AM +0530, Aneesh Kumar K.V wrote:
From: Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com
Powerpc architecture uses a hash based page table mechanism for mapping
virtual
addresses to physical address. The architecture require this hash page table
to
be
On 07/02/2013 07:45 AM, Aneesh Kumar K.V wrote:
From: Aneesh Kumar K.Vaneesh.ku...@linux.vnet.ibm.com
Powerpc architecture uses a hash based page table mechanism for mapping virtual
addresses to physical address. The architecture require this hash page table to
be physically contiguous. With
Alexander Graf ag...@suse.de writes:
On 07/02/2013 07:45 AM, Aneesh Kumar K.V wrote:
From: Aneesh Kumar K.Vaneesh.ku...@linux.vnet.ibm.com
Powerpc architecture uses a hash based page table mechanism for mapping
virtual
addresses to physical address. The architecture require this hash page
On 07/02/2013 05:31 PM, Aneesh Kumar K.V wrote:
Alexander Grafag...@suse.de writes:
On 07/02/2013 07:45 AM, Aneesh Kumar K.V wrote:
From: Aneesh Kumar K.Vaneesh.ku...@linux.vnet.ibm.com
Powerpc architecture uses a hash based page table mechanism for mapping virtual
addresses to physical
On Tue, 2013-07-02 at 17:12 +0200, Alexander Graf wrote:
Is CMA a mandatory option in the kernel? Or can it be optionally
disabled? If it can be disabled, we should keep the preallocated
fallback case around for systems that have CMA disabled.
Why ? More junk code to keep around ...
If CMA
On 03.07.2013, at 00:28, Benjamin Herrenschmidt wrote:
On Tue, 2013-07-02 at 17:12 +0200, Alexander Graf wrote:
Is CMA a mandatory option in the kernel? Or can it be optionally
disabled? If it can be disabled, we should keep the preallocated
fallback case around for systems that have CMA
From: Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com
Powerpc architecture uses a hash based page table mechanism for mapping virtual
addresses to physical address. The architecture require this hash page table to
be physically contiguous. With KVM on Powerpc currently we use early reservation
