Re: [Patch] was Re: [Xen-ia64-devel] Good projects for someone

[Tristan Gingold <Tristan.Gingold@xxxxxxxx>]

Le Mardi 03 Janvier 2006 20:59, Magenheimer, Dan (HP Labs Fort Collins) a 
écrit :
> > I tried to remove the hack, but I got only a fatal error when
> > dom0 was built.
> > Here is a patch which fixes the issue: dom0 image was not
> > correctly protected
> > from memory allocator.
> >
> > I also remove the hack since it seems to work.  My machine
> > has 8GB.  The
> > frame_table uses about 55MB (72 bytes per page)!
> >
> > I am not sure we need a virtual memmap, if I understand
> > correctly what it is.
> > The current approach simply wastes many memory in unused
> > frame_table entries.
>
> I tried your patch and I still get "Not enough memory for
> frame table" and a reboot.  See attached file.
Hi,

thank you for your report.  It confirmed the problem I feared.
You don't have much memory (2GB), but you have a *very* big hole:
(XEN) Init boot pages: 0x1000000 -> 0x4000000.
(XEN) Init boot pages: 0x8f89030 -> 0x3f5e4000.
(XEN) Init boot pages: 0x3fb00000 -> 0x3fb2c000.
** HERE **
(XEN) Init boot pages: 0x4040000000 -> 0x407de8a000.
(XEN) Init boot pages: 0x407df42a54 -> 0x407efe0008.
(XEN) Init boot pages: 0x407efe0068 -> 0x407efe3f82.
(XEN) Init boot pages: 0x407efe3fca -> 0x407effc008.
(XEN) Init boot pages: 0x407effc7e8 -> 0x407fd68000.
(XEN) Init boot pages: 0x407fda4000 -> 0x407fe10000.
(XEN) Init boot pages: 0x407fe80000 -> 0x407ffbc000.

So, I will work on enabling VIRTUAL_MEM_MAP.

Could you try the patch without the modif in efi.c ?  I think the rest of the 
patch really fix a bug with memory reservation.

Thanks,
Tristan.


_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel