From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael S. Tsirkin" Subject: Re: [PATCH V2] VFIO driver: Non-privileged user level PCI drivers Date: Thu, 24 Jun 2010 18:03:35 +0300 Message-ID: <20100624150335.GA10501@redhat.com> References: <4c0eb470.1HMjondO00NIvFM6%pugs@cisco.com> <201006111515.53562.pugs@lyon-about.com> <20100613102339.GB4191@redhat.com> <201006171414.00878.pugs@lyon-about.com> <20100624122219.GD20761@8bytes.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Tom Lyon , randy.dunlap@oracle.com, linux-kernel@vger.kernel.org, kvm@vger.kernel.org, chrisw@sous-sol.org, hjk@linutronix.de, avi@redhat.com, gregkh@suse.de, aafabbri@cisco.com, scofeldm@cisco.com To: Joerg Roedel Return-path: Content-Disposition: inline In-Reply-To: <20100624122219.GD20761@8bytes.org> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On Thu, Jun 24, 2010 at 02:22:19PM +0200, Joerg Roedel wrote: > On Thu, Jun 17, 2010 at 02:14:00PM -0700, Tom Lyon wrote: > > On Sunday 13 June 2010 03:23:39 am Michael S. Tsirkin wrote: > > > OK, after more investigation, I realize you are right. > > We definitely need the IOMMU protection for interrupts, and > > if we have it, a lot of the code for config space protection is pointless. > > It does seem that the Intel intr_remapping code does what we want > > (accidentally) but that the AMD iommu code does not yet do any > > interrupt remapping. Joerg - can you comment? On the roadmap? > > Work on this is planned, but not at a high priority by now. I can > re-prioritize this item if needed. > > Joerg As a stop-gap measure, we could get by with a portable API that let us figure out whether a given iommu supports interrupt remapping. -- MST