libvirt/tests/nodedevschemadata/mdev_c60cc60c_c60c_c60c_c60c_c60cc60cc60c.xml

<device>
  <name>mdev_c60cc60c_c60c_c60c_c60c_c60cc60cc60c_0_0_0052</name>
  <path>/sys/devices/css0/0.0.0052/c60cc60c-c60c-c60c-c60c-c60cc60cc60c</path>
  <parent>css_0_0_0052</parent>
  <driver>
    <name>vfio_ccw_mdev</name>
  </driver>
  <capability type='mdev'>
    <type id='vfio_ccw-io'/>
    <uuid>c60cc60c-c60c-c60c-c60c-c60cc60cc60c</uuid>
    <parent_addr>0.0.0052</parent_addr>
    <iommuGroup number='4'/>
  </capability>
</device>
nodedev: add an active config to mdev The configuration of a defined mdev can be modified after the mdev is started. The defined configuration and the active configuration can therefore run out of sync. Handle this by storing the modifiable data which is the mdev type and attributes in two separate active and defined configurations. mdevctl supports with callout scripts to do an attribute retrieval of started mdevs which is already implemented in libvirt. Signed-off-by: Boris Fiuczynski <fiuczy@linux.ibm.com> Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Jonathon Jongsma <jjongsma@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com> 2024-02-22 13:02:01 +00:00			`<device>`
			`<name>mdev_c60cc60c_c60c_c60c_c60c_c60cc60cc60c_0_0_0052</name>`
			`<path>/sys/devices/css0/0.0.0052/c60cc60c-c60c-c60c-c60c-c60cc60cc60c</path>`
			`<parent>css_0_0_0052</parent>`
			`<driver>`
			`<name>vfio_ccw_mdev</name>`
			`</driver>`
			`<capability type='mdev'>`
			`<type id='vfio_ccw-io'/>`
			`<uuid>c60cc60c-c60c-c60c-c60c-c60cc60cc60c</uuid>`
			`<parent_addr>0.0.0052</parent_addr>`
			`<iommuGroup number='4'/>`
			`</capability>`
			`</device>`