From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: a ton of kernel issues
Date: Thu, 15 Dec 2011 11:26:59 -0500
Message-ID: <20111215162659.GC7272@phenom.dumpdata.com>
References: <CAJeBh4sxdNTxM_oLFAuA6Mw75=LaYysrpS5b8NsZMbkf_swNVw@mail.gmail.com>
	<4EE72A94.6040904@gmail.com> <4EE75080.1000909@citrix.com>
	<1323783428.20077.298.camel@zakaz.uk.xensource.com>
	<4EE7BC9B.6040003@gmail.com>
	<1323815427.20936.96.camel@dagon.hellion.org.uk>
	<4EE7D75B.6080209@gmail.com>
	<1323847523.20936.110.camel@dagon.hellion.org.uk>
	<1323864969.20077.405.camel@zakaz.uk.xensource.com>
	<4EE9EBF5.8000402@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <4EE9EBF5.8000402@gmail.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: George Shuklin <george.shuklin@gmail.com>
Cc: "sandr8@gmail.com" <sandr8@gmail.com>, "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, Ian Campbell <Ian.Campbell@citrix.com>, David Vrabel <david.vrabel@citrix.com>
List-Id: xen-devel@lists.xenproject.org

On Thu, Dec 15, 2011 at 04:45:41PM +0400, George Shuklin wrote:
> On 14.12.2011 16:16, Ian Campbell wrote:
> >I take it back, there is indeed a bug in the PV ops kernel in this
> >regard.
> >
> >It works with xm/xend because they set the maximum reservation for
> >guests to static-max on boot. xl (and, I think, xapi) instead set the
> >maximum reservation to the current balloon target and change it
> >dynamically as the target is changed (as a method of enforcing the
> >targets). However the pvops kernel incorrectly uses the maximum
> >reservation at boot to size the physical address space for guests.
> >
> >The patch below fixes this.
> >
> >
> (skip)
> 
> I've checked this patch against current vanilla v3.2-rc5 - it fix
> problem I wrote about.

Excellent. I added a 'Reported-and-Tested-by' with your name.
> 
> Is any chance that fix will go to release of 3.2?

That is the plan.
>