From: Ian Campbell <Ian.Campbell@XenSource.com>
To: "Zulauf, John" <john.zulauf@intel.com>
Cc: Gerd Hoffmann <kraxel@suse.de>,
Xen devel list <xen-devel@lists.xensource.com>
Subject: RE: xensource (pci) device id's?
Date: Thu, 01 Feb 2007 20:29:36 +0000 [thread overview]
Message-ID: <1170361776.12801.14.camel@localhost.localdomain> (raw)
In-Reply-To: <BD262A443AD428499D90AF8368C4528D310740@fmsmsx411.amr.corp.intel.com>
On Thu, 2007-02-01 at 12:02 -0800, Zulauf, John wrote:
> If we change all the PCI vendor ID's for the virtualized devices, how
> will the OS find the correct driver in standard HVM systems?
Gerd is proposing to change the subvendor/subdevice ID's which is
different to the regular vendor/device ID.
The purpose of the subvendor/subdevice ID is to allow manufacturers to
take an existing PCI device chipset (with a given vendor/device ID burnt
in) and incorporate it into a card of their own. They can then use their
own subvendor/subdevice ID for this card and presumably have their own
driver match on these IDs rather than the more generic ones to offer
advanced functionality which is dependant on the board not the chipset
etc.
Linux at least matches primarily on the vendor/device IDs with
subvendor/subdevice set to match anything so we would be OK here. From
include/linux/pci.h here is the macro typically used by drivers:
#define PCI_DEVICE(vend,dev) \
.vendor = (vend), .device = (dev), \
.subvendor = PCI_ANY_ID, .subdevice = PCI_ANY_ID
I'd be interested to know if this is true of other OSs such as Windows
and what matching procedure (if any) the PCI spec actually specifies.
Ian.
next prev parent reply other threads:[~2007-02-01 20:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-01 13:53 xensource (pci) device id's? Gerd Hoffmann
2007-02-01 13:58 ` Ian Campbell
2007-02-01 14:30 ` Gerd Hoffmann
2007-02-01 15:45 ` Gerd Hoffmann
2007-02-02 9:26 ` Ian Campbell
2007-02-02 9:47 ` Gerd Hoffmann
2007-02-02 18:25 ` Keir Fraser
2007-02-05 8:48 ` Gerd Hoffmann
2007-02-05 14:20 ` Gerd Hoffmann
2007-02-02 19:03 ` Keir Fraser
2007-02-05 2:29 ` EPS Signature Kaushik Barde
2007-02-05 2:52 ` Ian Pratt
2007-02-10 7:52 ` GDT access from DOM-0 driver Kaushik Barde
2007-02-11 1:33 ` EPS Signature Kaushik Barde
2007-02-11 10:09 ` Keir Fraser
2007-02-11 23:39 ` Kaushik Barde
2007-02-12 0:58 ` Keir Fraser
2007-02-12 2:36 ` Kaushik Barde
2007-02-12 7:43 ` Keir Fraser
2007-02-06 15:43 ` Andrew D. Ball
2007-02-05 8:55 ` xensource (pci) device id's? Gerd Hoffmann
2007-02-01 20:02 ` Zulauf, John
2007-02-01 20:29 ` Ian Campbell [this message]
2007-02-01 23:22 ` Keir Fraser
2007-02-02 8:15 ` Gerd Hoffmann
2007-02-01 23:17 ` Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1170361776.12801.14.camel@localhost.localdomain \
--to=ian.campbell@xensource.com \
--cc=john.zulauf@intel.com \
--cc=kraxel@suse.de \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.