mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gianluca Guida <gianluca.guida@citrix.com>
To: Miroslav Rezanina <mrezanin@redhat.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Gianluca Guida <Gianluca.Guida@eu.citrix.com>
Subject: Re: [PATCH][v2.6.29][XEN] Return unused memory to hypervisor
Date: Fri, 21 Aug 2009 12:51:06 +0100	[thread overview]
Message-ID: <19086.35370.70561.378736@gianluca.uk.xensource.com> (raw)
In-Reply-To: <1378245818.61101250842487688.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>

Miroslav Rezanina writes:
 > ----- Original Message -----
 > 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
 > 
 > I agree. However, I'm not sure if xen supports such a precise handling.

Xen will just get a list of mfn to remove from the domain. That is
precise enough. The scenario Jeremy is describing does happen,
especially in dom0 kernels.

G.

  reply	other threads:[~2009-08-21 12:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
     [not found] <1582654680.152201253087647836.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2009-09-16  7:56 ` Miroslav Rezanina
     [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
2009-09-08 18:58           ` Jeremy Fitzhardinge
2009-09-03 23:26   ` Jeremy Fitzhardinge
2009-09-04  5:29     ` 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=19086.35370.70561.378736@gianluca.uk.xensource.com \
    --to=gianluca.guida@citrix.com \
    --cc=Gianluca.Guida@eu.citrix.com \
    --cc=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 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®