[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] Re: "reserve_top_address" and the kernel virtual memory with KML.
On Sat, Aug 30, 2008 at 10:38 PM, Peter Teoh <htmldeveloper@xxxxxxxxx> wrote:
Probably this was too early to have called "reserve_top_address" . I tried shifting this call to the place right before the mem_init() in the same function. vfs_caches_init_early(); cpuset_init_early(); //ask for 8 MB topmost reserve_top_address(8388608ul); mem_init(); enable_debug_pagealloc(); This time I got a kernel panic instead and the error said "unknown_bootoption+0x0/0x1f0".
I think it says that the default 128 MB size allocated for "vmalloc" can be altered with the "size" parameter. Again, reserve_top_address also has an impact on the amount of memory given to vmalloc as it resizes the __VMALLOC_RESERVE parameter. I am sure it 128M could be a thing to try out.
-Regmee _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |