From: Steve 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>,
Steve Sistare <steven.sistare@oracle.com>
Subject: [PATCH V3 0/3] flush workers on suspend
Date: Mon, 20 May 2024 08:20:59 -0700 [thread overview]
Message-ID: <1716218462-84587-1-git-send-email-steven.sistare@oracle.com> (raw)
Flush to guarantee no workers are running when suspend returns,
for vdpa, vdpa_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"
Changes in v3:
- rewrote vdpa_sim patch
Steve Sistare (3):
vhost-vdpa: flush workers on suspend
vduse: suspend
vdpa_sim: flush workers on suspend
drivers/vdpa/vdpa_sim/vdpa_sim.c | 16 ++++++++++++++--
drivers/vdpa/vdpa_sim/vdpa_sim.h | 1 +
drivers/vdpa/vdpa_user/vduse_dev.c | 24 ++++++++++++++++++++++++
drivers/vhost/vdpa.c | 3 +++
4 files changed, 42 insertions(+), 2 deletions(-)
--
2.39.3
next reply other threads:[~2024-05-20 15:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-20 15:20 Steve Sistare [this message]
2024-05-20 15:21 ` [PATCH V3 1/3] vhost-vdpa: " Steve Sistare
2024-05-21 2:28 ` Jason Wang
2024-05-21 13:38 ` Steven Sistare
2024-05-22 3:41 ` Jason Wang
2024-05-20 15:21 ` [PATCH V3 2/3] vduse: suspend Steve Sistare
2024-05-21 2:30 ` Jason Wang
2024-05-21 13:38 ` Steven Sistare
2024-05-22 3:40 ` Jason Wang
2024-05-20 15:21 ` [PATCH V3 3/3] vdpa_sim: flush workers on suspend Steve Sistare
2024-05-21 2:32 ` Jason Wang
2024-05-21 13:39 ` Steven Sistare
2024-05-22 3:39 ` Jason Wang
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=1716218462-84587-1-git-send-email-steven.sistare@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
all inboxes | Powered by JetHome®