All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Radhakrishnan, Prashanth" <Prashanth.Radhakrishnan@netapp.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Memory-hotplug support for x86_64 domUs?
Date: Tue, 12 Aug 2008 09:50:00 -0700	[thread overview]
Message-ID: <48A1BF38.4040200@goop.org> (raw)
In-Reply-To: <B4A89DAB06701749A8440A7A633FA69AEF672F@SACMVEXC2-PRD.hq.netapp.com>

Radhakrishnan, Prashanth wrote:
> Hi,
>
> 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.

    J

       reply	other threads:[~2008-08-12 16:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <B4A89DAB06701749A8440A7A633FA69AEF672F@SACMVEXC2-PRD.hq.netapp.com>
2008-08-12 16:50 ` Jeremy Fitzhardinge [this message]
     [not found]   ` <B4A89DAB06701749A8440A7A633FA69AFF4F8F@SACMVEXC2-PRD.hq.netapp.com>
2008-08-12 17:46     ` Memory-hotplug support for x86_64 domUs? Jeremy Fitzhardinge

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48A1BF38.4040200@goop.org \
    --to=jeremy@goop.org \
    --cc=Prashanth.Radhakrishnan@netapp.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.