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

RE: [Xen-devel] [RFC][PATCH 4/6] HVM PCI Passthrough (non-IOMMU)


  • To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Guy Zana" <guy@xxxxxxxxxxxx>
  • Date: Sat, 2 Jun 2007 15:45:10 -0400
  • Delivery-date: Sat, 02 Jun 2007 12:48:16 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acej2E1juVhMSFpbRnuzdID01/diyQAG1qiQAFXGz4A=
  • Thread-topic: [Xen-devel] [RFC][PATCH 4/6] HVM PCI Passthrough (non-IOMMU)

 

> -----Original Message-----
> From: Tian, Kevin [mailto:kevin.tian@xxxxxxxxx] 
> Sent: Friday, June 01, 2007 5:45 AM
> To: Guy Zana; xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [Xen-devel] [RFC][PATCH 4/6] HVM PCI Passthrough 
> (non-IOMMU)
> 
> Hi, Guy,
>       The picture in my mind for polarity change is to change 
> generic level-triggered handle flow like:
> 
> When interrupt happens,
> ->ack():
>           1. Change pin's polarity
>           2. EOI
> 
> Do_IRQ_guest (either event to para-domain, or Assert/Deassert 
> virtual wire of HVM domain), or handled by Xen itself
> 
> ->end():
>           No-op
> 

That's a good way to go IMO. 
I actually thought about something similar, but being cautious, I tried to make 
as few changes as I could to see if it works at first.

Thanks,
Guy.

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