From: Si-Wei Liu <si-wei.liu@oracle.com>
To: Jason Wang <jasowang@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Zhu, Lingshan" <lingshan.zhu@intel.com>
Cc: virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, kvm@vger.kernel.org, parav@nvidia.com,
xieyongji@bytedance.com, gautam.dawar@amd.com
Subject: Re: [PATCH 2/2] vDPA: conditionally read fields in virtio-net dev
Date: Thu, 18 Aug 2022 16:20:30 -0700 [thread overview]
Message-ID: <f0b6ea5c-1783-96d2-2d9f-e5cf726b0fc0@oracle.com> (raw)
In-Reply-To: <54aa5a5c-69e2-d372-3e0c-b87f595d213c@redhat.com>
On 8/17/2022 9:15 PM, Jason Wang wrote:
>
> 在 2022/8/17 18:37, Michael S. Tsirkin 写道:
>> On Wed, Aug 17, 2022 at 05:43:22PM +0800, Zhu, Lingshan wrote:
>>>
>>> On 8/17/2022 5:39 PM, Michael S. Tsirkin wrote:
>>>> On Wed, Aug 17, 2022 at 05:13:59PM +0800, Zhu, Lingshan wrote:
>>>>> On 8/17/2022 4:55 PM, Michael S. Tsirkin wrote:
>>>>>> On Wed, Aug 17, 2022 at 10:14:26AM +0800, Zhu, Lingshan wrote:
>>>>>>> Yes it is a little messy, and we can not check _F_VERSION_1
>>>>>>> because of
>>>>>>> transitional devices, so maybe this is the best we can do for now
>>>>>> I think vhost generally needs an API to declare config space
>>>>>> endian-ness
>>>>>> to kernel. vdpa can reuse that too then.
>>>>> Yes, I remember you have mentioned some IOCTL to set the endian-ness,
>>>>> for vDPA, I think only the vendor driver knows the endian,
>>>>> so we may need a new function vdpa_ops->get_endian().
>>>>> In the last thread, we say maybe it's better to add a comment for
>>>>> now.
>>>>> But if you think we should add a vdpa_ops->get_endian(), I can work
>>>>> on it for sure!
>>>>>
>>>>> Thanks
>>>>> Zhu Lingshan
>>>> I think QEMU has to set endian-ness. No one else knows.
>>> Yes, for SW based vhost it is true. But for HW vDPA, only
>>> the device & driver knows the endian, I think we can not
>>> "set" a hardware's endian.
>> QEMU knows the guest endian-ness and it knows that
>> device is accessed through the legacy interface.
>> It can accordingly send endian-ness to the kernel and
>> kernel can propagate it to the driver.
>
>
> I wonder if we can simply force LE and then Qemu can do the endian
> conversion?
convert from LE for config space fields only, or QEMU has to forcefully
mediate and covert endianness for all device memory access including
even the datapath (fields in descriptor and avail/used rings)? I hope
it's not the latter, otherwise it loses the point to use vDPA for
datapath acceleration.
Even if its the former, it's a little weird for vendor device to
implement a LE config space with BE ring layout, although still possible...
-Siwei
>
> Thanks
>
>
>>
>>> So if you think we should add a vdpa_ops->get_endian(),
>>> I will drop these comments in the next version of
>>> series, and work on a new patch for get_endian().
>>>
>>> Thanks,
>>> Zhu Lingshan
>> Guests don't get endian-ness from devices so this seems pointless.
>>
>
next prev parent reply other threads:[~2022-08-18 23:20 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 9:26 [PATCH 0/2] allow userspace to query device features Zhu Lingshan
2022-08-15 9:26 ` [PATCH 1/2] vDPA: allow userspace to query features of a vDPA device Zhu Lingshan
2022-08-15 18:15 ` Si-Wei Liu
2022-08-16 1:49 ` Zhu, Lingshan
2022-08-16 2:07 ` Parav Pandit
2022-08-16 4:21 ` Zhu, Lingshan
2022-08-15 9:26 ` [PATCH 2/2] vDPA: conditionally read fields in virtio-net dev Zhu Lingshan
2022-08-15 15:52 ` Michael S. Tsirkin
2022-08-15 23:32 ` Si-Wei Liu
2022-08-16 1:58 ` Zhu, Lingshan
2022-08-16 4:26 ` Zhu, Lingshan
2022-08-16 7:58 ` Si-Wei Liu
2022-08-16 9:08 ` Zhu, Lingshan
2022-08-16 23:14 ` Si-Wei Liu
2022-08-17 2:14 ` Zhu, Lingshan
2022-08-17 8:55 ` Michael S. Tsirkin
2022-08-17 9:13 ` Zhu, Lingshan
2022-08-17 9:39 ` Michael S. Tsirkin
2022-08-17 9:43 ` Zhu, Lingshan
2022-08-17 10:37 ` Michael S. Tsirkin
2022-08-18 4:15 ` Jason Wang
2022-08-18 7:58 ` Zhu, Lingshan
2022-08-18 23:20 ` Si-Wei Liu [this message]
2022-08-19 0:42 ` Jason Wang
2022-08-19 3:52 ` Michael S. Tsirkin
2022-08-20 8:55 ` Si-Wei Liu
2022-08-22 5:07 ` Zhu, Lingshan
2022-08-23 3:26 ` Jason Wang
2022-08-23 6:52 ` Zhu, Lingshan
2022-08-30 9:43 ` Zhu, Lingshan
2022-08-26 6:23 ` Si-Wei Liu
2022-09-02 6:03 ` Jason Wang
2022-09-02 6:14 ` Michael S. Tsirkin
2022-09-05 3:54 ` Jason Wang
2022-08-16 2:32 ` Parav Pandit
2022-08-16 4:18 ` Zhu, Lingshan
2022-08-16 21:02 ` Parav Pandit
2022-08-16 21:09 ` Michael S. Tsirkin
2022-08-17 2:03 ` Zhu, Lingshan
2022-08-18 4:18 ` Jason Wang
2022-08-18 6:38 ` Zhu, Lingshan
2022-08-18 17:20 ` Parav Pandit
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=f0b6ea5c-1783-96d2-2d9f-e5cf726b0fc0@oracle.com \
--to=si-wei.liu@oracle.com \
--cc=gautam.dawar@amd.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lingshan.zhu@intel.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=parav@nvidia.com \
--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).