| Message ID | 20250304132253.23955-1-frediano.ziglio@cloud.com (mailing list archive) |
|---|---|
| State | New |
| Headers | show |
| Series | [v2] docs: Add some details on XenServer PCI devices | expand |
On Tue Mar 4, 2025 at 1:22 PM GMT, Frediano Ziglio wrote: > Describe the usage of devices 5853:0002 and 5853:C000. > > Signed-off-by: Frediano Ziglio <frediano.ziglio@cloud.com> > --- > Changes since v1: > - address minor comments > --- > docs/man/xen-pci-device-reservations.7.pod | 7 +++++++ > 1 file changed, 7 insertions(+) > > diff --git a/docs/man/xen-pci-device-reservations.7.pod b/docs/man/xen-pci-device-reservations.7.pod > index 9ddf3a18ad..adc325069c 100644 > --- a/docs/man/xen-pci-device-reservations.7.pod > +++ b/docs/man/xen-pci-device-reservations.7.pod > @@ -10,6 +10,9 @@ 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. > +XenServer, for Windows machines, may present Xen Platform device with device > +ID 0x0002 instead of 0x0001. Device 0x0001 and 0x0002 should be mutually > +exclusive. > > Some Xen vendors wish to provide alternative and/or additional guest drivers > that can bind to virtual devices[1]. This may be done using the Xen PCI > @@ -86,4 +89,8 @@ and unplug protocol. > libxl provides support for creation of a single additional xen-pvdevice. > See the vendor_device parameter in xl.cfg(5). > > +XenServer might present a xen-pvdevice device with ID 0xC000. > +Such device is a placeholder for Windows update usage and is always exposed > +in conjunction with a Xen Platform PCI device, usually with ID 0x0002 > + > =back LGTM Reviewed-by: Alejandro Vallejo <alejandro.vallejo@cloud.com> Cheers, Alejandro
On Tue, Mar 4, 2025 at 1:23 PM Frediano Ziglio <frediano.ziglio@cloud.com> wrote: > > Describe the usage of devices 5853:0002 and 5853:C000. > > Signed-off-by: Frediano Ziglio <frediano.ziglio@cloud.com> > --- > Changes since v1: > - address minor comments > --- > docs/man/xen-pci-device-reservations.7.pod | 7 +++++++ > 1 file changed, 7 insertions(+) > > diff --git a/docs/man/xen-pci-device-reservations.7.pod b/docs/man/xen-pci-device-reservations.7.pod > index 9ddf3a18ad..adc325069c 100644 > --- a/docs/man/xen-pci-device-reservations.7.pod > +++ b/docs/man/xen-pci-device-reservations.7.pod > @@ -10,6 +10,9 @@ 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. > +XenServer, for Windows machines, may present Xen Platform device with device > +ID 0x0002 instead of 0x0001. Device 0x0001 and 0x0002 should be mutually > +exclusive. > > Some Xen vendors wish to provide alternative and/or additional guest drivers > that can bind to virtual devices[1]. This may be done using the Xen PCI > @@ -86,4 +89,8 @@ and unplug protocol. > libxl provides support for creation of a single additional xen-pvdevice. > See the vendor_device parameter in xl.cfg(5). > > +XenServer might present a xen-pvdevice device with ID 0xC000. > +Such device is a placeholder for Windows update usage and is always exposed > +in conjunction with a Xen Platform PCI device, usually with ID 0x0002 > + > =back Any additional comment? Frediano
diff --git a/docs/man/xen-pci-device-reservations.7.pod b/docs/man/xen-pci-device-reservations.7.pod index 9ddf3a18ad..adc325069c 100644 --- a/docs/man/xen-pci-device-reservations.7.pod +++ b/docs/man/xen-pci-device-reservations.7.pod @@ -10,6 +10,9 @@ 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. +XenServer, for Windows machines, may present Xen Platform device with device +ID 0x0002 instead of 0x0001. Device 0x0001 and 0x0002 should be mutually +exclusive. Some Xen vendors wish to provide alternative and/or additional guest drivers that can bind to virtual devices[1]. This may be done using the Xen PCI @@ -86,4 +89,8 @@ and unplug protocol. libxl provides support for creation of a single additional xen-pvdevice. See the vendor_device parameter in xl.cfg(5). +XenServer might present a xen-pvdevice device with ID 0xC000. +Such device is a placeholder for Windows update usage and is always exposed +in conjunction with a Xen Platform PCI device, usually with ID 0x0002 + =back
Describe the usage of devices 5853:0002 and 5853:C000. Signed-off-by: Frediano Ziglio <frediano.ziglio@cloud.com> --- Changes since v1: - address minor comments --- docs/man/xen-pci-device-reservations.7.pod | 7 +++++++ 1 file changed, 7 insertions(+)