Re: [PATCH RFC] x86: add brk allocation for very, very early allocations

[Jeremy Fitzhardinge]

H. Peter Anvin wrote:
> That would make sense.  init_memory_mapping() needs to know what not to
> step on, and that would include the brk at this stage.  For 64-bit mode,
> Xen is the only user of !PSE, and so may be particularly vulnerable to
> this issue (because of massively larger direct mapping tables.)
>   

Yep.

> This reminds me... is your intent that the BRK is permanent (unless
> explicitly freed on a page by page basis) or part of the init memory
> that is flushed?
>   

Permanent.  I'm using it to allocate things which are the moral 
equivalent of the kernel pagetables.

   J
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/