From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:42437) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TinZN-00069O-Ec for qemu-devel@nongnu.org; Wed, 12 Dec 2012 09:46:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TinZB-0002fz-FN for qemu-devel@nongnu.org; Wed, 12 Dec 2012 09:45:57 -0500 Received: from mx1.redhat.com ([209.132.183.28]:45374) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TinZB-0002fI-18 for qemu-devel@nongnu.org; Wed, 12 Dec 2012 09:45:45 -0500 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id qBCEjiGQ007731 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 12 Dec 2012 09:45:44 -0500 Date: Wed, 12 Dec 2012 16:48:54 +0200 From: "Michael S. Tsirkin" Message-ID: <20121212144854.GG15555@redhat.com> References: <1353320494-15033-1-git-send-email-pbonzini@redhat.com> <1353320494-15033-5-git-send-email-pbonzini@redhat.com> <20121212142207.GA15555@redhat.com> <50C894CB.9030406@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50C894CB.9030406@redhat.com> Subject: Re: [Qemu-devel] [PATCH 4/5] ivshmem: use symbolic constant for PCI ID, add to pci-ids.txt List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: qemu-devel@nongnu.org, kraxel@redhat.com On Wed, Dec 12, 2012 at 03:29:31PM +0100, Paolo Bonzini wrote: > Il 12/12/2012 15:22, Michael S. Tsirkin ha scritto: > >> > @@ -29,4 +29,6 @@ maintained as part of the virtio specification. > >> > 1af4:1100 Used as PCI Subsystem ID for existing hardware devices emulated > >> > by qemu. > >> > > >> > +1af4:1110 ivshmem device (shared memory, docs/specs/ivshmem_device_spec.txt) > >> > + > >> > All other device IDs are reserved. > >> > diff --git a/hw/ivshmem.c b/hw/ivshmem.c > >> > index f6dbb21..8adeb2c 100644 > >> > --- a/hw/ivshmem.c > >> > +++ b/hw/ivshmem.c > >> > @@ -800,7 +800,7 @@ static void ivshmem_class_init(ObjectClass *klass, void *data) > >> > k->init = pci_ivshmem_init; > >> > k->exit = pci_ivshmem_uninit; > >> > k->vendor_id = PCI_VENDOR_ID_REDHAT_QUMRANET; > >> > - k->device_id = 0x1110; > >> > + k->device_id = PCI_DEVICE_ID_QUMRANET_IVSHMEM; > >> > k->class_id = PCI_CLASS_MEMORY_RAM; > >> > dc->reset = ivshmem_reset; > >> > dc->props = ivshmem_properties; > >> > diff --git a/hw/pci.h b/hw/pci.h > >> > index 0719521..3704d5f 100644 > >> > --- a/hw/pci.h > >> > +++ b/hw/pci.h > >> > @@ -78,6 +78,7 @@ > >> > #define PCI_DEVICE_ID_VIRTIO_SCSI 0x1004 > >> > #define PCI_DEVICE_ID_VIRTIO_RNG 0x1005 > >> > #define PCI_DEVICE_ID_VIRTIO_9P 0x1009 > >> > +#define PCI_DEVICE_ID_QUMRANET_IVSHMEM 0x1110 > >> > > >> > #define FMT_PCIBUS PRIx64 > > Why _QUMRANET I wonder? > > > > Because it's under 0x1af4 (PCI_VENDOR_ID_REDHAT_QUMRANET), not 0x1b36 > (PCI_VENDOR_ID_REDHAT). > > Paolo Yes but so are all virtio devices are they not?