From: "Michael S. Tsirkin" <mst@redhat.com>
To: Dragos Tatulea <dtatulea@nvidia.com>
Cc: Jason Wang <jasowang@redhat.com>,
Eugenio Perez Martin <eperezma@redhat.com>,
Si-Wei Liu <si-wei.liu@oracle.com>,
virtualization@lists.linux-foundation.org,
Gal Pressman <gal@nvidia.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Parav Pandit <parav@nvidia.com>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Subject: Re: [PATCH 0/2] vdpa: Block vq property change in DRIVER_OK
Date: Mon, 25 Dec 2023 09:40:17 -0500 [thread overview]
Message-ID: <20231225093850-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20231225134210.151540-1-dtatulea@nvidia.com>
On Mon, Dec 25, 2023 at 03:42:08PM +0200, Dragos Tatulea wrote:
> This series prevents the change of virtqueue address or state when a
> device is in DRIVER_OK and not suspended. The virtio spec doesn't
> allow changing virtqueue addresses and state in DRIVER_OK, but some devices
> do support this operation when the device is suspended. The series
> leaves the door open for these devices.
>
> The series was suggested while discussing the addition of resumable
> virtuque support in the mlx5_vdpa driver [0].
I am confused. Isn't this also included in
vdpa/mlx5: Add support for resumable vqs
do you now want this merged separately?
> [0] https://lore.kernel.org/virtualization/20231219180858.120898-1-dtatulea@nvidia.com/T/#m044ddf540d98a6b025f81bffa058ca647a3d013e
>
> Dragos Tatulea (2):
> vdpa: Track device suspended state
> vdpa: Block vq property changes in DRIVER_OK
>
> drivers/vhost/vdpa.c | 23 +++++++++++++++++++++--
> 1 file changed, 21 insertions(+), 2 deletions(-)
>
> --
> 2.43.0
next prev parent reply other threads:[~2023-12-25 14:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-25 13:42 [PATCH 0/2] vdpa: Block vq property change in DRIVER_OK Dragos Tatulea
2023-12-25 13:42 ` [PATCH 1/2] vdpa: Track device suspended state Dragos Tatulea
2023-12-25 13:42 ` [PATCH 2/2] vdpa: Block vq property changes in DRIVER_OK Dragos Tatulea
2023-12-25 14:40 ` Michael S. Tsirkin [this message]
2023-12-25 15:09 ` [PATCH 0/2] vdpa: Block vq property change " Dragos Tatulea
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=20231225093850-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=dtatulea@nvidia.com \
--cc=eperezma@redhat.com \
--cc=gal@nvidia.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=parav@nvidia.com \
--cc=si-wei.liu@oracle.com \
--cc=virtualization@lists.linux-foundation.org \
--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