From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:39121)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <stefanha@gmail.com>) id 1T1CpE-00009m-FP
	for qemu-devel@nongnu.org; Tue, 14 Aug 2012 04:50:10 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <stefanha@gmail.com>) id 1T1CpD-0007yX-8r
	for qemu-devel@nongnu.org; Tue, 14 Aug 2012 04:50:08 -0400
Received: from mail-ey0-f173.google.com ([209.85.215.173]:50134)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <stefanha@gmail.com>) id 1T1CpD-0007wE-1R
	for qemu-devel@nongnu.org; Tue, 14 Aug 2012 04:50:07 -0400
Received: by eaac13 with SMTP id c13so48134eaa.4
	for <qemu-devel@nongnu.org>; Tue, 14 Aug 2012 01:50:05 -0700 (PDT)
Date: Tue, 14 Aug 2012 08:12:07 +0100
From: Stefan Hajnoczi <stefanha@gmail.com>
Message-ID: <20120814071207.GA14056@stefanha-thinkpad.localdomain>
References: <20120801050241.22163.78549.stgit@bling.home>
	<20120801051814.22163.66621.stgit@bling.home>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20120801051814.22163.66621.stgit@bling.home>
Subject: Re: [Qemu-devel] [PATCH 2/3] vfio: vfio-pci device assignment driver
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: aik@ozlabs.ru, aliguori@us.ibm.com, qemu-devel@nongnu.org, kvm@vger.kernel.org

On Tue, Jul 31, 2012 at 11:18:15PM -0600, Alex Williamson wrote:
> This adds the core of the QEMU VFIO-based PCI device assignment driver.
> To make use of this driver, enable CONFIG_VFIO, CONFIG_VFIO_IOMMU_TYPE1,
> and CONFIG_VFIO_PCI in your host Linux kernel config.  Load the vfio-pci
> module.  To assign device 0000:05:00.0 to a guest, do the following:
> 
> for dev in $(ls /sys/bus/pci/devices/0000:05:00.0/iommu_group/devices); do
>     vendor=$(cat /sys/bus/pci/devices/$dev/vendor)
>     device=$(cat /sys/bus/pci/devices/$dev/device)
>     if [ -e /sys/bus/pci/devices/$dev/driver ]; then
>         echo $dev > /sys/bus/pci/devices/$dev/driver/unbind
>     fi
>     echo $vendor $device > /sys/bus/pci/drivers/vfio-pci/new_id
> done

Both vfio-pci and the old driver successfully match the $vendor:$device.
What happens when another $vendor:$device PCI adapter is hotplugged into
the host?

Is there a way to bind vfio-pci on a per-adapter basis instead of a
per-$vendor:$device?

Stefan