* [PATCH] docs: record reservations of device IDs under the Xen vendor ID
@ 2013-07-03 17:52 James Bulpin
2013-07-03 20:15 ` Keir Fraser
0 siblings, 1 reply; 3+ messages in thread
From: James Bulpin @ 2013-07-03 17:52 UTC (permalink / raw)
To: xen-devel@lists.xen.org; +Cc: Ian Campbell
This patch introduces a documentation file to record reservations of
ranges of PCI device IDs within the Xen vendor ID 0x5853.
Signed-off-by: James Bulpin <james.bulpin@citrix.com>
diff -r cbf91a963462 docs/misc/pci-device-reservations.txt
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/docs/misc/pci-device-reservations.txt Wed Jul 03 18:34:31 2013 +0100
@@ -0,0 +1,32 @@
+PCI vendor ID 0x5853 has been reserved for use by Xen systems in order to
+advertise certain virtual hardware to guest virtual machines. The primary
+use of this is with device ID 0x0001 to advertise the Xen Platform PCI
+device - the presence of this virtual device enables a guest Operating
+System (subject to the availability of suitable drivers) to make use of
+paravirtualisation features such as disk and network devices etc.
+
+Some Xen vendors wish to provide alternative and/or additional guest drivers
+that can bind to virtual devices. This may be done using the Xen PCI vendor
+ID of 0x5853 and Xen-vendor/device specific PCI device IDs. This file
+records reservations made within the device ID range in order to avoid
+multiple Xen vendors using conflicting IDs.
+
+Guidelines
+ 1. A vendor may request a range of device IDs by submitting a patch to
+ this file.
+ 2. Vendor allocations should be in the range 0xc000-0xfffe to reduce the
+ possibility of clashes with community IDs assigned from the bottom up.
+ 3. The vendor is responsible for allocations within the range and should
+ try to record specific device IDs in PCI ID databases such as
+ http://pciids.sourceforge.net and http//www.pcidatabase.com
+
+Reservations
+============
+
+ range | vendor/product
+--------------+--------------------------------------------------------------
+0x0001 | (Xen Platform PCI device)
+0x0002 | Citrix XenServer (grandfathered allocation for XenServer 6.1)
+0xc000-0xc0ff | Citrix XenServer
+0xc100-0xc1ff | Citrix XenClient
+
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] docs: record reservations of device IDs under the Xen vendor ID
2013-07-03 17:52 [PATCH] docs: record reservations of device IDs under the Xen vendor ID James Bulpin
@ 2013-07-03 20:15 ` Keir Fraser
2013-07-04 10:40 ` Ian Campbell
0 siblings, 1 reply; 3+ messages in thread
From: Keir Fraser @ 2013-07-03 20:15 UTC (permalink / raw)
To: James Bulpin, xen-devel@lists.xen.org; +Cc: Ian Campbell
On 03/07/2013 18:52, "James Bulpin" <James.Bulpin@eu.citrix.com> wrote:
> This patch introduces a documentation file to record reservations of
> ranges of PCI device IDs within the Xen vendor ID 0x5853.
>
> Signed-off-by: James Bulpin <james.bulpin@citrix.com>
Acked-by: Keir Fraser <keir@xen.org>
> diff -r cbf91a963462 docs/misc/pci-device-reservations.txt
> --- /dev/null Thu Jan 01 00:00:00 1970 +0000
> +++ b/docs/misc/pci-device-reservations.txt Wed Jul 03 18:34:31 2013 +0100
> @@ -0,0 +1,32 @@
> +PCI vendor ID 0x5853 has been reserved for use by Xen systems in order to
> +advertise certain virtual hardware to guest virtual machines. The primary
> +use of this is with device ID 0x0001 to advertise the Xen Platform PCI
> +device - the presence of this virtual device enables a guest Operating
> +System (subject to the availability of suitable drivers) to make use of
> +paravirtualisation features such as disk and network devices etc.
> +
> +Some Xen vendors wish to provide alternative and/or additional guest drivers
> +that can bind to virtual devices. This may be done using the Xen PCI vendor
> +ID of 0x5853 and Xen-vendor/device specific PCI device IDs. This file
> +records reservations made within the device ID range in order to avoid
> +multiple Xen vendors using conflicting IDs.
> +
> +Guidelines
> + 1. A vendor may request a range of device IDs by submitting a patch to
> + this file.
> + 2. Vendor allocations should be in the range 0xc000-0xfffe to reduce the
> + possibility of clashes with community IDs assigned from the bottom up.
> + 3. The vendor is responsible for allocations within the range and should
> + try to record specific device IDs in PCI ID databases such as
> + http://pciids.sourceforge.net and http//www.pcidatabase.com
> +
> +Reservations
> +============
> +
> + range | vendor/product
> +--------------+--------------------------------------------------------------
> +0x0001 | (Xen Platform PCI device)
> +0x0002 | Citrix XenServer (grandfathered allocation for XenServer 6.1)
> +0xc000-0xc0ff | Citrix XenServer
> +0xc100-0xc1ff | Citrix XenClient
> +
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] docs: record reservations of device IDs under the Xen vendor ID
2013-07-03 20:15 ` Keir Fraser
@ 2013-07-04 10:40 ` Ian Campbell
0 siblings, 0 replies; 3+ messages in thread
From: Ian Campbell @ 2013-07-04 10:40 UTC (permalink / raw)
To: Keir Fraser; +Cc: James Bulpin, xen-devel@lists.xen.org
On Wed, 2013-07-03 at 21:15 +0100, Keir Fraser wrote:
> On 03/07/2013 18:52, "James Bulpin" <James.Bulpin@eu.citrix.com> wrote:
>
> > This patch introduces a documentation file to record reservations of
> > ranges of PCI device IDs within the Xen vendor ID 0x5853.
> >
> > Signed-off-by: James Bulpin <james.bulpin@citrix.com>
>
> Acked-by: Keir Fraser <keir@xen.org>
I have applied this.
>
> > diff -r cbf91a963462 docs/misc/pci-device-reservations.txt
> > --- /dev/null Thu Jan 01 00:00:00 1970 +0000
> > +++ b/docs/misc/pci-device-reservations.txt Wed Jul 03 18:34:31 2013 +0100
> > @@ -0,0 +1,32 @@
> > +PCI vendor ID 0x5853 has been reserved for use by Xen systems in order to
> > +advertise certain virtual hardware to guest virtual machines. The primary
> > +use of this is with device ID 0x0001 to advertise the Xen Platform PCI
> > +device - the presence of this virtual device enables a guest Operating
> > +System (subject to the availability of suitable drivers) to make use of
> > +paravirtualisation features such as disk and network devices etc.
> > +
> > +Some Xen vendors wish to provide alternative and/or additional guest drivers
> > +that can bind to virtual devices. This may be done using the Xen PCI vendor
> > +ID of 0x5853 and Xen-vendor/device specific PCI device IDs. This file
> > +records reservations made within the device ID range in order to avoid
> > +multiple Xen vendors using conflicting IDs.
> > +
> > +Guidelines
> > + 1. A vendor may request a range of device IDs by submitting a patch to
> > + this file.
> > + 2. Vendor allocations should be in the range 0xc000-0xfffe to reduce the
> > + possibility of clashes with community IDs assigned from the bottom up.
> > + 3. The vendor is responsible for allocations within the range and should
> > + try to record specific device IDs in PCI ID databases such as
> > + http://pciids.sourceforge.net and http//www.pcidatabase.com
> > +
> > +Reservations
> > +============
> > +
> > + range | vendor/product
> > +--------------+--------------------------------------------------------------
> > +0x0001 | (Xen Platform PCI device)
> > +0x0002 | Citrix XenServer (grandfathered allocation for XenServer 6.1)
> > +0xc000-0xc0ff | Citrix XenServer
> > +0xc100-0xc1ff | Citrix XenClient
> > +
> >
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xen.org
> > http://lists.xen.org/xen-devel
>
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2013-07-04 10:40 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-07-03 17:52 [PATCH] docs: record reservations of device IDs under the Xen vendor ID James Bulpin
2013-07-03 20:15 ` Keir Fraser
2013-07-04 10:40 ` Ian Campbell
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).