From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [RFC PATCH 0/5] QEMU VFIO device assignment Date: Mon, 12 Jul 2010 09:29:38 +0300 Message-ID: <4C3AB652.4000106@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> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org, pugs@cisco.com, chrisw@redhat.com, mst@redhat.com To: Alex Williamson Return-path: Received: from mx1.redhat.com ([209.132.183.28]:15662 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753332Ab0GLGaK (ORCPT ); Mon, 12 Jul 2010 02:30:10 -0400 In-Reply-To: <1278879889.20397.143.camel@x201> Sender: kvm-owner@vger.kernel.org List-ID: 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?) 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.