From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Tian, Kevin" <kevin.tian@intel.com>
Subject: Re: (v2) Design proposal for RMRR fix
Date: Wed, 14 Jan 2015 09:44:48 +0000
Message-ID: <AADFC41AFE54684AB9EE6CBC0274A5D1261451A1@SHSMSX101.ccr.corp.intel.com>
References: <54B3A71002000078000538E1@mail.emea.novell.com>
	<AADFC41AFE54684AB9EE6CBC0274A5D1261343B2@SHSMSX101.ccr.corp.intel.com>
	<54B3AB380200007800053917@mail.emea.novell.com>
	<AADFC41AFE54684AB9EE6CBC0274A5D126134459@SHSMSX101.ccr.corp.intel.com>
	<54B3AE8802000078000539B7@mail.emea.novell.com>
	<AADFC41AFE54684AB9EE6CBC0274A5D126134604@SHSMSX101.ccr.corp.intel.com>
	<CAFLBxZYN+dTg7OHrJwUi+_=K7rEGhZU6UScp9dRLN1zyfb41aA@mail.gmail.com>
	<AADFC41AFE54684AB9EE6CBC0274A5D126134784@SHSMSX101.ccr.corp.intel.com>
	<CAFLBxZYD5KAO4vOXi6+E+f7HL+cYzG+-OMG1t1C7aFA5BoUugQ@mail.gmail.com>
	<AADFC41AFE54684AB9EE6CBC0274A5D1261416F1@SHSMSX101.ccr.corp.intel.com>
	<20150113164546.GF28074@localhost.localdomain>
	<AADFC41AFE54684AB9EE6CBC0274A5D126144EDA@SHSMSX101.ccr.corp.intel.com>
	<54B63EC70200007800054A39@mail.emea.novell.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: <54B63EC70200007800054A39@mail.emea.novell.com>
Content-Language: en-US
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: Jan Beulich <JBeulich@suse.com>
Cc: "wei.liu2@citrix.com" <wei.liu2@citrix.com>, "ian.campbell@citrix.com" <ian.campbell@citrix.com>, "stefano.stabellini@eu.citrix.com" <stefano.stabellini@eu.citrix.com>, George Dunlap <George.Dunlap@eu.citrix.com>, "tim@xen.org" <tim@xen.org>, "ian.jackson@eu.citrix.com" <ian.jackson@eu.citrix.com>, "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>, "Zhang,
	Yang Z" <yang.z.zhang@intel.com>, "Chen, Tiejun" <tiejun.chen@intel.com>
List-Id: xen-devel@lists.xenproject.org

> From: Jan Beulich [mailto:JBeulich@suse.com]
> Sent: Wednesday, January 14, 2015 5:03 PM
> 
> >>> On 14.01.15 at 09:13, <kevin.tian@intel.com> wrote:
> >>  From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
> >> Sent: Wednesday, January 14, 2015 12:46 AM
> >>
> >> Perhaps an easier way of this is to use the existing
> >> mechanism we have - that is the XENMEM_memory_map (which
> >> BTW e820_host uses). If all of this is done in the libxl (which
> >> already does this based on the host E820, thought it can
> >> be modified to query the hypervisor for other 'reserved
> >> regions') and hvmloader is modified to use XENMEM_memory_map
> >> and base its E820 on that (and also QEMU-xen), then we solve
> >> this problem and also the http://bugs.xenproject.org/xen/bug/28?
> >
> > I'm not familiar with that option, but a quick search looks saying
> > it's only for PV guest?
> >
> > and please note XENMEM_memory_map only includes RAM entries
> > (looks also only for pv), while following above intention what we
> > really want is real e820_host w/ all entries filled.
> 
> But from the very beginning when these were proposed it was
> said that they would need extending from being PV/PVH only to
> also be usable for HVM. Such a change would be minimally
> intrusive afaict as at least the latter already is allowed for PVH
> too.
> 

if we make assumption on not breaking lowmem/highmem structure
in domain builder, then this change can be avoided.

Thanks
Kevin