mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-12-23 21:34:54 +03:00
9d15647dcb
By default Xen only allows guests to write "known safe" values into PCI configuration space, yet many devices require writes to other areas of the configuration space in order to operate properly. To allow writing any values Xen supports the 'permissive' setting, see xl.cfg(5) man page. This change models Xen's permissive setting by adding a writeFiltering attribute on the <source> element of a PCI hostdev. When writeFiltering is set to 'no', the Xen permissive setting will be enabled and guests will be able to write any values into the device's configuration space. The permissive setting remains disabled in the absense of the writeFiltering attribute, of if it is explicitly set to 'yes'. Signed-off-by: Jim Fehlig <jfehlig@suse.com> Signed-off-by: Simon Gaiser <simon@invisiblethingslab.com> Signed-off-by: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com> |
||
|---|---|---|
| .. | ||
| basic-hvm.json | ||
| basic-hvm.xml | ||
| basic-pv.json | ||
| basic-pv.xml | ||
| basic-pvh.json | ||
| basic-pvh.xml | ||
| cpu-shares-hvm.json | ||
| cpu-shares-hvm.xml | ||
| fullvirt-acpi-slic.json | ||
| fullvirt-acpi-slic.xml | ||
| fullvirt-cpuid-legacy-nest.json | ||
| fullvirt-cpuid-legacy-nest.xml | ||
| fullvirt-cpuid.json | ||
| fullvirt-cpuid.xml | ||
| max-eventchannels-hvm.json | ||
| max-eventchannels-hvm.xml | ||
| max-gntframes-hvm.json | ||
| max-gntframes-hvm.xml | ||
| moredevs-hvm.json | ||
| moredevs-hvm.xml | ||
| multiple-ip.json | ||
| multiple-ip.xml | ||
| variable-clock-hvm.json | ||
| variable-clock-hvm.xml | ||
| vnuma-hvm-legacy-nest.json | ||
| vnuma-hvm-legacy-nest.xml | ||
| vnuma-hvm.json | ||
| vnuma-hvm.xml | ||