Re: [PATCH] fix dom0 builder TAKE 2(was Re: [Xen-ia64-devel] [PATCH] fix dom0 builder) - Alex Williamson - com.xensource.lists.xen-ia64-devel

22 messages in com.xensource.lists.xen-ia64-develRe: [PATCH] fix dom0 builder TAKE 2(w...

From	Sent On	Attachments
Isaku Yamahata	06 Oct 2006 00:41	.patch
Alex Williamson	08 Oct 2006 17:05
Tristan Gingold	09 Oct 2006 00:37
Isaku Yamahata	09 Oct 2006 02:15
Tristan Gingold	09 Oct 2006 05:00
Isaku Yamahata	15 Oct 2006 19:05	.patch
Isaku Yamahata	15 Oct 2006 19:06	.patch
Alex Williamson	15 Oct 2006 20:05	.patch
Isaku Yamahata	15 Oct 2006 20:33
Alex Williamson	15 Oct 2006 21:35
Isaku Yamahata	15 Oct 2006 23:05
Alex Williamson	16 Oct 2006 13:41
Alex Williamson	17 Oct 2006 21:11
Isaku Yamahata	21 Dec 2006 01:10	.patch, .patch, .patch, 3 more
Alex Williamson	03 Jan 2007 20:01
Isaku Yamahata	03 Jan 2007 20:36
Akio Takebe	04 Jan 2007 00:22
Isaku Yamahata	04 Jan 2007 01:03	.patch
Akio Takebe	04 Jan 2007 02:40	.patch
Alex Williamson	04 Jan 2007 16:32
Alex Williamson	04 Jan 2007 16:35
Alex Williamson	04 Jan 2007 16:35

Subject:	Re: [PATCH] fix dom0 builder TAKE 2(was Re: [Xen-ia64-devel] [PATCH] fix dom0 builder)
From:	Alex Williamson (alex...@hp.com)
Date:	10/16/2006 01:41:17 PM
List:	com.xensource.lists.xen-ia64-devel

On Mon, 2006-10-16 at 15:06 +0900, Isaku Yamahata wrote:

Hi Alex.

If CONFIG_FLATMEM=y is enabled(xenLinux default is so), it seems sane that the total is about 5GB. Do disabling CONFIG_FLATMEM=n and enabling CONFIG_DISCONTIGMEM=y (or CONFIG_SPARSEMEM=y) make difference? And I also noticed that xenLinux default config disables CONFIG_VIRTUAL_MEM_MAP=n. Since dom0 may see underlying machine memory layout with the patch, should we revise default Linux config?

Hi Isaku,

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,

Alex