WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH][v2] Hybrid extension support in Xen

To: Sheng Yang <sheng@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH][v2] Hybrid extension support in Xen
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Tue, 02 Feb 2010 14:01:43 +0000
Cc: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 02 Feb 2010 06:02:06 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <201002022152.27984.sheng@xxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcqkD0FQckvLvxRrTGC6L/yh1PSyGwAAP56f
Thread-topic: [Xen-devel] [PATCH][v2] Hybrid extension support in Xen
User-agent: Microsoft-Entourage/12.23.0.091001
On 02/02/2010 13:52, "Sheng Yang" <sheng@xxxxxxxxxxxxxxx> wrote:

>> I didn't even find where these get used, except to reserve an area in e820,
>> and it wasn't clear why that reservation is necessary.
>> 
> It has been used in the last [6/6] patch of Linux kernel side, which would use
> the pages to map grant table. It works the same as the MMIO region in PVonHVM
> device. Reserve it in BIOS because we think it's more elegant than depends on
> QEmu to provide the reserved memory space.

Hmm. Can't this be done in phases? It seems unnecessary to be making changes
solely to remove qemu dependencies in the intial patchset, when the patchset
does not actually achieve that aim.

I think an HVM guest with no PCI space is a little way off, and perhaps we
can find a better way than hardcoding an address in two places.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>