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

RE: [Xen-ia64-devel] RE: Event channel vs current scheme speed [was vIOSAPIC and IRQs delivery]


  • To: "Tristan Gingold" <Tristan.Gingold@xxxxxxxx>, "Magenheimer, Dan \(HP Labs Fort Collins\)" <dan.magenheimer@xxxxxx>, <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Dong, Eddie" <eddie.dong@xxxxxxxxx>
  • Date: Fri, 10 Mar 2006 17:21:02 +0800
  • Delivery-date: Fri, 10 Mar 2006 09:23:41 +0000
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcZDZuWVEVQM1pUVRfKITTzrlxKfvgAu5SxQ
  • Thread-topic: [Xen-ia64-devel] RE: Event channel vs current scheme speed [was vIOSAPIC and IRQs delivery]

Tristan Gingold wrote:
> 
> Event channel is 1 hypercall *iif* callback is used.  If current
> event-channel (through IRQ) is used, this is not true.  And I am
> angry with callback. 
> 

It looked like you agree this suggestion (at least not against) at
Xensummit.
What changes your mind? 

BTW, callback support is on the way now. Kevin has sent out some
patch already. By the end of Q1, we should see this.



> Ask Dan.  I don't know why he didn't use event channel to deliver
> IRQs.  By seeing the amount of optimization for IRQs, I deduced he
> didn't want to deviler IRQs with event-channel.  Maybe I am wrong.
> 
At the very beginning, taking a shortcut is defintely OK, because the
community at that time is very small. Now we have double digits active 
people in the community so we can do more :-)
BTW, last year our design are based on that dom0 own all machine 
resource, so that shortcut is correct and reasonable. If I had been
implementing this code, I would have taken shortcut too.
Eddie

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


 


Rackspace

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