[Xen-changelog] [xen-unstable] [IA64] fix domVTi boot with maxmem

[Xen patchbot-unstable <patchbot-unstable@xxxxxxxxxxxxxxxxxxx>]

# HG changeset patch
# User awilliam@xxxxxxxxxxx
# Node ID 1eb880e9ff944de77d534517492d0a583fc9587e
# Parent  77bf1d1628a77bd9a207aeb99d2cbb400671a109
[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@xxxxxxxxxxxxxx>
---
 xen/arch/ia64/vmx/vmx_init.c |    5 ++++-
 1 files changed, 4 insertions(+), 1 deletion(-)

diff -r 77bf1d1628a7 -r 1eb880e9ff94 xen/arch/ia64/vmx/vmx_init.c
--- a/xen/arch/ia64/vmx/vmx_init.c      Tue Oct 31 22:25:21 2006 -0700
+++ b/xen/arch/ia64/vmx/vmx_init.c      Tue Oct 31 22:25:25 2006 -0700
@@ -364,7 +364,10 @@ static const io_range_t io_ranges[] = {
 
 /* Reseve 1 page for shared I/O ,1 page for xenstore and 1 page for buffer 
I/O.  */
 #define VMX_SYS_PAGES  (3 + (GFW_SIZE >> PAGE_SHIFT))
-#define VMX_CONFIG_PAGES(d) ((d)->max_pages - VMX_SYS_PAGES)
+/* If we support maxmem for domVTi, we should change from tot_page to 
max_pages.
+ * #define VMX_CONFIG_PAGES(d) ((d)->max_pages - VMX_SYS_PAGES)
+ */
+#define VMX_CONFIG_PAGES(d) ((d)->tot_pages - VMX_SYS_PAGES)
 
 static void vmx_build_physmap_table(struct domain *d)
 {

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