The need for tow-level page tables and small pages

Hesham Moustafa heshamelmatary at
Wed Apr 10 11:20:37 UTC 2013

On Wed, Apr 10, 2013 at 1:00 PM, Chris Johns <chrisj at> wrote:
> Hesham Moustafa wrote:
>> I read some docs that relate to dynamic linker/loader implemented by
>> Chris and I think this project may need some sort of dynamic
>> page-level allocation combined with protection attributes. That's for
>> example.
> The linker/loader performs fix ups at the address provided by the allocator
> therefore the standard libc malloc can be used. The loader provides hooks to
> allow a custom allocator and that allocator could implement some form of
> protection for executable and/or read only sections of memory.
that allocator provides SW protection only ? or SW and/or HW ?
> The linker/loader does not care how this is implemented. I hope this clarifies
> what the loader requires.
That said, if there was a low-level API that can provide HW level
protection for any
region of memory (that maybe previously allocated by whatever allocator), would
the linker/loader use it ?
> Chris

More information about the devel mailing list