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] buildconfigs of supporting SPARSEMEM

To: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-ia64-devel] [Patch][RFC] buildconfigs of supporting SPARSEMEM
From: Akio Takebe <takebe_akio@xxxxxxxxxxxxxx>
Date: Tue, 30 Jan 2007 18:10:06 +0900
Delivery-date: Tue, 30 Jan 2007 01:11:41 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi,

This patch is for updating buildconfig.
This patch fix the following issue which dom0 reserves waste memory.
See the following link.
http://lists.xensource.com/archives/html/xen-ia64-devel/2007-01/msg00113.html

In the case of linux side, it seems SPARSEMEM is used with NUMA.
Actually in linux-2.6.18, NUMA depends on !FLATMEM.

==========================================================
config NUMA
        bool "NUMA support"
        depends on !IA64_HP_SIM && !FLATMEM
        default y if IA64_SGI_SN2
        help
          Say Y to compile the kernel to support NUMA (Non-Uniform Memory
          Access).  This option is for configuring high-end multiprocessor
          server systems.  If in doubt, say N.
==========================================================

So I update buildconfig with SPARSEMEM and NUMA.
I tested dom0 boot. This is no problem.
I cannot test domU boot, because currently xen-ia64 tree 
cannot boot domU without my patch.
But I think domU boot is no problem if current tree is fixed.

Our PRIMEQUEST having small memory cannot boot without this patch.
Please test other IPFs.
If you have any comments, please.

F.Y.I.
The following warnig is occurred at compile time with my patch,
but this warning is no problem.

In file included from 
/home/takebe/xen-ia64-unstable.hg.070130/linux-2.6.18-xen/include/linux/gfp.h:4,
                 from 
/home/takebe/xen-ia64-unstable.hg.070130/linux-2.6.18-xen/include/linux/slab.h:14,
                 from 
/home/takebe/xen-ia64-unstable.hg.070130/linux-2.6.18-xen/include/linux/percpu.h:4,
                 from 
/home/takebe/xen-ia64-unstable.hg.070130/linux-2.6.18-xen/include/linux/rcupdate.h:41,
                 from 
/home/takebe/xen-ia64-unstable.hg.070130/linux-2.6.18-xen/include/linux/dcache.h:10,
                 from 
/home/takebe/xen-ia64-unstable.hg.070130/linux-2.6.18-xen/include/linux/fs.h:229,
                 from 
/home/takebe/xen-ia64-unstable.hg.070130/linux-2.6.18-xen/drivers/md/dm.h:13,
                 from 
/home/takebe/xen-ia64-unstable.hg.070130/linux-2.6.18-xen/drivers/md/dm-path-selector.c:12:
/home/takebe/xen-ia64-unstable.hg.070130/linux-2.6.18-xen/include/linux/mmzone.h:
 At top level:
/home/takebe/xen-ia64-unstable.hg.070130/linux-2.6.18-xen/include/linux/mmzone.h:604:
 warning: static declaration of 'pfn_valid' follows non-static declaration
include2/asm/maddr.h:72: warning: 'pfn_valid' declared inline after being called
include2/asm/maddr.h:72: warning: previous implicit declaration of 'pfn_valid' 
was here

Signed-off-by: Akio Takebe <takebe_akio@xxxxxxxxxxxxxx>

---
diff -r d0b2022e2403 buildconfigs/linux-defconfig_xen_ia64
--- a/buildconfigs/linux-defconfig_xen_ia64     Mon Jan 29 11:17:15 2007 -0700
+++ b/buildconfigs/linux-defconfig_xen_ia64     Tue Jan 30 18:48:48 2007 +0900
@@ -1,8 +1,9 @@
 #
 # Automatically generated make config: don't edit
 # Linux kernel version: 2.6.18-xen
-# Mon Jan 29 10:01:13 2007
-#
+# Tue Jan 30 18:04:41 2007
+#
+CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
 
 #
 # Code maturity level options
@@ -129,19 +130,26 @@ CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
 # CONFIG_PERMIT_BSP_REMOVE is not set
 # CONFIG_PREEMPT is not set
 CONFIG_SELECT_MEMORY_MODEL=y
-CONFIG_FLATMEM_MANUAL=y
+# CONFIG_FLATMEM_MANUAL is not set
 # CONFIG_DISCONTIGMEM_MANUAL is not set
-# CONFIG_SPARSEMEM_MANUAL is not set
-CONFIG_FLATMEM=y
-CONFIG_FLAT_NODE_MEM_MAP=y
+CONFIG_SPARSEMEM_MANUAL=y
+CONFIG_SPARSEMEM=y
+CONFIG_NEED_MULTIPLE_NODES=y
+CONFIG_HAVE_MEMORY_PRESENT=y
 # CONFIG_SPARSEMEM_STATIC is not set
+CONFIG_SPARSEMEM_EXTREME=y
+# CONFIG_MEMORY_HOTPLUG is not set
 CONFIG_SPLIT_PTLOCK_CPUS=4
+CONFIG_MIGRATION=y
 CONFIG_RESOURCES_64BIT=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_NODES_SHIFT=10
+CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID=y
+CONFIG_HAVE_ARCH_NODEDATA_EXTENSION=y
 # CONFIG_IA32_SUPPORT is not set
 CONFIG_IA64_MCA_RECOVERY=y
 CONFIG_PERFMON=y
@@ -172,6 +180,7 @@ CONFIG_ACPI_PROCESSOR=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

Best Regards,

Akio Takebe


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

<Prev in Thread] Current Thread [Next in Thread>