libvirt/tests/nodedevschemadata/pci_1002_71c4.xml

<device>
  <name>pci_1002_71c4</name>
  <parent>pci_8086_27a1</parent>
  <capability type='pci'>
    <domain>0</domain>
    <bus>1</bus>
    <slot>0</slot>
    <function>0</function>
    <product id='0x71c4'>M56GL [Mobility FireGL V5200]</product>
    <vendor id='0x1002'>ATI Technologies Inc</vendor>
    <numa node='1'/>
  </capability>
</device>
Added complete set of RNG schemas for all XML formats 2009-01-27 18:29:53 +03:00			`<device>`
			`<name>pci_1002_71c4</name>`
			`<parent>pci_8086_27a1</parent>`
			`<capability type='pci'>`
			`<domain>0</domain>`
			`<bus>1</bus>`
			`<slot>0</slot>`
			`<function>0</function>`
			`<product id='0x71c4'>M56GL [Mobility FireGL V5200]</product>`
			`<vendor id='0x1002'>ATI Technologies Inc</vendor>`
nodedev: Export NUMA node locality for PCI devices A PCI device can be associated with a specific NUMA node. Later, when a guest is pinned to one NUMA node the PCI device can be assigned on different NUMA node. This makes DMA transfers travel across nodes and thus results in suboptimal performance. We should expose the NUMA node locality for PCI devices so management applications can make better decisions. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> 2014-05-07 20:07:12 +04:00			`<numa node='1'/>`
Added complete set of RNG schemas for all XML formats 2009-01-27 18:29:53 +03:00			`</capability>`
			`</device>`