On 10/31/2016 12:49 PM, Jike Song wrote: > On 10/27/2016 05:29 AM, Kirti Wankhede wrote: >> Added details of sysfs ABI for mediated device framework >> >> Signed-off-by: Kirti Wankhede <kwankhede@xxxxxxxxxx> >> Signed-off-by: Neo Jia <cjia@xxxxxxxxxx> >> Change-Id: Icb0fd4ed58a2fa793fbcb1c3d5009a4403c1f3ac >> --- >> Documentation/ABI/testing/sysfs-bus-vfio-mdev | 111 ++++++++++++++++++++++++++ >> 1 file changed, 111 insertions(+) >> create mode 100644 Documentation/ABI/testing/sysfs-bus-vfio-mdev >> >> diff --git a/Documentation/ABI/testing/sysfs-bus-vfio-mdev b/Documentation/ABI/testing/sysfs-bus-vfio-mdev >> new file mode 100644 >> index 000000000000..452dbe39270e >> --- /dev/null >> +++ b/Documentation/ABI/testing/sysfs-bus-vfio-mdev >> @@ -0,0 +1,111 @@ >> +What: /sys/.../<device>/mdev_supported_types/ >> +Date: October 2016 >> +Contact: Kirti Wankhede <kwankhede@xxxxxxxxxx> >> +Description: >> + This directory contains list of directories of currently >> + supported mediated device types and their details for >> + <device>. Supported type attributes are defined by the >> + vendor driver who registers with Mediated device framework. >> + Each supported type is a directory whose name is created >> + by adding the device driver string as a prefix to the >> + string provided by the vendor driver. >> + >> +What: /sys/.../<device>/mdev_supported_types/<type-id>/ >> +Date: October 2016 >> +Contact: Kirti Wankhede <kwankhede@xxxxxxxxxx> >> +Description: >> + This directory gives details of supported type, like name, >> + description, available_instances, device_api etc. >> + 'device_api' and 'available_instances' are mandatory >> + attributes to be provided by vendor driver. 'name', >> + 'description' and other vendor driver specific attributes >> + are optional. >> + > > Hi Kirti, > > Is there any checking in the mdev framework that mandatory attributes > are actually provided? > No. These are exposed so that libvirt can use those to create devices. If those are not provided, libvirt would not work. Kirti. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
