On Fri, Oct 22, 2021 at 12:19:11AM -0500, Mike Christie wrote: > diff --git a/include/uapi/linux/vhost.h b/include/uapi/linux/vhost.h > index c998860d7bbc..e5c0669430e5 100644 > --- a/include/uapi/linux/vhost.h > +++ b/include/uapi/linux/vhost.h > @@ -70,6 +70,17 @@ > #define VHOST_VRING_BIG_ENDIAN 1 > #define VHOST_SET_VRING_ENDIAN _IOW(VHOST_VIRTIO, 0x13, struct vhost_vring_state) > #define VHOST_GET_VRING_ENDIAN _IOW(VHOST_VIRTIO, 0x14, struct vhost_vring_state) > +/* By default, a device gets one vhost_worker created during VHOST_SET_OWNER > + * that its virtqueues share. This allows userspace to create a vhost_worker > + * and map a virtqueue to it or map a virtqueue to an existing worker. > + * > + * If pid > 0 and it matches an existing vhost_worker thread it will be bound > + * to the vq. If pid is VHOST_VRING_NEW_WORKER, then a new worker will be > + * created and bound to the vq. > + * > + * This must be called after VHOST_SET_OWNER and before the vq is active. > + */ > +#define VHOST_SET_VRING_WORKER _IOWR(VHOST_VIRTIO, 0x15, struct vhost_vring_worker) Please clarify whether or not multiple devices can attach vqs to the same worker. Stefan
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/virtualization
