From: Paul Durrant <paul.durrant@citrix.com>
To: xen-devel@lists.xen.org
Cc: Paul Durrant <paul.durrant@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>
Subject: [PATCH] docs: Add some words describing xen-pvdevice
Date: Wed, 13 Nov 2013 16:09:32 +0000 [thread overview]
Message-ID: <1384358972-38832-1-git-send-email-paul.durrant@citrix.com> (raw)
This patch adds a short description of xen-pvdevice to
pci-device-reservations.txt, which contains the canonical list
of device IDs that may be used to create xen-pvdevice instances.
Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
Cc: Ian Campbell <ian.campbell@citrix.com>
---
docs/misc/pci-device-reservations.txt | 31 +++++++++++++++++++++++++++++--
1 file changed, 29 insertions(+), 2 deletions(-)
diff --git a/docs/misc/pci-device-reservations.txt b/docs/misc/pci-device-reservations.txt
index 19bd9d5..62d86c3 100644
--- a/docs/misc/pci-device-reservations.txt
+++ b/docs/misc/pci-device-reservations.txt
@@ -6,8 +6,8 @@ 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
+that can bind to virtual devices[1]. 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.
@@ -29,3 +29,30 @@ Reservations
0x0002 | Citrix XenServer (grandfathered allocation for XenServer 6.1)
0xc000-0xc0ff | Citrix XenServer
0xc100-0xc1ff | Citrix XenClient
+
+[1] Upstream QEMU provides a parameterized device called xen-pvdevice that
+ can be used to host guest drivers. Execute:
+
+ qemu-system-i386 -device xen-pvdevice,help
+
+ for a list of all parameters. The following parameters are relevant to
+ driver binding:
+
+ vendor-id (default 0x5853): The PCI vendor ID and subsystem vendor
+ ID of the device.
+ device-id (must be specified): The PCI device ID and subsystem device
+ ID of the device.
+ revision (default 0x01): The PCI revision of the device
+
+ Also the size parameter (default 0x400000) can be used to specify the
+ size of the single MMIO BAR that the device exposes. This area may be
+ used by drivers for mapping grant tables, etc.
+
+ Note that the presence of the Xen Platform PCI device is generally a
+ pre-requisite for an additional xen-pvdevice as it is the platform
+ device that provides that IO ports necessary for unplugging emulated
+ devices. See hvm-emulated-unplug.markdown for details of the IO ports
+ and unplug protocol.
+
+ libxl provides support for creation of a single additional xen-pvdevice.
+ See the vendor_device parameter in xl.cfg(5).
--
1.7.10.4
next reply other threads:[~2013-11-13 16:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 16:09 Paul Durrant [this message]
2013-11-19 14:34 ` [PATCH] docs: Add some words describing xen-pvdevice Ian Campbell
2013-11-29 10:39 ` 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=1384358972-38832-1-git-send-email-paul.durrant@citrix.com \
--to=paul.durrant@citrix.com \
--cc=ian.campbell@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 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).