[Xen-devel] [PATCH 5/5] pciback: documentation for user-space quirks

[Chris <hap10@xxxxxxxxxxxxxx>]

This patch provides basic documentation for the per-device permissive
flag and the two policy files.  However, the general intent of this
patch set is to avoid the need for user interaction, so documentation is
somewhat sparse.

Signed-off-by: Chris Bookholt <hap10@xxxxxxxxxxxxxx>

diff -r b20580cf7fc1 docs/src/user.tex
--- a/docs/src/user.tex Wed Jul 12 16:34:39 2006 +0100
+++ b/docs/src/user.tex Thu Jul 13 15:13:53 2006 -0400
@@ -1343,6 +1343,29 @@ Unbind a device from its driver and bind
 
 Note that the "-n" option in the example is important as it causes echo to not
 output a new-line.
+
+\subsubsection{PCI Backend Configuration - User-space Quirks}
+Quirky devices (such as the Broadcom Tigon 3) may need write access to their
+configuration space registers.  Xen can be instructed to allow specified PCI
+devices write access to specific configuration space registers.  The policy may
+be found in:
+
+\centerline{ \path{/etc/xen/xend-pci-quirks.sxp} }
+
+The policy file is heavily commented and is intended to provide enough
+documentation for developers to extend it.
+
+\subsubsection{PCI Backend Configuration - Permissive Flag}
+If the user-space quirks approach doesn't meet your needs you may want to 
enable
+the permissive flag for that device.  To do so, first get the PCI domain, bus,
+slot, and function information from dom0 via \path{lspci}.  Then augment the
+user-space policy for permissive devices.  The permissive policy can be found
+in:
+
+\centerline{ \path{/etc/xen/xend-pci-permissive.sxp} }
+
+Currently, the only way to reset the permissive flag is to unbind the device
+from the PCI Backend driver.
 
 \subsubsection{PCI Frontend Configuration}
 To configure a domU to receive a PCI device:

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel