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] [RFC][PATCH 4/6] HVM PCI Passthrough (non-IOMMU)

To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] [RFC][PATCH 4/6] HVM PCI Passthrough (non-IOMMU)
From: "Guy Zana" <guy@xxxxxxxxxxxx>
Date: Sat, 2 Jun 2007 15:45:10 -0400
Delivery-date: Sat, 02 Jun 2007 12:48:16 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <D470B4E54465E3469E2ABBC5AFAC390F013B1EBF@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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: 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

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