WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ia64-devel

Re: [Xen-ia64-devel] Question to memory handling for domU

Le Jeudi 10 Août 2006 16:10, Dietmar Hahn a écrit :
> Hi Tristan,
>
> Am Donnerstag, 10. August 2006 15:26 schrieb Tristan Gingold:
> > Le Jeudi 10 Août 2006 15:13, Dietmar Hahn a écrit :
> > > Hi,
> > >
> > > while I was playing with my mini-os and the memory a short question
> > > comes up: What memory info is relevant and where gets the domU kernel
> > > loaded within the (for domU) configured memory?
> >
> > domU kernel is loaded at its physical address (IIRC).  Check the ELF
> > header.
> >
> > > I have 128MB configured for domU.
> > > start_info->nr_pages gives me 8192 pages -> 128MB.
> >
> > Seems correct :-)
> >
> > > The memory given by the efi (EfiConventionalMemory) is physically
> > > between 0x200000 and 0x7ff4000 -> ~2MB are absent.
> > > Do I have to take this efi memory only, right? How is the absent memory
> > > used?
> >
> > You have memory between 0 and 0x200000.  The start_info page is not in
> > the memmap (IIRC).
>
> OK I understand. Between 0 and 0x200000 are the bootinfo, efi and pal
> stuff. Between 0x200000 and 0x7ff4000 is the memory usable for mini-os.
> This includes the kernel code and data.
> Now only the area between 0x7ff4000 and 0x8000000 is unclear.
3 pages: 1 for xenbus, 1 for console and 1 for start_info.

> Is 0x200000 a fix address?
Yes, but we could reduce it.

[...]
Tristan.

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