On 2/5/21 4:40 AM, Jason Wang wrote:
>
> On 2021/2/4 下午7:15, Adrian Moreno wrote:
>> Sorry I have not followed this work as close as I would have wanted.
>> Some questions below.
>>
>> On 2/4/21 4:16 AM, Jason Wang wrote:
>>> On 2021/2/2 下午6:35, Parav Pandit wrote:
>>>> Linux vdpa interface allows vdpa device management functionality.
>>>> This includes adding, removing, querying vdpa devices.
>>>>
>>>> vdpa interface also includes showing supported management devices
>>>> which support such operations.
>>>>
>>>> This patchset includes kernel uapi headers and a vdpa tool.
>>>>
>>>> examples:
>>>>
>>>> $ vdpa mgmtdev show
>>>> vdpasim:
>>>> supported_classes net
>>>>
>>>> $ vdpa mgmtdev show -jp
>>>> {
>>>> "show": {
>>>> "vdpasim": {
>>>> "supported_classes": [ "net" ]
>>>> }
>>>> }
>>>> }
>>>>
>> How can a user establish the relationship between a mgmtdev and it's parent
>> device (pci vf, sf, etc)?
>
>
> Parav should know more but I try to answer.
>
> I think there should be BDF information in the mgmtdev show command if the
> parent is a PCI device, or we can simply show the parent here?
>
>
>>
>>>> Create a vdpa device of type networking named as "foo2" from
>>>> the management device vdpasim_net:
>>>>
>>>> $ vdpa dev add mgmtdev vdpasim_net name foo2
>>>>
>> I guess this command will accept a 'type' parameter once more
>> supported_classes
>> are added?
>
>
> This could be extended in the future.
>
>
>>
>> Also, will this tool also handle the vdpa driver binding or will the user
>> handle
>> that through the vdpa bus' sysfs interface?
>
>
> I think not, it's the configuration below the vdpa bus. The sysfs should be
> the
> only interface for managing driver binding.
>
Understood, thanks.
--
Adrián Moreno
