From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:41405)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1Tj5EC-0001xz-05
	for qemu-devel@nongnu.org; Thu, 13 Dec 2012 04:37:17 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1Tj5EB-0001GO-1e
	for qemu-devel@nongnu.org; Thu, 13 Dec 2012 04:37:15 -0500
Received: from mx1.redhat.com ([209.132.183.28]:18741)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1Tj5EA-0001GJ-QF
	for qemu-devel@nongnu.org; Thu, 13 Dec 2012 04:37:14 -0500
Message-ID: <50C9A1BF.1000808@redhat.com>
Date: Thu, 13 Dec 2012 10:37:03 +0100
From: Paolo Bonzini <pbonzini@redhat.com>
MIME-Version: 1.0
References: <1355157952-2321-1-git-send-email-fred.konrad@greensocs.com>
	<1355157952-2321-8-git-send-email-fred.konrad@greensocs.com>
	<CAFEAcA8rEg2S84Pz=pZ5FvvRdJbwwp8o-fAxVGne6_eN7LXstQ@mail.gmail.com>
	<50C8C4A2.7010709@suse.de>
	<CAFEAcA8264ymxVZKTbBQeGT_h1HSMgRscn6wyOFHQ3fnKYG-Ag@mail.gmail.com>
	<50C8C6E9.9050207@redhat.com> <20121212212217.GB23087@redhat.com>
In-Reply-To: <20121212212217.GB23087@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [RFC PATCH v7 7/8] virtio-pci-blk : Switch to new
	API.
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: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>, aliguori@us.ibm.com, e.voevodin@samsung.com, mark.burton@greensocs.com, qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>, stefanha@redhat.com, cornelia.huck@de.ibm.com, =?ISO-8859-1?Q?Andreas_F=E4?= =?ISO-8859-1?Q?rber?= <afaerber@suse.de>, fred.konrad@greensocs.com

Il 12/12/2012 22:22, Michael S. Tsirkin ha scritto:
> > > It should be equally
> > > valid to just use the PCI transport plugged into a VirtioDevice,
> > > both of which were created by the user with -device [and for
> > > new transports, separate transport and backend should be the
> > > standard]. That means the virtio-bus interface needs a way for
> > > the backend to announce to the transport what it is so that
> > > the PCI transport can set the right PCI IDs.
> > 
> > There is such an interface (the device_id, aka VIRTIO_ID_*).  Then
> > virtio-pci needs a mapping from the device_id to the (default)
> > vendor_id/device_id/class tuple.
> 
> At least device id and vedor id are easy.

Class too, this is a new device virtio-pci so it doesn't need to support
old machine types.

Paolo