Re: [Xen-devel] [PATCH] Citrix PV Bus device [V3]

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Wed, 2013-07-03 at 11:12 +0000, James Bulpin wrote:
> On Tue, 2 Jul 2013, Stefano Stabellini wrote:
> > - the Citrix [vendor id|device id] pair has to be different from the
> > xenproject one (0x5853|0x0001). I am sure we can arrange the
> > xenproject device id space so that Windows PV drivers vendors don't have
> > to acquire their own PCI vendor ids.
> 
> (removing qemu-devel)
> 
> I agree - this makes sense. There are already a few known uses of other
> device IDs such as:
> 
>   0002 - used by Citrix for a version of Windows PV drivers [1]

In the wild I presume?

>   c110 - Virtualized HID [2]
>   c147 - Virtualized Graphics Device [2]
> 
> I suggest we have a file somewhere in the Xen tree to record
> reservations, e.g. docs/misc/pci-device-reservations.txt - changes to
> this would then be managed via the usual patch submission process
> and therefore be transparent and subject to community review.

This sounds like a good idea to me.

Apart from grandfathering in 0002 lets keep the per-vendor IDs in the
0xc000-0xfffe range to start with, reducing the possibility of clashes
with community IDs assigned from the bottom up.

Is someone going to send an initial patch adding the currently know IDs?

>  For
> example we could allocate to a Xen vendor such as Citrix XenClient a
> range of device IDs like c100-c1ff and let it use the range as it
> desires.

Well, they'd presumably have to submit the patch themselves, but yes.

> In addition to these reservations we could encourage vendors to
> record individual device IDs within their reservation with
> pciids.sourceforge.net/www.pcidatabase.com as with the two XenClient
> cases above.

Good idea.

Ian.

> 
> Cheers,
> James
> 
> [1] http://pciids.sourceforge.net/
> [2] http://www.pcidatabase.com
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxx
> http://lists.xen.org/xen-devel



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel