[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] [PATCH] Simplify IO event handling since it's now onlyused for IO done notification.


  • To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
  • 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
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • 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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.