From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Miroslav Rezanina <mrezanin@redhat.com>
Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com
Subject: Re: [PATCH][v2.6.29][XEN] Return unused memory to hypervisor
Date: Thu, 03 Sep 2009 16:26:24 -0700 [thread overview]
Message-ID: <4AA050A0.90609@goop.org> (raw)
In-Reply-To: <1962776416.772071250687130436.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
On 08/19/09 06:05, Miroslav Rezanina wrote:
> when running linux as XEN guest and use boot parameter mem= to set memory lower then is assigned to guest, not used memory should be returned to hypervisor as free. This is working with kernel available on xen.org pages, but is not working with kernel 2.6.29. Comparing both kernels I found code for returning unused memory to hypervisor is missing. Following patch add this functionality to 2.6.29 kernel.
>
Are you planning on submitting a revised patch along the lines I suggested?
Thanks,
J
WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Miroslav Rezanina <mrezanin@redhat.com>
Cc: xen-devel@lists.xensource.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][v2.6.29][XEN] Return unused memory to hypervisor
Date: Thu, 03 Sep 2009 16:26:24 -0700 [thread overview]
Message-ID: <4AA050A0.90609@goop.org> (raw)
In-Reply-To: <1962776416.772071250687130436.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
On 08/19/09 06:05, Miroslav Rezanina wrote:
> when running linux as XEN guest and use boot parameter mem= to set memory lower then is assigned to guest, not used memory should be returned to hypervisor as free. This is working with kernel available on xen.org pages, but is not working with kernel 2.6.29. Comparing both kernels I found code for returning unused memory to hypervisor is missing. Following patch add this functionality to 2.6.29 kernel.
>
Are you planning on submitting a revised patch along the lines I suggested?
Thanks,
J
next prev parent reply other threads:[~2009-09-03 23:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <131246341.771871250687008542.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2009-08-19 13:05 ` [PATCH][v2.6.29][XEN] Return unused memory to hypervisor Miroslav Rezanina
2009-08-19 13:05 ` Miroslav Rezanina
2009-08-19 16:16 ` Jeremy Fitzhardinge
2009-08-20 7:47 ` Miroslav Rezanina
2009-08-20 7:47 ` Miroslav Rezanina
2009-08-20 16:39 ` Jeremy Fitzhardinge
2009-08-20 16:39 ` Jeremy Fitzhardinge
2009-09-07 12:41 ` Miroslav Rezanina
2009-09-07 12:41 ` Miroslav Rezanina
2009-09-08 18:58 ` Jeremy Fitzhardinge
2009-09-08 18:58 ` Jeremy Fitzhardinge
2009-08-20 9:31 ` [Xen-devel] " Gianluca Guida
2009-08-20 9:31 ` Gianluca Guida
2009-08-20 11:36 ` [PATCH v2][v2.6.29][XEN] " Miroslav Rezanina
2009-09-03 23:26 ` Jeremy Fitzhardinge [this message]
2009-09-03 23:26 ` [PATCH][v2.6.29][XEN] " Jeremy Fitzhardinge
2009-09-04 5:29 ` Miroslav Rezanina
[not found] <1152394510.61021250842386600.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2009-08-21 8:14 ` Miroslav Rezanina
2009-08-21 8:14 ` Miroslav Rezanina
2009-08-21 11:51 ` Gianluca Guida
2009-08-21 11:51 ` Gianluca Guida
[not found] <1582654680.152201253087647836.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2009-09-16 7:56 ` Miroslav Rezanina
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=4AA050A0.90609@goop.org \
--to=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mrezanin@redhat.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.