[Xen-ia64-devel] [RFC] Change .config of dom0 for

2007-01-17 Thread Akio Takebe
Hi, Isaku and all

When I boot dom0 with dom0_mem=31G, dom0 use about 2GB memory after booting.
I check why dom0 use 2GB, then I found the following message at the boot time.

 Aperture: 64 megabytes
 Kernel range: 0xe52b4000 - 0xe92b4000
 Address size: 30 bits
Memory: 30649984k/32456704k available (10480k code, 1805472k reserved, 4361k 
data, 288k init) --- !!!reserved 1.8GB!!!
McKinley Errata 9 workaround not needed; disabling it

So I check the rsvd_memory, but rsvd_region is no problem.
rsvd_region[0]=1480 (0xe0002228 - 0xe00027f0)
rsvd_region[1]=96   (0xe100 - 0xe160)
rsvd_region[2]=18344456 (0xe400 - 0xe517ea08)
rsvd_region[3]=16384(0xe518 - 0xe5184000)
rsvd_region[4]=66   (0xe5180080 - 0xe51800c2)
rsvd_region[5]=80   (0xe5180480 - 0xe51804d0)
rsvd_region[6]=1305615  (0xe5184000 - 0xe52c2c0f)
rsvd_region[7]=0(0x - 0x)

Because Isaku's dom0 patches change dom0's memory map from contiguous memory 
to discontiguous memory, I change .config of dom0 like the below,
then I can get the following message and dom0 don't use 2GB.

# diff -uNrp buildconfigs/linux-defconfig_xen_ia64 build-linux-2.6.16.33-
xen_ia64/.config  
--- buildconfigs/linux-defconfig_xen_ia64   2007-01-17 07:21:06.0 +
0900
+++ build-linux-2.6.16.33-xen_ia64/.config  2007-01-17 20:22:11.0 +
0900
@@ -1,7 +1,7 @@
 #
 # Automatically generated make config: don't edit
-# Linux kernel version: 2.6.16.29-xen
-# Tue Nov 14 10:38:50 2006
+# Linux kernel version: 2.6.16.33-xen
+# Wed Jan 17 20:22:11 2007
 #
 
 #
@@ -125,18 +125,23 @@ CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
 # CONFIG_SCHED_SMT is not set
 # CONFIG_PREEMPT is not set
 CONFIG_SELECT_MEMORY_MODEL=y
-CONFIG_FLATMEM_MANUAL=y
-# CONFIG_DISCONTIGMEM_MANUAL is not set
+# CONFIG_FLATMEM_MANUAL is not set
+CONFIG_DISCONTIGMEM_MANUAL=y
 # CONFIG_SPARSEMEM_MANUAL is not set
-CONFIG_FLATMEM=y
+CONFIG_DISCONTIGMEM=y
 CONFIG_FLAT_NODE_MEM_MAP=y
+CONFIG_NEED_MULTIPLE_NODES=y
 # CONFIG_SPARSEMEM_STATIC is not set
 CONFIG_SPLIT_PTLOCK_CPUS=4
+CONFIG_MIGRATION=y
 CONFIG_ARCH_SELECT_MEMORY_MODEL=y
 CONFIG_ARCH_DISCONTIGMEM_ENABLE=y
 CONFIG_ARCH_FLATMEM_ENABLE=y
 CONFIG_ARCH_SPARSEMEM_ENABLE=y
-# CONFIG_VIRTUAL_MEM_MAP is not set
+CONFIG_NUMA=y
+CONFIG_VIRTUAL_MEM_MAP=y
+CONFIG_HOLES_IN_ZONE=y
+CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID=y
 # CONFIG_IA32_SUPPORT is not set
 CONFIG_IA64_MCA_RECOVERY=y
 CONFIG_PERFMON=y
@@ -166,6 +171,7 @@ CONFIG_ACPI_FAN=y
 CONFIG_ACPI_PROCESSOR=y
 CONFIG_ACPI_HOTPLUG_CPU=y
 CONFIG_ACPI_THERMAL=y
+CONFIG_ACPI_NUMA=y
 CONFIG_ACPI_BLACKLIST_YEAR=0
 # CONFIG_ACPI_DEBUG is not set
 CONFIG_ACPI_EC=y
@@ -1522,7 +1528,6 @@ CONFIG_HAVE_ARCH_ALLOC_SKB=y
 CONFIG_HAVE_ARCH_DEV_ALLOC_SKB=y
 CONFIG_XEN_BALLOON=y
 CONFIG_XEN_SKBUFF=y
-# CONFIG_XEN_DEVMEM is not set
 CONFIG_XEN_REBOOT=y
 # CONFIG_XEN_SMPBOOT is not set
 CONFIG_XEN_INTERFACE_VERSION=0x00030203
@@ -1558,3 +1563,4 @@ CONFIG_XEN_COMPAT_030002_AND_LATER=y
 CONFIG_XEN_COMPAT_030002=y
 CONFIG_HAVE_IRQ_IGNORE_UNHANDLED=y
 CONFIG_NO_IDLE_HZ=y
+CONFIG_XEN_DEVMEM=y


Should we change .config of dom0?
Or should we fix other code?

I think we should change .confing,
I use CONFIG_DISCONTIGMEM and CONFIG_VIRTUAL_MEM_MAP,
but we may use SPARSEMEM.
(I'll check SPARSEMEM soon.)

Please comment.

Best Regards,

Akio Takebe


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


Re: [Xen-ia64-devel] [RFC] Change .config of dom0 for

2007-01-17 Thread Alex Williamson
On Thu, 2007-01-18 at 09:10 +0900, Akio Takebe wrote:
 Hi, Isaku and all
 
 When I boot dom0 with dom0_mem=31G, dom0 use about 2GB memory after booting.
 I check why dom0 use 2GB, then I found the following message at the boot time.
 
  Aperture: 64 megabytes
  Kernel range: 0xe52b4000 - 0xe92b4000
  Address size: 30 bits
 Memory: 30649984k/32456704k available (10480k code, 1805472k reserved, 4361k 
 data, 288k init) --- !!!reserved 1.8GB!!!
 McKinley Errata 9 workaround not needed; disabling it
...
 
 Should we change .config of dom0?
 Or should we fix other code?
 
 I think we should change .confing,
 I use CONFIG_DISCONTIGMEM and CONFIG_VIRTUAL_MEM_MAP,
 but we may use SPARSEMEM.
 (I'll check SPARSEMEM soon.)

   I agree, we're presenting dom0 with a memory map similar to bare
metal hardware.  The contiguous memory handlers aren't going to be able
to deal with that efficiently on many ia64 platforms.  Thanks,

Alex

-- 
Alex Williamson HP Open Source  Linux Org.


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


Re: [Xen-ia64-devel] [RFC] Change .config of dom0 for

2007-01-17 Thread Akio Takebe
Hi, Alex and all

 I think we should change .confing,
 I use CONFIG_DISCONTIGMEM and CONFIG_VIRTUAL_MEM_MAP,
 but we may use SPARSEMEM.
 (I'll check SPARSEMEM soon.)

   I agree, we're presenting dom0 with a memory map similar to bare
metal hardware.  The contiguous memory handlers aren't going to be able
to deal with that efficiently on many ia64 platforms.  Thanks,

Thank you for your reply.
I check SPARSEMEM, but unfortunately I have many compile error.
So if we choice SPARSEMEM, we must fix bits.
Which config are everyone think best?

Best Regards,

Akio Takebe


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