From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH] kvm tools: adds a PCI device that exports a host shared segment as a PCI BAR in the guest Date: Thu, 25 Aug 2011 08:41:43 +0300 Message-ID: <4E55E097.8000709@redhat.com> References: <20110824222510.GC14835@dancer.ca.sandia.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: penberg@kernel.org, Sasha Levin , kvm@vger.kernel.org To: David Evensky Return-path: Received: from mx1.redhat.com ([209.132.183.28]:56679 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752337Ab1HYFlt (ORCPT ); Thu, 25 Aug 2011 01:41:49 -0400 In-Reply-To: <20110824222510.GC14835@dancer.ca.sandia.gov> Sender: kvm-owner@vger.kernel.org List-ID: On 08/25/2011 01:25 AM, David Evensky wrote: > #define PCI_DEVICE_ID_VIRTIO_BLN 0x1005 > #define PCI_DEVICE_ID_VIRTIO_P9 0x1009 > #define PCI_DEVICE_ID_VESA 0x2000 > +#define PCI_DEVICE_ID_PCI_SHMEM 0x0001 > > #define PCI_VENDOR_ID_REDHAT_QUMRANET 0x1af4 > +#define PCI_VENDOR_ID_PCI_SHMEM 0x0001 > #define PCI_SUBSYSTEM_VENDOR_ID_REDHAT_QUMRANET 0x1af4 > > Please use a real life vendor ID from http://www.pcidatabase.com. If you're following an existing spec, you should pick the vendor ID matching the device you're emulating. If not, as seems to be the case here, you need your own, or permission from an existing owner of a vendor ID. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.