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] Per vcpu IO evtchn patch for HVM domain

To: "Li, Xin B" <xin.b.li@xxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Per vcpu IO evtchn patch for HVM domain
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Wed, 22 Feb 2006 18:52:04 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 22 Feb 2006 18:46:02 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <59D45D057E9702469E5775CBB56411F101B3964E@pdsmsx406>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <59D45D057E9702469E5775CBB56411F101B3964E@pdsmsx406>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 22 Feb 2006, at 12:45, Li, Xin B wrote:

Per vcpu IO evtchn patch for HVM domain.
We are starting to send patches to support SMP VMX guest, for SVM side,
should have a test to see if this patch breaks anything there.

Can you explain the bind_interdomain logic? Looks as though both the device model *and* Xen are doing bind_interdomain now? I'd prefer to do it just in the device model, especially since you had to punch a hole through to evtchn_bind_vcpu() to be able to do it within Xen!

 -- Keir


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