From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Zhu, Lingshan" <lingshan.zhu@intel.com>
Cc: netdev@vger.kernel.org,
virtualization@lists.linux-foundation.org,
xieyongji@bytedance.com, gautam.dawar@amd.com
Subject: Re: [PATCH V3 6/6] vDPA: fix 'cast to restricted le16' warnings in vdpa.c
Date: Fri, 29 Jul 2022 05:39:05 -0400 [thread overview]
Message-ID: <20220729053615-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <05bf4c84-28dd-4956-4719-3a5361d151d8@intel.com>
On Fri, Jul 29, 2022 at 05:35:09PM +0800, Zhu, Lingshan wrote:
>
>
> On 7/29/2022 5:23 PM, Michael S. Tsirkin wrote:
> > On Fri, Jul 29, 2022 at 05:20:17PM +0800, Zhu, Lingshan wrote:
> > >
> > > On 7/29/2022 5:17 PM, Michael S. Tsirkin wrote:
> > > > On Fri, Jul 29, 2022 at 05:07:11PM +0800, Zhu, Lingshan wrote:
> > > > > On 7/29/2022 4:53 PM, Michael S. Tsirkin wrote:
> > > > > > On Fri, Jul 01, 2022 at 09:28:26PM +0800, Zhu Lingshan wrote:
> > > > > > > This commit fixes spars warnings: cast to restricted __le16
> > > > > > > in function vdpa_dev_net_config_fill() and
> > > > > > > vdpa_fill_stats_rec()
> > > > > > >
> > > > > > > Signed-off-by: Zhu Lingshan <lingshan.zhu@intel.com>
> > > > > > > ---
> > > > > > > drivers/vdpa/vdpa.c | 6 +++---
> > > > > > > 1 file changed, 3 insertions(+), 3 deletions(-)
> > > > > > >
> > > > > > > diff --git a/drivers/vdpa/vdpa.c b/drivers/vdpa/vdpa.c
> > > > > > > index 846dd37f3549..ed49fe46a79e 100644
> > > > > > > --- a/drivers/vdpa/vdpa.c
> > > > > > > +++ b/drivers/vdpa/vdpa.c
> > > > > > > @@ -825,11 +825,11 @@ static int vdpa_dev_net_config_fill(struct vdpa_device *vdev, struct sk_buff *ms
> > > > > > > config.mac))
> > > > > > > return -EMSGSIZE;
> > > > > > > - val_u16 = le16_to_cpu(config.status);
> > > > > > > + val_u16 = __virtio16_to_cpu(true, config.status);
> > > > > > > if (nla_put_u16(msg, VDPA_ATTR_DEV_NET_STATUS, val_u16))
> > > > > > > return -EMSGSIZE;
> > > > > > > - val_u16 = le16_to_cpu(config.mtu);
> > > > > > > + val_u16 = __virtio16_to_cpu(true, config.mtu);
> > > > > > > if (nla_put_u16(msg, VDPA_ATTR_DEV_NET_CFG_MTU, val_u16))
> > > > > > > return -EMSGSIZE;
> > > > > > Wrong on BE platforms with legacy interface, isn't it?
> > > > > > We generally don't handle legacy properly in VDPA so it's
> > > > > > not a huge deal, but maybe add a comment at least?
> > > > > Sure, I can add a comment here: this is for modern devices only.
> > > > >
> > > > > Thanks,
> > > > > Zhu Lingshan
> > > > Hmm. what "this" is for modern devices only here?
> > > this cast, for LE modern devices.
> > I think status existed in legacy for sure, and it's possible that
> > some legacy devices backported mtu and max_virtqueue_pairs otherwise
> > we would have these fields as __le not as __virtio, right?
> yes, that's the reason why it is virtio_16 than just le16.
>
> I may find a better solution to detect whether it is LE, or BE without a
> virtio_dev structure.
> Check whether vdpa_device->get_device_features() has VIRTIO_F_VERISON_1. If
> the device offers _F_VERSION_1, then it is a LE device,
> or it is a BE device, then we use __virtio16_to_cpu(false, config.status).
>
> Does this look good?
No since the question is can be a legacy driver with a transitional
device. I don't have a good idea yet. vhost has VHOST_SET_VRING_ENDIAN
and maybe we need something like this for config as well?
> >
> > > > > > > @@ -911,7 +911,7 @@ static int vdpa_fill_stats_rec(struct vdpa_device *vdev, struct sk_buff *msg,
> > > > > > > }
> > > > > > > vdpa_get_config_unlocked(vdev, 0, &config, sizeof(config));
> > > > > > > - max_vqp = le16_to_cpu(config.max_virtqueue_pairs);
> > > > > > > + max_vqp = __virtio16_to_cpu(true, config.max_virtqueue_pairs);
> > > > > > > if (nla_put_u16(msg, VDPA_ATTR_DEV_NET_CFG_MAX_VQP, max_vqp))
> > > > > > > return -EMSGSIZE;
> > > > > > > --
> > > > > > > 2.31.1
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2022-07-29 9:39 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220701132826.8132-1-lingshan.zhu@intel.com>
[not found] ` <20220701132826.8132-4-lingshan.zhu@intel.com>
2022-07-01 22:02 ` [PATCH V3 3/6] vDPA: allow userspace to query features of a vDPA device Parav Pandit via Virtualization
2022-07-04 4:46 ` Jason Wang
2022-07-04 12:53 ` Parav Pandit via Virtualization
[not found] ` <1e1e5f8c-d20e-4e54-5fc0-e12a7ba818a3@intel.com>
2022-07-05 11:56 ` Parav Pandit via Virtualization
[not found] ` <a59209f3-9005-b9f6-6f27-e136443aa3e1@intel.com>
2022-07-05 17:01 ` Parav Pandit via Virtualization
[not found] ` <814143c9-b7ab-a1c7-c5e2-cff8b024fc2f@intel.com>
2022-07-06 2:28 ` Parav Pandit via Virtualization
[not found] ` <cbd81bad-b188-2895-4606-326eac36b02f@intel.com>
2022-07-24 15:23 ` Parav Pandit via Virtualization
2022-07-27 8:15 ` Si-Wei Liu
[not found] ` <bfd46eb1-bc82-b1c8-f492-7bcaaada8aa4@intel.com>
2022-07-08 16:13 ` Parav Pandit via Virtualization
[not found] ` <20220701132826.8132-6-lingshan.zhu@intel.com>
2022-07-01 22:07 ` [PATCH V3 5/6] vDPA: answer num of queue pairs = 1 to userspace when VIRTIO_NET_F_MQ == 0 Parav Pandit via Virtualization
[not found] ` <ef1c42e8-2350-dd9c-c6c0-2e9bbe85adb4@intel.com>
2022-07-08 16:23 ` Parav Pandit via Virtualization
[not found] ` <00c1f5e8-e58d-5af7-cc6b-b29398e17c8b@intel.com>
2022-07-12 16:48 ` Parav Pandit via Virtualization
[not found] ` <c7c8f49c-484f-f5b3-39e6-0d17f396cca7@intel.com>
2022-07-13 3:06 ` Parav Pandit via Virtualization
[not found] ` <1246d2f1-2822-0edb-cd57-efc4015f05a2@intel.com>
2022-07-26 15:56 ` Parav Pandit via Virtualization
2022-07-26 19:52 ` Michael S. Tsirkin
2022-07-26 20:49 ` Parav Pandit via Virtualization
[not found] ` <19681358-fc81-be5b-c20b-7394a549f0be@intel.com>
2022-07-27 2:17 ` Parav Pandit via Virtualization
[not found] ` <e98fc062-021b-848b-5cf4-15bd63a11c5c@intel.com>
2022-07-27 3:47 ` Parav Pandit via Virtualization
2022-07-27 6:01 ` Michael S. Tsirkin
2022-07-27 6:54 ` Jason Wang
2022-07-27 9:02 ` Michael S. Tsirkin
2022-07-27 9:50 ` Jason Wang
2022-07-27 15:45 ` Michael S. Tsirkin
2022-07-28 1:21 ` Jason Wang
[not found] ` <459524bc-0e21-422b-31c1-39745fd25fac@intel.com>
2022-07-28 5:53 ` Jason Wang
2022-07-28 6:41 ` Michael S. Tsirkin
2022-08-01 4:50 ` Jason Wang
[not found] ` <4925d1db-51d1-148a-72e0-2347b20e82f4@intel.com>
2022-07-27 6:56 ` Jason Wang
2022-07-27 9:05 ` Michael S. Tsirkin
2022-07-27 7:50 ` Si-Wei Liu
2022-07-27 9:01 ` Michael S. Tsirkin
2022-07-27 10:09 ` Si-Wei Liu
2022-07-27 15:48 ` Michael S. Tsirkin
2022-07-28 7:22 ` Si-Wei Liu
[not found] ` <939bc589-b3ad-d317-8b1d-6da58e4670c0@intel.com>
2022-07-28 1:41 ` Si-Wei Liu
[not found] ` <685241b9-3487-489c-2784-2a2209f660ad@intel.com>
2022-07-28 21:54 ` Si-Wei Liu
2022-07-13 5:26 ` Michael S. Tsirkin
2022-07-26 15:54 ` Parav Pandit via Virtualization
2022-07-26 19:48 ` Michael S. Tsirkin
2022-07-26 20:53 ` Parav Pandit via Virtualization
[not found] ` <20220701132826.8132-5-lingshan.zhu@intel.com>
2022-07-01 22:12 ` [PATCH V3 4/6] vDPA: !FEATURES_OK should not block querying device config space Parav Pandit via Virtualization
2022-07-13 5:23 ` Michael S. Tsirkin
2022-07-27 9:43 ` Si-Wei Liu
[not found] ` <63242254-ba84-6810-dad8-34f900b97f2f@intel.com>
2022-07-28 0:56 ` Si-Wei Liu
2022-07-28 2:06 ` Jason Wang
2022-07-28 7:08 ` Si-Wei Liu
2022-07-28 7:36 ` Jason Wang
2022-07-28 8:20 ` spec clarification (was Re: [PATCH V3 4/6] vDPA: !FEATURES_OK should not block querying device config space) Si-Wei Liu
2022-07-28 11:28 ` Michael S. Tsirkin
2022-07-28 11:35 ` [PATCH V3 4/6] vDPA: !FEATURES_OK should not block querying device config space Michael S. Tsirkin
2022-07-28 22:12 ` Si-Wei Liu
[not found] ` <00e2e07e-1a2e-7af8-a060-cc9034e0d33f@intel.com>
2022-07-28 21:48 ` Si-Wei Liu
[not found] ` <c143e2da-208e-b046-9b8f-1780f75ed3e6@intel.com>
2022-07-29 20:55 ` Si-Wei Liu
2022-08-01 4:44 ` Jason Wang
2022-08-01 22:53 ` Si-Wei Liu
2022-08-01 22:58 ` Si-Wei Liu
2022-08-02 6:33 ` Jason Wang
2022-08-03 1:26 ` Si-Wei Liu
[not found] ` <213dec42-bd3d-2b5c-9003-276bc2a9f649@intel.com>
2022-08-03 23:09 ` Si-Wei Liu
[not found] ` <20220701132826.8132-7-lingshan.zhu@intel.com>
2022-07-01 22:18 ` [PATCH V3 6/6] vDPA: fix 'cast to restricted le16' warnings in vdpa.c Parav Pandit via Virtualization
[not found] ` <dea8be07-bc25-192c-ecd7-636cbdb2a629@intel.com>
2022-07-08 16:08 ` Parav Pandit via Virtualization
2022-07-29 8:53 ` Michael S. Tsirkin
[not found] ` <7ce4da7f-80aa-14d6-8200-c7f928f32b48@intel.com>
2022-07-29 9:17 ` Michael S. Tsirkin
[not found] ` <50b4e7ba-3e49-24b7-5c23-d8a76c61c924@intel.com>
2022-07-29 9:23 ` Michael S. Tsirkin
[not found] ` <05bf4c84-28dd-4956-4719-3a5361d151d8@intel.com>
2022-07-29 9:39 ` Michael S. Tsirkin [this message]
[not found] ` <87efac3e-2196-f9ad-1af1-a27470824eac@intel.com>
2022-07-29 10:16 ` Michael S. Tsirkin
2022-08-01 4:33 ` Jason Wang
2022-08-01 6:25 ` Michael S. Tsirkin
[not found] ` <20220701132826.8132-2-lingshan.zhu@intel.com>
2022-07-04 4:39 ` [PATCH V3 1/6] vDPA/ifcvf: get_config_size should return a value no greater than dev implementation Jason Wang
[not found] ` <b2b2fb5e-c1c2-84b6-0315-a6eef121cdac@intel.com>
2022-07-13 5:44 ` Michael S. Tsirkin
2022-07-13 5:31 ` Michael S. Tsirkin
[not found] ` <20220701132826.8132-3-lingshan.zhu@intel.com>
2022-07-04 4:43 ` [PATCH V3 2/6] vDPA/ifcvf: support userspace to query features and MQ of a management device Jason Wang
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=20220729053615-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=gautam.dawar@amd.com \
--cc=lingshan.zhu@intel.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=xieyongji@bytedance.com \
/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).