From: Cindy Lu <lulu@redhat.com>
To: lulu@redhat.com, jasowang@redhat.com, mst@redhat.com,
michael.christie@oracle.com, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: [PATCH v2 1/7] vhost: Add a new modparam to allow userspace select vhost_task
Date: Fri, 4 Oct 2024 09:58:15 +0800 [thread overview]
Message-ID: <20241004015937.2286459-2-lulu@redhat.com> (raw)
In-Reply-To: <20241004015937.2286459-1-lulu@redhat.com>
The vhost is now using vhost_task and working as a child of the owner thread.
While this makes sense from containerization POV, some old userspace is
confused, as previously vhost not and so was allowed to steal cpu resources
from outside the container. So we add the kthread API support back
Add a new module parameter to allow userspace to select behaviour
between using kthread and task
Signed-off-by: Cindy Lu <lulu@redhat.com>
---
drivers/vhost/vhost.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c
index 9ac25d08f473..a4a0bc34f59b 100644
--- a/drivers/vhost/vhost.c
+++ b/drivers/vhost/vhost.c
@@ -41,6 +41,10 @@ static int max_iotlb_entries = 2048;
module_param(max_iotlb_entries, int, 0444);
MODULE_PARM_DESC(max_iotlb_entries,
"Maximum number of iotlb entries. (default: 2048)");
+bool enforce_inherit_owner = true;
+module_param(enforce_inherit_owner, bool, 0444);
+MODULE_PARM_DESC(enforce_inherit_owner,
+ "enforce vhost use vhost_task(default: Y)");
enum {
VHOST_MEMORY_F_LOG = 0x1,
--
2.45.0
next prev parent reply other threads:[~2024-10-04 1:59 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 1:58 [PATCH v2 0/7] vhost: Add support of kthread API Cindy Lu
2024-10-04 1:58 ` Cindy Lu [this message]
2024-10-05 15:42 ` [PATCH v2 1/7] vhost: Add a new modparam to allow userspace select vhost_task kernel test robot
2024-10-07 13:31 ` Stefano Garzarella
2024-10-09 7:28 ` Jason Wang
2024-10-09 7:57 ` Stefano Garzarella
2024-10-09 8:20 ` Jason Wang
2024-10-14 6:47 ` Cindy Lu
2024-10-14 6:46 ` Cindy Lu
2024-10-04 1:58 ` [PATCH v2 2/7] vhost: Add kthread support in function vhost_worker_queue() Cindy Lu
2024-10-04 1:58 ` [PATCH v2 3/7] vhost: Add kthread support in function vhost_workers_free() Cindy Lu
2024-10-07 13:32 ` Stefano Garzarella
2024-10-15 5:54 ` Cindy Lu
2024-10-14 21:05 ` Mike Christie
2024-10-15 6:05 ` Cindy Lu
2024-10-15 6:52 ` Stefano Garzarella
2024-10-15 7:19 ` Cindy Lu
2024-10-04 1:58 ` [PATCH v2 4/7] vhost: Add the vhost_worker to support kthread Cindy Lu
2024-10-14 22:56 ` Mike Christie
2024-10-15 9:03 ` Cindy Lu
2024-10-04 1:58 ` [PATCH v2 5/7] vhost: Add the cgroup related function Cindy Lu
2024-10-04 1:58 ` [PATCH v2 6/7] vhost: Add kthread support in function vhost_worker_create Cindy Lu
2024-10-14 21:02 ` Mike Christie
2024-10-15 6:30 ` Cindy Lu
2024-10-04 1:58 ` [PATCH v2 7/7] vhost: Add new UAPI to support change to task mode Cindy Lu
2024-10-07 13:37 ` Stefano Garzarella
2024-10-14 20:56 ` Mike Christie
2024-10-15 2:35 ` Cindy Lu
2024-10-15 10:19 ` Michael S. Tsirkin
2024-10-17 6:53 ` 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=20241004015937.2286459-2-lulu@redhat.com \
--to=lulu@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.christie@oracle.com \
--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®