arch: x86: mm: Start of physpage allocator

Signed-off-by: Bart Kuivenhoven <bemkuivenhoven@gmail.com>
arch: x86: mm: Add page_allocator code

Signed-off-by: Bart Kuivenhoven <bemkuivenhoven@gmail.com>
mm: arch: x86: pte: Add discriptor and comments
mm: pte: Add discriptor and todo comments
mm: Move page_alloc to main tree and clean up pte
mm: page_alloc: Make a start on parsing mboot map
mm: page_alloc: Call the initialisator in init
mm: page_alloc: Add some comments

Comment, because ... Well ... Comments are fun, right?
Well You should see the patch. Ok I agree, they're not funny at all.
mm: page_alloc: resolved some warnings
mm: page_alloc: Add clean list end feature
mm: page_alloc: Remove bug to reallocating kernel

In the old situation the kernel allowed for its own memory to be
reallocated. That situation would allow for severe memory corruption to
occur.

The new situation simply takes a loop and marks all the pages in use by
the kernel as unavailable.
sched: Add a roundrobin scheduler
mm: page_alloc: Add list dumping function
mm: paging: Map the entire first GB to core memory

The kernel will need the statically allocated page tables and page
directories. This is best declared in the linker script as there they
can be defined as page boundary aligned.

The Assembler code will now run a little longer in order to map the
kernel space.
mm: paging: Added some todo items to PTE
mm: pte: Starting to rework the pte system

You know, like with a design this time ...
mm: pte: Add userland pte system
mm: pte_core: Allign the pte core segments

Pte segments are to be aligned to memory size covered by the page table
pointed to.
mm: pte: Fix initialisation and add comments
mm: pte: rename pte to vm and delete buddy

Rename:

The rename is necessary because the data structures describe virtual
memory more than they would describe page table entries, despite the
fact that they actually contain references to the page tables.

deletion of buddy:

The buddy allocator was fun and all, but didn't fit into the design of
the kernel anylonger. It would start colliding with the replacing
virtual memory manager otherwise.