From: Miroslav Rezanina <mrezanin@redhat.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com,
Gianluca Guida <gianluca.guida@citrix.com>
Subject: Re: [PATCH][v2.6.29][XEN] Return unused memory to hypervisor
Date: Mon, 7 Sep 2009 08:41:54 -0400 (EDT) [thread overview]
Message-ID: <1864241231.701071252327314933.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com> (raw)
In-Reply-To: <4A8D7C26.5020902@goop.org>
----- "Jeremy Fitzhardinge" <jeremy@goop.org> wrote:
> From: "Jeremy Fitzhardinge" <jeremy@goop.org>
> To: "Miroslav Rezanina" <mrezanin@redhat.com>
> Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com, "Gianluca Guida" <gianluca.guida@citrix.com>
> Sent: Thursday, August 20, 2009 6:39:02 PM GMT +01:00 Amsterdam / Berlin / Bern / Rome / Stockholm / Vienna
> Subject: Re: [PATCH][v2.6.29][XEN] Return unused memory to hypervisor
>
> On 08/20/09 00:47, Miroslav Rezanina wrote:
> > there is handled e820 map in guest. However, this patch informs
> > hypervisor, that guest uses less memory than was assigned to it.
> > If hypervisor is not informed, memory is reserved for guest that
> > do not need it. If hypervisor is informed, he decrease memory
> > reservation for guest and unused memory is marked as free
> > for use by other guests.
> >
>
> Yes. But the guest will modify its own e820 map for a number of
> reasons; for example: reducing its own memory, or clearing a space
> for
> the PCI hole. In general we want to free any underlying pages which
> don't correspond to E820_RAM regions.
>
> J
> --
Hi Jeremy,
can you give me a practical example, where e820 map can have "hole" inside,
i.e. there will be block of memory not listed in e820 map that have listed
memory before and after it?
As I checked the source code, there is always removed memory from some point
till end of map, not from one adress till another. And I can't image how would
be such a case handled. Of course, there can be some special regions, as the PCI
hole, but these are marked as "Reserved".
There can be "reserved and returned" some inside memory, but this is already
handled by balloon driver. My patch returns memory that this driver can't use.
Regards,
Mirek
--
Miroslav Rezanina
Software Engineer - Virtualization Team - XEN kernel
next prev parent reply other threads:[~2009-09-07 12:41 UTC|newest]
Thread overview: 13+ 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 ` Miroslav Rezanina
2009-08-19 16:16 ` Jeremy Fitzhardinge
2009-08-20 7:47 ` Miroslav Rezanina
2009-08-20 16:39 ` Jeremy Fitzhardinge
2009-09-07 12:41 ` Miroslav Rezanina [this message]
2009-09-08 18:58 ` Jeremy Fitzhardinge
2009-08-20 9:31 ` [Xen-devel] " Gianluca Guida
2009-08-20 11:36 ` [PATCH v2][v2.6.29][XEN] " Miroslav Rezanina
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 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=1864241231.701071252327314933.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com \
--to=mrezanin@redhat.com \
--cc=gianluca.guida@citrix.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®