From mboxrd@z Thu Jan  1 00:00:00 1970
From: Wei Liu <wei.liu2@citrix.com>
Subject: Re: [edk2] Passing Xen memory map and resource map to
	OVMF
Date: Wed, 13 Nov 2013 11:58:11 +0000
Message-ID: <20131113115811.GC4948__8663.75306291065$1384344007$gmane$org@zion.uk.xensource.com>
References: <20131112183321.GN13369@zion.uk.xensource.com>
	<52827C0B.5040901@redhat.com>
	<1384326219.3560.9.camel@nilsson.home.kraxel.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Content-Disposition: inline
In-Reply-To: <1384326219.3560.9.camel@nilsson.home.kraxel.org>
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: Gerd Hoffmann <kraxel@redhat.com>
Cc: Wei Liu <wei.liu2@citrix.com>, "Jordan
	Justen (Intel address)" <jordan.l.justen@intel.com>, edk2-devel@lists.sourceforge.net, xen-devel@lists.xen.org, Igor Mammedov <imammedo@redhat.com>, Laszlo Ersek <lersek@redhat.com>
List-Id: xen-devel@lists.xenproject.org

On Wed, Nov 13, 2013 at 08:03:39AM +0100, Gerd Hoffmann wrote:
>   Hi,
> 
> > > The first thing that comes in mind is to reuse E820 table for memory map
> > > plus some extra fields for io / mmio resources. But I guess UEFI is the
> > > new world so stuffs like E820 from old world will be less popular. Any
> > > suggestion on existing table / data structure I can use?
> 
> What io/mmio ressources do you need to pass on?
> 

MMIO holes, IO range created by hvmloader.

OVMF should make use of that information instead of creating MMIO holes
etc of its own. See OvmfPkg/PlatformPei/Platform.c:MemMapInitialization.

> > As far as I can see, qemu exports an fw_cfg table called "etc/e820". See
> > qemu commit
> > 
> > commit 7d67110f2d9a6a2d6b5215a948abc95d07258735
> > Author: Gerd Hoffmann <kraxel@redhat.com>
> > Date:   Fri Oct 18 11:31:54 2013 +0200
> > 
> >     pc: add etc/e820 fw_cfg file
> 
> New in qemu 1.7  Was added exactly to deal with the 1TB limitation and
> also to allow for non-contiguous memory (not implemented yet in qemu,
> but if numa support is extended some day to support that we are fine
> interface-wise).
> 

This is probably too new for us. We're still fighting a regression in
1.6.

Wei.

> > Does this work when qemu is used in combination with Xen?
> 
> It should, might need windup in the xen machine type though (not fully
> sure how much code is shared between normal and xen machine types).
> 
> cheers,
>   Gerd
>