mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Cindy Lu <lulu@redhat.com>
To: lulu@redhat.com, jasowang@redhat.com, mst@redhat.com,
	linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org
Subject: [RFC 4/7] vhost: Add the vhost_worker to support kthread
Date: Mon, 19 Aug 2024 17:27:30 +0800	[thread overview]
Message-ID: <20240819092851.441670-5-lulu@redhat.com> (raw)
In-Reply-To: <20240819092851.441670-1-lulu@redhat.com>

Add back the previously removed vhost_worker function to support the kthread
and rename it vhost_run_work_kthread_list.

Signed-off-by: Cindy Lu <lulu@redhat.com>
---
 drivers/vhost/vhost.c | 38 ++++++++++++++++++++++++++++++++++++++
 1 file changed, 38 insertions(+)

diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c
index 77071def355c..593f9521f51d 100644
--- a/drivers/vhost/vhost.c
+++ b/drivers/vhost/vhost.c
@@ -417,6 +417,44 @@ static void vhost_vq_reset(struct vhost_dev *dev,
 	__vhost_vq_meta_reset(vq);
 }
 
+static int vhost_run_work_kthread_list(void *data)
+{
+	struct vhost_worker *worker = data;
+	struct vhost_work *work, *work_next;
+	struct vhost_dev *dev = worker->dev;
+	struct llist_node *node;
+
+	kthread_use_mm(dev->mm);
+
+	for (;;) {
+		/* mb paired w/ kthread_stop */
+		set_current_state(TASK_INTERRUPTIBLE);
+
+		if (kthread_should_stop()) {
+			__set_current_state(TASK_RUNNING);
+			break;
+		}
+		node = llist_del_all(&worker->work_list);
+		if (!node)
+			schedule();
+
+		node = llist_reverse_order(node);
+		/* make sure flag is seen after deletion */
+		smp_wmb();
+		llist_for_each_entry_safe(work, work_next, node, node) {
+			clear_bit(VHOST_WORK_QUEUED, &work->flags);
+			__set_current_state(TASK_RUNNING);
+			kcov_remote_start_common(worker->kcov_handle);
+			work->fn(work);
+			kcov_remote_stop();
+			cond_resched();
+		}
+	}
+	kthread_unuse_mm(dev->mm);
+
+	return 0;
+}
+
 static bool vhost_run_work_list(void *data)
 {
 	struct vhost_worker *worker = data;
-- 
2.45.0


  parent reply	other threads:[~2024-08-19  9:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-19  9:27 [RFC 0/7] vhost: Add support of kthread API Cindy Lu
2024-08-19  9:27 ` [RFC 1/7] vhost: Add a new module_param for enable kthread Cindy Lu
2024-08-19  9:27 ` [RFC 2/7] vhost: Add kthread support in function vhost_worker_queue() Cindy Lu
2024-08-27  2:36   ` Jason Wang
2024-08-28  9:32     ` Cindy Lu
2024-08-19  9:27 ` [RFC 3/7] vhost: Add kthread support in function vhost_workers_free() Cindy Lu
2024-08-19  9:27 ` Cindy Lu [this message]
2024-08-19  9:27 ` [RFC 5/7] vhost: Add the cgroup related function Cindy Lu
2024-08-19  9:27 ` [RFC 6/7] vhost: Add kthread support in function vhost_worker_create Cindy Lu
2024-08-19  9:27 ` [RFC 7/7] vhost: Add new UAPI to support changing Kthread mode Cindy Lu
2024-08-21  5:06   ` Christoph Hellwig
2024-08-25 13:51     ` Cindy Lu
2024-08-26  6:21     ` Jason Wang
2024-08-26  6:26       ` Christoph Hellwig
2024-08-27  2:09         ` Jason Wang
2024-08-27  2:30           ` Jason Wang
2024-08-27  2:32   ` Jason Wang
2024-08-28  9:46     ` Cindy Lu
2024-08-27  2:36   ` Jason Wang
2024-08-27  2:35 ` [RFC 0/7] vhost: Add support of kthread API Jason Wang
2024-08-28  9:47   ` Cindy Lu

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=20240819092851.441670-5-lulu@redhat.com \
    --to=lulu@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=virtualization@lists.linux-foundation.org \
    /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®