From: Carlos Bilbao <cbilbao@digitalocean.com>
To: Dragos Tatulea <dtatulea@nvidia.com>,
Jason Wang <jasowang@redhat.com>,
Carlos Bilbao <carlos.bilbao.osdev@gmail.com>
Cc: mst@redhat.com, shannon.nelson@amd.com, sashal@kernel.org,
alvaro.karsz@solid-run.com, christophe.jaillet@wanadoo.fr,
steven.sistare@oracle.com, bilbao@vt.edu,
xuanzhuo@linux.alibaba.com, johnah.palmer@oracle.com,
eperezma@redhat.com, cratiu@nvidia.com,
virtualization@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] vdpa: Remove ioctl VHOST_VDPA_SET_CONFIG per spec compliance
Date: Wed, 4 Sep 2024 09:17:33 -0500 [thread overview]
Message-ID: <c2d0df0d-85ae-4605-ac37-71794105f3cd@digitalocean.com> (raw)
In-Reply-To: <faafc28a-23a9-4dff-8223-1c72acb42443@nvidia.com>
Hello,
On 9/4/24 12:58 AM, Dragos Tatulea wrote:
>
> On 04.09.24 05:38, Jason Wang wrote:
>> On Wed, Sep 4, 2024 at 1:15 AM Carlos Bilbao
>> <carlos.bilbao.osdev@gmail.com> wrote:
>>> From: Carlos Bilbao <cbilbao@digitalocean.com>
>>>
>>> Remove invalid ioctl VHOST_VDPA_SET_CONFIG and all its implementations
>>> with vdpa_config_ops->set_config(). This is needed per virtio spec
>>> requirements; virtio-spec v3.1 Sec 5.1.4 states that "All of the device
>>> configuration fields are read-only for the driver."
>>>
>>> Signed-off-by: Carlos Bilbao <cbilbao@digitalocean.com>
>> Note that only the config space of the modern device is read only. So
>> it should be fine to remove vp_vdpa which only works for modern
>> devices.
> Just out of curiosity: how will this work for devices that are not
> v1.3 compliant but are v1.2 compliant? Or is this true of all devices
> except eni?
>
> Thanks,
> Dragos
>> And for eni, it is a legacy only device, so we should not move the
>> set_config there.
Understood. I'll keep the ENI as is for v3 and will reach out to the maintainers.
>>
>> For the rest, we need the acks for those maintainers.
Thanks, Carlos
>>
>> Thanks
>>
prev parent reply other threads:[~2024-09-04 14:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 17:15 [PATCH v2 0/2] Properly initialize speed/duplex and remove vDPA config updates Carlos Bilbao
2024-09-03 17:15 ` [PATCH v2 1/2] vdpa/mlx5: Set speed and duplex of vDPA devices to UNKNOWN Carlos Bilbao
2024-09-03 17:37 ` Nelson, Shannon
2024-09-04 14:14 ` Carlos Bilbao
2024-09-03 17:15 ` [PATCH v2 2/2] vdpa: Remove ioctl VHOST_VDPA_SET_CONFIG per spec compliance Carlos Bilbao
2024-09-04 3:38 ` Jason Wang
2024-09-04 5:58 ` Dragos Tatulea
2024-09-04 6:34 ` Jason Wang
2024-09-04 17:48 ` Dragos Tatulea
2024-09-05 2:23 ` Jason Wang
2024-09-04 14:17 ` Carlos Bilbao [this message]
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=c2d0df0d-85ae-4605-ac37-71794105f3cd@digitalocean.com \
--to=cbilbao@digitalocean.com \
--cc=alvaro.karsz@solid-run.com \
--cc=bilbao@vt.edu \
--cc=carlos.bilbao.osdev@gmail.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=cratiu@nvidia.com \
--cc=dtatulea@nvidia.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=johnah.palmer@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=sashal@kernel.org \
--cc=shannon.nelson@amd.com \
--cc=steven.sistare@oracle.com \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.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
all inboxes | Powered by JetHome®