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

[Xen-ia64-devel] [PATCH][RFC] fix dom0 builder TAKE3

On Mon, Oct 16, 2006 at 02:41:40PM -0600, Alex Williamson wrote:

>    Yes, I think we'll need to switch to discontig/sparsemem for the dom0
> kernel if the memmory map is going to reflect the bare metal hardware
> memory layout.  Unfortunately, just switching to discontig w/ virtual
> memmap does not solve the problem I'm seeing.  The dom0 kernel reports
> the correct amount of memory early in bootup.  Perhaps the balloon
> driver is causing this(?)  Thanks,

I looked into balloon driver and found that it doesn't take care of
sparsely populated memory.
How about those patches?

- dom0_initrd_start.patch
  changed dom0's initrd image load area so that it follows start info.
  It becomes non-sense to use dom0_size if dom0 memoy is assigned sparsely.
- fix_dom0_builder.patch
  fix dom0 builder so that xen doesn't assign memory on I/O area.
- convmem_end.patch
  split the meaning of struct domain::maxmem into struct
  arch_domain::convmem_end so that maxmem means the number of pages which
  domain has and convmem_end means the highest address of conventional
  memory (i.e. RAM).
- max_mapnr_config_flatmem.patch
  remove warning when !CONFIG_FLATMEM moving max_mapnr declaration.
- sparse_contiugous_bitmap.patch
  allocate contiguous_bitmap sparsely like virtual memmap.
  With dom0 memory assignment changed, memory might be sparse, so simple bitmap
  may waste too much memory.
- fix_balloon_init.patch
  make balloon driver not return pages which are in
  [xen_start_info->nr_pages, max_pfn] on ia64.
  On ia64 memory might be assigned sparsely. In that case
  xen_start_info->nr_pages and max_pfn doesn't match while pages which are in
  [xen_start_info->nr_pages, max_pfn] are used.

-- 
yamahata

Attachment: 13110_39d2b340885f_dom0_initrd_start.patch
Description: Text document

Attachment: 13111_2f68d7084097_fix_dom0_builder.patch
Description: Text document

Attachment: 13112_0c823791df8d_convmem_end.patch
Description: Text document

Attachment: 13113_e4195cf98e69_max_mapnr_config_flatmem.patch
Description: Text document

Attachment: 13114_bddf36d06df6_sparse_contiugous_bitmap.patch
Description: Text document

Attachment: 13115_d8b84560af53_fix_balloon_init.patch
Description: Text document

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-ia64-devel] [PATCH][RFC] fix dom0 builder TAKE3, Isaku Yamahata <=