From: "Zhu, Lingshan" <lingshan.zhu@intel.com>
To: Eli Cohen <elic@nvidia.com>, Jason Wang <jasowang@redhat.com>
Cc: mst <mst@redhat.com>,
virtualization <virtualization@lists.linux-foundation.org>,
netdev <netdev@vger.kernel.org>, Parav Pandit <parav@nvidia.com>
Subject: Re: [PATCH 3/6] vDPA/ifcvf: support userspace to query device feature bits
Date: Mon, 6 Jun 2022 16:24:22 +0800 [thread overview]
Message-ID: <52eedc6b-d5dc-538a-6380-361f5812a7ec@intel.com> (raw)
In-Reply-To: <DM8PR12MB5400F0F46CD4B0749A60FE8BABDE9@DM8PR12MB5400.namprd12.prod.outlook.com>
On 6/2/2022 3:46 PM, Eli Cohen wrote:
>
>> -----Original Message-----
>> From: Jason Wang <jasowang@redhat.com>
>> Sent: Thursday, June 2, 2022 10:32 AM
>> To: Zhu Lingshan <lingshan.zhu@intel.com>
>> Cc: mst <mst@redhat.com>; virtualization <virtualization@lists.linux-foundation.org>; netdev <netdev@vger.kernel.org>; Eli Cohen
>> <elic@nvidia.com>; Parav Pandit <parav@nvidia.com>
>> Subject: Re: [PATCH 3/6] vDPA/ifcvf: support userspace to query device feature bits
>>
>> On Thu, Jun 2, 2022 at 10:48 AM Zhu Lingshan <lingshan.zhu@intel.com> wrote:
>>> This commit supports userspace to query device feature bits
>>> by filling the relevant netlink attribute.
>>>
>>> There are two types of netlink attributes:
>>> VDPA_ATTR_DEV_XXXX work for virtio devices config space, and
>>> VDPA_ATTR_MGMTDEV_XXXX work for the management devices.
>>>
>>> This commit fixes a misuse of VDPA_ATTR_DEV_SUPPORTED_FEATURES,
>>> this attr is for a virtio device, not management devices.
>>>
>>> Thus VDPA_ATTR_MGMTDEV_SUPPORTED_FEATURES is introduced for
>>> reporting management device features, and VDPA_ATTR_DEV_SUPPORTED_FEATURES
>>> for virtio devices feature bits.
>>>
>>> Signed-off-by: Zhu Lingshan <lingshan.zhu@intel.com>
>>> ---
>>> drivers/vdpa/vdpa.c | 15 ++++++++++-----
>>> include/uapi/linux/vdpa.h | 1 +
>>> 2 files changed, 11 insertions(+), 5 deletions(-)
>>>
>>> diff --git a/drivers/vdpa/vdpa.c b/drivers/vdpa/vdpa.c
>>> index 2b75c00b1005..c820dd2b0307 100644
>>> --- a/drivers/vdpa/vdpa.c
>>> +++ b/drivers/vdpa/vdpa.c
>>> @@ -508,7 +508,7 @@ static int vdpa_mgmtdev_fill(const struct vdpa_mgmt_dev *mdev, struct sk_buff *m
>>> err = -EMSGSIZE;
>>> goto msg_err;
>>> }
>>> - if (nla_put_u64_64bit(msg, VDPA_ATTR_DEV_SUPPORTED_FEATURES,
>>> + if (nla_put_u64_64bit(msg, VDPA_ATTR_MGMTDEV_SUPPORTED_FEATURES,
>> Adding Eli and Parav.
>>
>> If I understand correctly, we can't provision virtio features right
>> now. This means, the vDPA instance should have the same features as
>> its parent (management device).
> A management device should be read as "a management device capable of
> instantiating a virtio device". Thus, I see no reason to introduce another attribute.
> VDPA_ATTR_DEV_SUPPORTED_FEATURES is the capability of the management
> device to spawn a virtio device with certain features.
This may not be true because the "managed" device may have different
feature bits than the "management" device.
E.g., we can choose not to provide MQ feature for a managed device.
As Jason said, it is about provisioning, and we need two different attrs
anyway.
Thanks,
Zhu Lingshan
>
>> And it seems to me if we can do things like this, we need first allow
>> the features to be provisioned. (And this change breaks uABI)
>>
>> Thanks
>>
>>
>>> mdev->supported_features, VDPA_ATTR_PAD)) {
>>> err = -EMSGSIZE;
>>> goto msg_err;
>>> @@ -827,7 +827,7 @@ static int vdpa_dev_net_mq_config_fill(struct vdpa_device *vdev,
>>> static int vdpa_dev_net_config_fill(struct vdpa_device *vdev, struct sk_buff *msg)
>>> {
>>> struct virtio_net_config config = {};
>>> - u64 features;
>>> + u64 features_device, features_driver;
>>> u16 val_u16;
>>>
>>> vdpa_get_config_unlocked(vdev, 0, &config, sizeof(config));
>>> @@ -844,12 +844,17 @@ static int vdpa_dev_net_config_fill(struct vdpa_device *vdev, struct sk_buff *ms
>>> if (nla_put_u16(msg, VDPA_ATTR_DEV_NET_CFG_MTU, val_u16))
>>> return -EMSGSIZE;
>>>
>>> - features = vdev->config->get_driver_features(vdev);
>>> - if (nla_put_u64_64bit(msg, VDPA_ATTR_DEV_NEGOTIATED_FEATURES, features,
>>> + features_driver = vdev->config->get_driver_features(vdev);
>>> + if (nla_put_u64_64bit(msg, VDPA_ATTR_DEV_NEGOTIATED_FEATURES, features_driver,
>>> VDPA_ATTR_PAD))
>>> return -EMSGSIZE;
>>>
>>> - return vdpa_dev_net_mq_config_fill(vdev, msg, features, &config);
>>> + features_device = vdev->config->get_device_features(vdev);
>>> + if (nla_put_u64_64bit(msg, VDPA_ATTR_DEV_SUPPORTED_FEATURES, features_device,
>>> + VDPA_ATTR_PAD))
>>> + return -EMSGSIZE;
>>> +
>>> + return vdpa_dev_net_mq_config_fill(vdev, msg, features_device, &config);
>>> }
>>>
>>> static int
>>> diff --git a/include/uapi/linux/vdpa.h b/include/uapi/linux/vdpa.h
>>> index 1061d8d2d09d..70a3672c288f 100644
>>> --- a/include/uapi/linux/vdpa.h
>>> +++ b/include/uapi/linux/vdpa.h
>>> @@ -30,6 +30,7 @@ enum vdpa_attr {
>>> VDPA_ATTR_MGMTDEV_BUS_NAME, /* string */
>>> VDPA_ATTR_MGMTDEV_DEV_NAME, /* string */
>>> VDPA_ATTR_MGMTDEV_SUPPORTED_CLASSES, /* u64 */
>>> + VDPA_ATTR_MGMTDEV_SUPPORTED_FEATURES, /* u64 */
>>>
>>> VDPA_ATTR_DEV_NAME, /* string */
>>> VDPA_ATTR_DEV_ID, /* u32 */
>>> --
>>> 2.31.1
>>>
next prev parent reply other threads:[~2022-06-06 8:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 2:38 [PATCH 0/6] ifcvf/vDPA: support query device config space through netlink Zhu Lingshan
2022-06-02 2:38 ` [PATCH 1/6] vDPA/ifcvf: get_config_size should return a value no greater than dev implementation Zhu Lingshan
2022-06-02 7:11 ` Jason Wang
2022-06-06 8:17 ` Zhu, Lingshan
2022-06-02 2:38 ` [PATCH 2/6] vDPA/ifcvf: support userspace to query features and MQ of a management device Zhu Lingshan
2022-06-02 7:21 ` Jason Wang
2022-06-06 8:18 ` Zhu, Lingshan
2022-06-02 2:38 ` [PATCH 3/6] vDPA/ifcvf: support userspace to query device feature bits Zhu Lingshan
2022-06-02 7:32 ` Jason Wang
2022-06-02 7:46 ` Eli Cohen
2022-06-06 8:24 ` Zhu, Lingshan [this message]
2022-06-02 2:38 ` [PATCH 4/6] vDPA: !FEATURES_OK should not block querying device config space Zhu Lingshan
2022-06-02 7:36 ` Jason Wang
2022-06-06 8:19 ` Zhu, Lingshan
2022-06-02 2:38 ` [PATCH 5/6] vDPA: answer num of queue pairs = 1 to userspace when VIRTIO_NET_F_MQ == 0 Zhu Lingshan
2022-06-02 7:38 ` Jason Wang
2022-06-06 8:21 ` Zhu, Lingshan
2022-06-07 6:14 ` Jason Wang
2022-06-07 8:40 ` Zhu, Lingshan
2022-06-02 2:38 ` [PATCH 6/6] vDPA: fix 'cast to restricted le16' warnings in vdpa_dev_net_config_fill() Zhu Lingshan
2022-06-02 7:40 ` Jason Wang
2022-06-06 8:22 ` Zhu, Lingshan
2022-06-07 6:15 ` Jason Wang
2022-06-07 6:41 ` Zhu, Lingshan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52eedc6b-d5dc-538a-6380-361f5812a7ec@intel.com \
--to=lingshan.zhu@intel.com \
--cc=elic@nvidia.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=parav@nvidia.com \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).