From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [Xen-users] Xen memory allocation for dom0 and domU
Date: Thu, 5 Feb 2015 10:07:23 +0000
Message-ID: <1423130843.24924.53.camel@citrix.com>
References: <CAHyh4xjOykrATAUXGqNd1h1ThiZ5FX680Pn=_mKxtePaAF-ubQ@mail.gmail.com>
	<1423044595.17711.12.camel@citrix.com>
	<CAHyh4xiPZsqWkuthvHHC-ina7Ua2YHqeAiiP6U-3oAC=M+pnHw@mail.gmail.com>
	<1423061748.24924.10.camel@citrix.com>
	<1423068085.24924.36.camel@citrix.com>
	<CAHyh4xjXd_ZfBhXD1nBNYp=r28bYL4Vp-_6cyVjq+xYd_QYbNQ@mail.gmail.com>
	<CAHyh4xjZXenuLDttDQod+WspJEocVbyD+hHGaa1mNShLLnhZPw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <CAHyh4xjZXenuLDttDQod+WspJEocVbyD+hHGaa1mNShLLnhZPw@mail.gmail.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Jintack Lim <jintack@cs.columbia.edu>
Cc: xen-users@lists.xen.org, Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>, Tim Deegan <tim@xen.org>, Jan Beulich <JBeulich@suse.com>, xen-devel <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

On Wed, 2015-02-04 at 22:39 -0500, Jintack Lim wrote:
> On Wed, Feb 4, 2015 at 9:55 PM, Jintack Lim <jintack@cs.columbia.edu> wrote:
> > On Wed, Feb 4, 2015 at 11:41 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
> >>
> >> Patch for all this below. Jan, I don't think there is any (possibly
> >> historical on x86_32) x86 option we should be trying to be consistent
> >> with.
> >
> > Thanks, Ian.
> > Your patch works well!
> >
> 
> Will this patch be pushed to the upstream?
> 
> I was not able to find this patch in here.
>  http://xenbits.xen.org/gitweb/?p=xen.git;a=summary
> Could you tell me where is the patch now?

It'll be reviewed on the xen-devel list and eventually (hopefully) acked
and committed to the staging branch, from where it will be automatically
tested and propagate to the master branch.

Based on Jan's comments I'm thinking there will be at least one more
revision.

Depending on how invasive the final patch is I may also consider it for
backport to the stable 4.5.x.

Ian.