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: IOEMU & XEN] Change ioreq layout and reduce its

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH: IOEMU & XEN] Change ioreq layout and reduce its size
From: "Xu, Dongxiao" <dongxiao.xu@xxxxxxxxx>
Date: Thu, 29 Oct 2009 21:21:30 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Delivery-date: Thu, 29 Oct 2009 06:21:55 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C70F3A6B.18B8B%keir.fraser@xxxxxxxxxxxxx>
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>
References: <C70F3A6B.18B8B%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcpYkwKRYYkSzUNFTkGlvHQ1NdgxkwABblAA
Thread-topic: [Xen-devel] [PATCH: IOEMU & XEN] Change ioreq layout and reduce its size
Keir Fraser wrote:
> [Ian, please apply the attached ioemu patch and then send me an
> updated QEMU_TAG. The change to the ioreq layout requires the ioemu
> and xen-unstable patch check-ins to be closely synchronised.]
> 
> Reduce size of Xen-qemu shared ioreq structure to 32 bytes. This has
> two advantages:

Hi, Keir, 
        Reduce the ioreq structure has these advantages indeed, but do we need 
to consider the following compatibility issues? Thanks!
1) HVM guest could migrate/save/restore between the new and old hypervisor if 
vcpu number is less than 32. 
2) Old qemu could work with new hypervisor if guest vcpu number is less than 
32. 

Best Regards, 
-- Dongxiao

>  1. We can support up to 128 VCPUs with a single shared page
>  2. If/when we want to go beyond 128 VCPUs, a whole number of ioreq_t
> structures will pack into a single shared page, so a multi-page array
> will have no ioreq_t straddling a page boundary
> 
> Also, while modifying qemu, replace a 32-entry vcpu-indexed array
> with a dynamically-allocated array.
> 
> Signed-off-by: Keir Fraser <keir.fraser@xxxxxxxxxx>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

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