[rumpkernel/rumprun] 68a211: panic if loadmem is called >once

  • From: GitHub <noreply@xxxxxxxxxx>
  • To: rumpkernel-builds@xxxxxxxxxxxxx
  • Date: Fri, 19 Jun 2015 08:00:30 -0700

Branch: refs/heads/master
Home: https://github.com/rumpkernel/rumprun
Commit: 68a211e456a9762b9306779bb4d09460b1229bb7

https://github.com/rumpkernel/rumprun/commit/68a211e456a9762b9306779bb4d09460b1229bb7
Author: Antti Kantee <pooka@xxxxxx>
Date: 2015-06-19 (Fri, 19 Jun 2015)

Changed paths:
M platform/hw/pgalloc.c

Log Message:
-----------
panic if loadmem is called >once


Commit: ec33320b8b93f3667574b25f9ad4d4e2fb175049

https://github.com/rumpkernel/rumprun/commit/ec33320b8b93f3667574b25f9ad4d4e2fb175049
Author: Antti Kantee <pooka@xxxxxx>
Date: 2015-06-19 (Fri, 19 Jun 2015)

Changed paths:
M platform/hw/pgalloc.c

Log Message:
-----------
Always run page allocator on "virtual memory" (or just "memory").

The page bitmap is its own "address space", which is va offset by the
address of the first page loaded. However, there is no assumption
anymore that this in any way maps to the physical memory space anymore.

TODO: convert Xen page mallocator to use the same scheme and unify
page allocators


Compare:
https://github.com/rumpkernel/rumprun/compare/536a95cf0211...ec33320b8b93

Other related posts:

  • » [rumpkernel/rumprun] 68a211: panic if loadmem is called >once - GitHub