From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael S. Tsirkin" Subject: Re: [RFC PATCH 0/5] QEMU VFIO device assignment Date: Mon, 12 Jul 2010 14:03:12 +0300 Message-ID: <20100712110312.GA25835@redhat.com> References: <20100711180910.20121.93313.stgit@localhost6.localdomain6> <4C3A0AB1.3070302@redhat.com> <1278873437.20397.29.camel@x201> <4C3A10D9.6050609@redhat.com> <1278879889.20397.143.camel@x201> <4C3AB652.4000106@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Alex Williamson , kvm@vger.kernel.org, qemu-devel@nongnu.org, pugs@cisco.com, chrisw@redhat.com To: Avi Kivity Return-path: Received: from mx1.redhat.com ([209.132.183.28]:58641 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751748Ab0GLLI3 (ORCPT ); Mon, 12 Jul 2010 07:08:29 -0400 Content-Disposition: inline In-Reply-To: <4C3AB652.4000106@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On Mon, Jul 12, 2010 at 09:29:38AM +0300, Avi Kivity wrote: > On 07/11/2010 11:24 PM, Alex Williamson wrote: > > > >One other thing to be aware of is that vfio requires devices to be > >PCI-2.3 compliant in order to support DisINTx. This allows vfio to > >support devices making use of shared INTx interrupts, but excludes older > >devices that users maybe managed to get assigned to an exclusive > >interrupt for kvm style assignment. > > > >I suppose we might be able to make vfio work with either pci 2.3 devices > >or older devices with exclusive interrupts if that ends up affecting > >many users. > > PCI 2.3 is already old enough (6-7 years?) I believe it was made a standard in 2002. > that I believe we can require it. > > -- > I have a truly marvellous patch that fixes the bug which this > signature is too narrow to contain. From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=33428 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OYGsA-0003Vx-MC for qemu-devel@nongnu.org; Mon, 12 Jul 2010 07:08:31 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OYGs9-0002DB-35 for qemu-devel@nongnu.org; Mon, 12 Jul 2010 07:08:30 -0400 Received: from mx1.redhat.com ([209.132.183.28]:27879) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OYGs8-0002D3-R1 for qemu-devel@nongnu.org; Mon, 12 Jul 2010 07:08:29 -0400 Date: Mon, 12 Jul 2010 14:03:12 +0300 From: "Michael S. Tsirkin" Message-ID: <20100712110312.GA25835@redhat.com> References: <20100711180910.20121.93313.stgit@localhost6.localdomain6> <4C3A0AB1.3070302@redhat.com> <1278873437.20397.29.camel@x201> <4C3A10D9.6050609@redhat.com> <1278879889.20397.143.camel@x201> <4C3AB652.4000106@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4C3AB652.4000106@redhat.com> Subject: [Qemu-devel] Re: [RFC PATCH 0/5] QEMU VFIO device assignment List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: chrisw@redhat.com, Alex Williamson , qemu-devel@nongnu.org, kvm@vger.kernel.org, pugs@cisco.com On Mon, Jul 12, 2010 at 09:29:38AM +0300, Avi Kivity wrote: > On 07/11/2010 11:24 PM, Alex Williamson wrote: > > > >One other thing to be aware of is that vfio requires devices to be > >PCI-2.3 compliant in order to support DisINTx. This allows vfio to > >support devices making use of shared INTx interrupts, but excludes older > >devices that users maybe managed to get assigned to an exclusive > >interrupt for kvm style assignment. > > > >I suppose we might be able to make vfio work with either pci 2.3 devices > >or older devices with exclusive interrupts if that ends up affecting > >many users. > > PCI 2.3 is already old enough (6-7 years?) I believe it was made a standard in 2002. > that I believe we can require it. > > -- > I have a truly marvellous patch that fixes the bug which this > signature is too narrow to contain.