direct-io.hg

changeset 12415:1eb880e9ff94

[IA64] fix domVTi boot with maxmem

We found the following bug.
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=800

I change assigned page number by assign_domain_page()
from d->max_pages to d->tot_pages in vmx_build_physmap_table()
because domVTi don't support maxmem.

Signed-off-by: Akio Takebe <takebe_akio@jp.fujitsu.com>
author awilliam@xenbuild.aw
date Tue Oct 31 22:25:25 2006 -0700 (2006-10-31)
parents 77bf1d1628a7
children 8ee7bb2af497
files xen/arch/ia64/vmx/vmx_init.c
line diff
     1.1 --- a/xen/arch/ia64/vmx/vmx_init.c	Tue Oct 31 22:25:21 2006 -0700
     1.2 +++ b/xen/arch/ia64/vmx/vmx_init.c	Tue Oct 31 22:25:25 2006 -0700
     1.3 @@ -364,7 +364,10 @@ static const io_range_t io_ranges[] = {
     1.4  
     1.5  /* Reseve 1 page for shared I/O ,1 page for xenstore and 1 page for buffer I/O.  */
     1.6  #define VMX_SYS_PAGES	(3 + (GFW_SIZE >> PAGE_SHIFT))
     1.7 -#define VMX_CONFIG_PAGES(d) ((d)->max_pages - VMX_SYS_PAGES)
     1.8 +/* If we support maxmem for domVTi, we should change from tot_page to max_pages.
     1.9 + * #define VMX_CONFIG_PAGES(d) ((d)->max_pages - VMX_SYS_PAGES)
    1.10 + */
    1.11 +#define VMX_CONFIG_PAGES(d) ((d)->tot_pages - VMX_SYS_PAGES)
    1.12  
    1.13  static void vmx_build_physmap_table(struct domain *d)
    1.14  {