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] Simplify IO event handling since it's now onlyus

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH] Simplify IO event handling since it's now onlyused for IO done notification.
From: "Li, Xin B" <xin.b.li@xxxxxxxxx>
Date: Fri, 10 Nov 2006 11:15:29 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 09 Nov 2006 19:15:47 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AccEGeyAxUYCtUelSqeyOM8p7TlblwAWJ3RQ
Thread-topic: [Xen-devel] [PATCH] Simplify IO event handling since it's now onlyused for IO done notification.
>Subject: [Xen-devel] [PATCH] Simplify IO event handling since 
>it's now onlyused for IO done notification.
>
>Simplify IO event handling since it's now only used for IO done
>notification.

Keir,
For the old code, we need it because interrupt notification from qemu
may wake up a vcpu that is waiting for an IO done notification from
Qemu, however, now interrupt notification logic is seperated and using
hypercall, so only after Qemu changes IO slot state to
STATE_IORESP_READY, it will wake up the target vcpu.  Why we still need
wait_on_xen_event_channel now?
BTW, prepare_wait_on_xen_event_channel and wait_on_xen_event_channel
don't need port parameter.
-Xin

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

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