Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1753836AbcKBH7y (ORCPT <rfc822;w@1wt.eu>);
        Wed, 2 Nov 2016 03:59:54 -0400
Received: from hqemgate15.nvidia.com ([216.228.121.64]:6432 "EHLO
        hqemgate15.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1752760AbcKBH7w (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 2 Nov 2016 03:59:52 -0400
X-PGP-Universal: processed;
        by hqpgpgate101.nvidia.com on Wed, 02 Nov 2016 00:59:50 -0700
Subject: Re: [PATCH v10 18/19] docs: Sysfs ABI for mediated device framework
To: Jike Song <jike.song@intel.com>
References: <1477517366-27871-1-git-send-email-kwankhede@nvidia.com>
 <1477517366-27871-19-git-send-email-kwankhede@nvidia.com>
 <5816F074.1010108@intel.com>
CC: <alex.williamson@redhat.com>, <pbonzini@redhat.com>,
        <kraxel@redhat.com>, <cjia@nvidia.com>, <qemu-devel@nongnu.org>,
        <kvm@vger.kernel.org>, <kevin.tian@intel.com>,
        <bjsdjshi@linux.vnet.ibm.com>, <linux-kernel@vger.kernel.org>
X-Nvconfidentiality: public
From: Kirti Wankhede <kwankhede@nvidia.com>
Message-ID: <1e834365-b1d2-57f5-1bae-659341b69951@nvidia.com>
Date: Wed, 2 Nov 2016 13:25:28 +0530
MIME-Version: 1.0
In-Reply-To: <5816F074.1010108@intel.com>
X-Originating-IP: [10.24.216.210]
X-ClientProxiedBy: DRHKMAIL102.nvidia.com (10.25.59.16) To
 bgmail102.nvidia.com (10.25.59.11)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 2145
Lines: 54



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@nvidia.com>
>> Signed-off-by: Neo Jia <cjia@nvidia.com>
>> 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@nvidia.com>
>> +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@nvidia.com>
>> +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.