From: Si-Wei Liu <si-wei.liu@oracle.com>
To: "Zhu, Lingshan" <lingshan.zhu@intel.com>,
jasowang@redhat.com, mst@redhat.com
Cc: netdev@vger.kernel.org, xieyongji@bytedance.com,
gautam.dawar@amd.com, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH 2/2] vDPA: conditionally read fields in virtio-net dev
Date: Tue, 16 Aug 2022 01:08:47 -0700 [thread overview]
Message-ID: <517a5f0b-e484-abdc-3ddd-7e46d8b7ff7e@oracle.com> (raw)
In-Reply-To: <9b6292f3-9bd5-ecd8-5e42-cd5d12f036e7@oracle.com>
[-- Attachment #1.1: Type: text/plain, Size: 375 bytes --]
On 8/16/2022 12:58 AM, Si-Wei Liu wrote:
>>
> Can you provide the context or link? It shouldn't work like this,
> otherwise it is breaking uABI. E.g. how will a legacy/BE supporting
> kernel/device be backward compatible with older vdpa tool (which has
> knowledge
s/has knowledge/has no knowledge/
> of this endianness implication/assumption from day one)?
>
> -Siwei
[-- Attachment #1.2: Type: text/html, Size: 899 bytes --]
[-- Attachment #2: Type: text/plain, Size: 183 bytes --]
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2022-08-16 8:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220815092638.504528-1-lingshan.zhu@intel.com>
[not found] ` <20220815092638.504528-3-lingshan.zhu@intel.com>
2022-08-15 15:52 ` [PATCH 2/2] vDPA: conditionally read fields in virtio-net dev Michael S. Tsirkin
2022-08-15 23:32 ` Si-Wei Liu
[not found] ` <20e92551-a639-ec13-3d9c-13bb215422e1@intel.com>
2022-08-16 7:58 ` Si-Wei Liu
2022-08-16 8:08 ` Si-Wei Liu [this message]
[not found] ` <22e0236f-b556-c6a8-0043-b39b02928fd6@intel.com>
2022-08-16 23:14 ` Si-Wei Liu
[not found] ` <52a47bc7-bf26-b8f9-257f-7dc5cea66d23@intel.com>
2022-08-17 8:55 ` Michael S. Tsirkin
[not found] ` <a91fa479-d1cc-a2d6-0821-93386069a2c1@intel.com>
2022-08-17 9:39 ` Michael S. Tsirkin
[not found] ` <449c2fb2-3920-7bf9-8c5c-a68456dfea76@intel.com>
2022-08-17 10:37 ` Michael S. Tsirkin
2022-08-18 4:15 ` Jason Wang
2022-08-18 23:20 ` Si-Wei Liu
2022-08-19 0:42 ` Jason Wang
2022-08-19 3:52 ` Michael S. Tsirkin
2022-08-20 8:55 ` Si-Wei Liu
[not found] ` <e06d1f6d-3199-1b75-d369-2e5d69040271@intel.com>
2022-08-23 3:26 ` Jason Wang
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-17 18:50 ` Si-Wei Liu
2022-08-16 2:32 ` Parav Pandit via Virtualization
[not found] ` <4184a943-f1c0-a57b-6411-bdd21e0bc710@intel.com>
2022-08-16 21:02 ` Parav Pandit via Virtualization
2022-08-16 21:09 ` Michael S. Tsirkin
[not found] ` <352e9533-8ab1-cec0-0141-ce0735ee39f5@intel.com>
2022-08-18 4:18 ` Jason Wang
2022-08-18 17:20 ` Parav Pandit via Virtualization
[not found] ` <20220815092638.504528-2-lingshan.zhu@intel.com>
2022-08-15 18:15 ` [PATCH 1/2] vDPA: allow userspace to query features of a vDPA device Si-Wei Liu
[not found] ` <cea494d0-d446-274f-f913-723822a53e6a@intel.com>
2022-08-16 2:07 ` Parav Pandit via Virtualization
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=517a5f0b-e484-abdc-3ddd-7e46d8b7ff7e@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=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).