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: "Xu, Dongxiao" <dongxiao.xu@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH: IOEMU & XEN] Change ioreq layout and reduce its size
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Thu, 29 Oct 2009 13:58:38 +0000
Cc: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Delivery-date: Thu, 29 Oct 2009 06:59:18 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <EADF0A36011179459010BDF5142A457501CED5FAE0@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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: AcpYkwKRYYkSzUNFTkGlvHQ1NdgxkwABblAAAAHLgmE=
Thread-topic: [Xen-devel] [PATCH: IOEMU & XEN] Change ioreq layout and reduce its size
User-agent: Microsoft-Entourage/12.20.0.090605
On 29/10/2009 13:21, "Xu, Dongxiao" <dongxiao.xu@xxxxxxxxx> wrote:

>> 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.

It still can, as the ioreq struct is private to the hypervisor and qemu,
neither of which is migrated/saved with the guest.

> 2) Old qemu could work with new hypervisor if guest vcpu number is less than
> 32. 

Qemu, like the toolstack, is expected to be upgraded with the hypervisor.

 -- Keir



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

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