Let userspace create vhost workers and bind them to vhost-blk
virtqueues with the mainstream ioctls from c1ecd8e95007 ("vhost: allow
userspace to create workers"), the same way d74b55e65502 ("vhost_scsi:
add support for worker ioctls") does it for vhost-scsi.

VHOST_NEW_WORKER needs the device in vhost_task mode, so userspace has
to issue VHOST_SET_FORK_FROM_OWNER with VHOST_FORK_OWNER_TASK before
VHOST_SET_OWNER: our fork_from_owner_default is kthread.

https://virtuozzo.atlassian.net/browse/VSTOR-107537
Feature: vhost-blk: in-kernel accelerator for virtio-blk guests

Suggested-by: Pavel Tikhomirov <[email protected]>
Signed-off-by: Alexander Ivanov <[email protected]>
Reviewed-by: Andrey Zhadchenko <[email protected]>
---
 drivers/vhost/blk.c | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/drivers/vhost/blk.c b/drivers/vhost/blk.c
index b7d3755200ba..1d26560dd4f0 100644
--- a/drivers/vhost/blk.c
+++ b/drivers/vhost/blk.c
@@ -978,6 +978,14 @@ static long vhost_blk_ioctl(struct file *f, unsigned int 
ioctl,
                return vhost_blk_set_features(blk, features);
        case VHOST_RESET_OWNER:
                return vhost_blk_reset_owner(blk);
+       case VHOST_NEW_WORKER:
+       case VHOST_FREE_WORKER:
+       case VHOST_ATTACH_VRING_WORKER:
+       case VHOST_GET_VRING_WORKER:
+               mutex_lock(&blk->dev.mutex);
+               ret = vhost_worker_ioctl(&blk->dev, ioctl, argp);
+               mutex_unlock(&blk->dev.mutex);
+               return ret;
        default:
                mutex_lock(&blk->dev.mutex);
                ret = vhost_dev_ioctl(&blk->dev, ioctl, argp);
-- 
2.53.0

_______________________________________________
Devel mailing list
[email protected]
https://lists.openvz.org/mailman/listinfo/devel

Reply via email to