From: Steven Sistare <steven.sistare@oracle.com>
To: virtualization@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Si-Wei Liu <si-wei.liu@oracle.com>,
Eugenio Perez Martin <eperezma@redhat.com>,
Xie Yongji <xieyongji@bytedance.com>,
Stefano Garzarella <sgarzare@redhat.com>
Subject: Re: [PATCH V2 0/3] flush workers on suspend
Date: Tue, 13 Feb 2024 10:10:31 -0500 [thread overview]
Message-ID: <83e12387-e9b6-4a06-a38e-0f9888cd4e88@oracle.com> (raw)
In-Reply-To: <1707758174-142161-1-git-send-email-steven.sistare@oracle.com>
On 2/12/2024 12:16 PM, Steve Sistare wrote:
> Flush to guarantee no workers are running when suspend returns,
> for vdpa, vpa_sim, and vduse. (mlx5 already does so, via the path
> mlx5_vdpa_suspend -> unregister_link_notifier -> flush_workqueue.)
Changes in V2:
- renamed "vduse: suspend" (was vduse: flush workers on suspend)
- call vhost_dev_flush unconditionally in "vhost-vdpa: flush workers on suspend"
- Steve
> Steve Sistare (3):
> vhost-vdpa: flush workers on suspend
> vduse: suspend
> vdpa_sim: flush workers on suspend
>
> drivers/vdpa/vdpa_sim/vdpa_sim.c | 13 +++++++++++++
> drivers/vdpa/vdpa_user/vduse_dev.c | 24 ++++++++++++++++++++++++
> drivers/vhost/vdpa.c | 3 +++
> 3 files changed, 40 insertions(+)
>
prev parent reply other threads:[~2024-02-13 15:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 17:16 [PATCH V2 0/3] flush workers on suspend Steve Sistare
2024-02-12 17:16 ` [PATCH V2 1/3] vhost-vdpa: " Steve Sistare
2024-02-13 15:58 ` Eugenio Perez Martin
2024-02-14 17:48 ` Steven Sistare
2024-02-12 17:16 ` [PATCH V2 2/3] vduse: suspend Steve Sistare
2024-02-12 17:16 ` [PATCH V2 3/3] vdpa_sim: flush workers on suspend Steve Sistare
2024-02-13 16:10 ` Eugenio Perez Martin
2024-02-14 17:50 ` Steven Sistare
2024-02-14 19:39 ` Eugenio Perez Martin
2024-02-14 19:52 ` Steven Sistare
2024-02-15 15:44 ` Eugenio Perez Martin
2024-02-16 15:15 ` Steven Sistare
2024-02-13 15:10 ` Steven Sistare [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=83e12387-e9b6-4a06-a38e-0f9888cd4e88@oracle.com \
--to=steven.sistare@oracle.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=sgarzare@redhat.com \
--cc=si-wei.liu@oracle.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