From: Keir Fraser <keir.xen@gmail.com>
To: James Bulpin <James.Bulpin@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Cc: Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [PATCH] docs: record reservations of device IDs under the Xen vendor ID
Date: Wed, 03 Jul 2013 21:15:39 +0100 [thread overview]
Message-ID: <CDFA44FB.2C015%keir.xen@gmail.com> (raw)
In-Reply-To: <817F8DE966913E4D91404CA656535C8408A030@LONPEX01CL01.citrite.net>
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
next prev parent reply other threads:[~2013-07-03 20:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2013-07-04 10:40 ` Ian Campbell
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=CDFA44FB.2C015%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=Ian.Campbell@citrix.com \
--cc=James.Bulpin@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
/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.