[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140610204405.GB21390@kroah.com>
Date: Tue, 10 Jun 2014 13:44:05 -0700
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: David Vrabel <david.vrabel@...rix.com>
Cc: Daniel Kiper <daniel.kiper@...cle.com>,
linux-kernel@...r.kernel.org, stable@...r.kernel.org,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
Subject: Re: [PATCH 3.4 82/88] xen/setup: Populate freed MFNs from non-RAM
E820 entries and gaps to E820 RAM
On Tue, Jun 10, 2014 at 02:18:16PM +0100, David Vrabel wrote:
> On 10/06/14 10:30, Daniel Kiper wrote:
> > On Tue, Jun 10, 2014 at 10:07:27AM +0100, David Vrabel wrote:
> >> On 10/06/14 01:25, Greg Kroah-Hartman wrote:
> >>> 3.4-stable review patch. If anyone has any objections, please let me know.
> >>
> >> This is a new feature and not a bug fix. I don't think it (and patches
> >> 83-85) are suitable for stable.
> >
> > IIRC, this is the main patch fixing dom0 memory looses.
> > Earlier patches are preparatory stuff and later ones are
> > fixing bugs introduced by this patch and others. Konrad and I
> > picked only minimal set of patches to fix that issue in 3.4.
>
> This is not a bug fix. dom0 was previously required to use the balloon
> driver to recover memory freed during setup. This was annoying but not
> a bug.
>
> This patches makes significant changes to how much memory dom0 ends up.
> Depending on hardware, the dom0_mem option, and the (non)use of the
> balloon driver applying this could result is between 1 - 3 GB of
> additional memory allocated to dom0. This could result in there being
> insufficient host memory available to start a VM.
>
> Please do not add to 3.4.y.
Ok, I'll go drop these now, thanks.
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists