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/
Home Products Support Community News


[Xen-devel] Re: Memory-hotplug support for x86_64 domUs?

To: "Radhakrishnan, Prashanth" <Prashanth.Radhakrishnan@xxxxxxxxxx>
Subject: [Xen-devel] Re: Memory-hotplug support for x86_64 domUs?
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Tue, 12 Aug 2008 09:50:00 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 12 Aug 2008 09:50:41 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <B4A89DAB06701749A8440A7A633FA69AEF672F@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <B4A89DAB06701749A8440A7A633FA69AEF672F@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20080723)
Radhakrishnan, Prashanth wrote:

I wanted to know if the following would work:
- memory-hotplug on x86_64 domUs
- memory-hotplug + ballooning interplay (e.g.
http://lkml.org/lkml/2008/4/3/449), again on x86_64 domUs

For starts, if I read the Xen linux src (at
http://xenbits.xensource.com/linux-2.6.18-xen.hg) right, it says that
SPARSEMEM cannot be enabled with X86_64_XEN. Is that right?

No, sparsemem is supported in pvops Xen kernels (both 32 and 64 bit). But it isn't very useful at present.

I have some patches to allow balloon expansion by using memory hotplug to add new memory to the system. But unfortunately it requires some changes to the memory hotplug subsystem, and last time I posted them we (the memory hotplug maintainers and I) failed to converge on a mutually acceptable set of patches. I put it aside to work on some higher value things (x86-64 support, mainly), and it's been sitting in the TODO state since.


Xen-devel mailing list

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