From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [PATCH] docs: record reservations of device IDs under the Xen vendor ID Date: Wed, 03 Jul 2013 21:15:39 +0100 Message-ID: References: <817F8DE966913E4D91404CA656535C8408A030@LONPEX01CL01.citrite.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <817F8DE966913E4D91404CA656535C8408A030@LONPEX01CL01.citrite.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: James Bulpin , "xen-devel@lists.xen.org" Cc: Ian Campbell List-Id: xen-devel@lists.xenproject.org On 03/07/2013 18:52, "James Bulpin" 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 Acked-by: Keir Fraser > 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