From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Evensky Subject: Re: [PATCH] kvm tools: adds a PCI device that exports a host shared segment as a PCI BAR in the guest Date: Wed, 24 Aug 2011 23:01:02 -0700 Message-ID: <20110825060102.GC24996@dancer.ca.sandia.gov> References: <20110824222510.GC14835@dancer.ca.sandia.gov> <4E55E097.8000709@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: David Evensky , penberg@kernel.org, Sasha Levin , kvm@vger.kernel.org To: Avi Kivity Return-path: Received: from sentry-two.sandia.gov ([132.175.109.14]:40276 "EHLO sentry-two.sandia.gov" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752354Ab1HYGBP (ORCPT ); Thu, 25 Aug 2011 02:01:15 -0400 Content-Disposition: inline In-Reply-To: <4E55E097.8000709@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: I don't know if there is a PCI card that only provides a region of memory. I'm not really trying to provide emulation for a known piece of hardware, so I picked values that weren't being used since there didn't appear to be an 'unknown'. I'll ask around. \dae On Thu, Aug 25, 2011 at 08:41:43AM +0300, Avi Kivity wrote: > 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. > > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html