[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACGkMEvHU0VnOEZbVnEr1SvmOF5PhMtKk=M2o7Wwq-DUO9p7Uw@mail.gmail.com>
Date: Wed, 4 Sep 2024 11:38:30 +0800
From: Jason Wang <jasowang@...hat.com>
To: Carlos Bilbao <carlos.bilbao.osdev@...il.com>
Cc: dtatulea@...dia.com, mst@...hat.com, shannon.nelson@....com,
sashal@...nel.org, alvaro.karsz@...id-run.com, christophe.jaillet@...adoo.fr,
steven.sistare@...cle.com, bilbao@...edu, xuanzhuo@...ux.alibaba.com,
johnah.palmer@...cle.com, eperezma@...hat.com, cratiu@...dia.com,
virtualization@...ts.linux.dev, linux-kernel@...r.kernel.org,
Carlos Bilbao <cbilbao@...italocean.com>
Subject: Re: [PATCH v2 2/2] vdpa: Remove ioctl VHOST_VDPA_SET_CONFIG per spec compliance
On Wed, Sep 4, 2024 at 1:15 AM Carlos Bilbao
<carlos.bilbao.osdev@...il.com> wrote:
>
> From: Carlos Bilbao <cbilbao@...italocean.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@...italocean.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.
And for eni, it is a legacy only device, so we should not move the
set_config there.
For the rest, we need the acks for those maintainers.
Thanks
Powered by blists - more mailing lists