Hello, Cyril.
On Wed, Sep 12, 2012 at 08:40:58PM -0400, Cyril Chemparathy wrote:
> You probably missed the lowmem bit from my response?
>
> This system has all of its memory outside the 4GB physical address
> space. This includes lowmem, which is permanently mapped into the
> kernel virtual addr
Hi Tejun,
On 9/12/2012 8:34 PM, Tejun Heo wrote:
Hello,
On Wed, Sep 12, 2012 at 08:08:30PM -0400, Cyril Chemparathy wrote:
So, a function which takes phys_addr_t for goal and limit but returns
void * doesn't make much sense unless the function creates directly
addressable mapping somewhere.
Hello,
On Wed, Sep 12, 2012 at 08:08:30PM -0400, Cyril Chemparathy wrote:
> >So, a function which takes phys_addr_t for goal and limit but returns
> >void * doesn't make much sense unless the function creates directly
> >addressable mapping somewhere.
>
> On the 32-bit PAE platform in question, p
Hi Tejun,
On 9/12/2012 4:39 PM, Tejun Heo wrote:
Hello,
On Wed, Sep 12, 2012 at 12:06:48PM -0400, Cyril Chemparathy wrote:
static void * __init alloc_bootmem_core(unsigned long size,
unsigned long align,
- unsigned
Hello,
On Wed, Sep 12, 2012 at 12:06:48PM -0400, Cyril Chemparathy wrote:
> static void * __init alloc_bootmem_core(unsigned long size,
> unsigned long align,
> - unsigned long goal,
> -
From: Vitaly Andrianov
On a physical address extended (PAE) systems physical memory may be located
outside the first 4GB address range. In particular, on TI Keystone devices,
all memory (including lowmem) is located outside the 4G address space. Many
functions in the bootmem.c use unsigned long
6 matches
Mail list logo
