From: Mike Christie <michael.christie@oracle.com>
To: Jason Wang <jasowang@redhat.com>,
sgarzare@redhat.com, stefanha@redhat.com,
linux-scsi@vger.kernel.org, target-devel@vger.kernel.org,
mst@redhat.com, pbonzini@redhat.com,
virtualization@lists.linux-foundation.org
Subject: Re: [RFC PATCH 5/8] vhost: allow userspace to bind vqs to CPUs
Date: Fri, 4 Dec 2020 10:32:56 -0600 [thread overview]
Message-ID: <30746f1c-ed8c-d2ae-9513-54fca8f52739@oracle.com> (raw)
In-Reply-To: <4546ef72-da7c-df9e-53be-c937a5437436@redhat.com>
On 12/4/20 2:09 AM, Jason Wang wrote:
>
> On 2020/12/4 下午3:56, Mike Christie wrote:
>> +static long vhost_vring_set_cpu(struct vhost_dev *d, struct
>> vhost_virtqueue *vq,
>> + void __user *argp)
>> +{
>> + struct vhost_vring_state s;
>> + int ret = 0;
>> +
>> + if (vq->private_data)
>> + return -EBUSY;
>> +
>> + if (copy_from_user(&s, argp, sizeof s))
>> + return -EFAULT;
>> +
>> + if (s.num == -1) {
>> + vq->cpu = s.num;
>> + return 0;
>> + }
>> +
>> + if (s.num >= nr_cpu_ids)
>> + return -EINVAL;
>> +
>> + if (!d->ops || !d->ops->get_workqueue)
>> + return -EINVAL;
>> +
>> + if (!d->wq)
>> + d->wq = d->ops->get_workqueue();
>> + if (!d->wq)
>> + return -EINVAL;
>> +
>> + vq->cpu = s.num;
>> + return ret;
>> +}
>
>
> So one question here. Who is in charge of doing this set_cpu? Note
> that sched_setaffinity(2) requires CAP_SYS_NICE to work, so I wonder
> whether or not it's legal for unprivileged Qemu to do this.
I was having qemu do it when it's setting up the vqs since it had the
info there already.
Is it normally the tool that makes calls into qemu that does the
operations that require CAP_SYS_NICE? If so, then I see the interface
needs to be changed.
next prev parent reply other threads:[~2020-12-04 16:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 7:56 [RFC PATCH 0/8] vhost: allow userspace to control vq cpu affinity Mike Christie
2020-12-04 7:56 ` [RFC PATCH 1/8] vhost: remove work arg from vhost_work_flush Mike Christie
2020-12-04 7:56 ` [RFC PATCH 2/8] vhost-scsi: remove extra flushes Mike Christie
2020-12-04 7:56 ` [RFC PATCH 3/8] vhost poll: fix coding style Mike Christie
2020-12-04 7:56 ` [RFC PATCH 4/8] vhost: move msg_handler to new ops struct Mike Christie
2020-12-04 7:56 ` [RFC PATCH 5/8] vhost: allow userspace to bind vqs to CPUs Mike Christie
2020-12-04 8:09 ` Jason Wang
2020-12-04 16:32 ` Mike Christie [this message]
2020-12-07 4:27 ` Jason Wang
2020-12-07 18:31 ` Mike Christie
2020-12-08 2:30 ` Jason Wang
2020-12-04 7:56 ` [RFC PATCH 6/8] vhost-scsi: make SCSI cmd completion per vq Mike Christie
2020-12-04 7:56 ` [RFC PATCH 7/8] vhost, vhost-scsi: flush IO vqs then send TMF rsp Mike Christie
2020-12-04 7:56 ` [RFC PATCH 8/8] vhost-scsi: hook vhost-scsi into vring set cpu support Mike Christie
2020-12-04 16:06 ` [RFC PATCH 0/8] vhost: allow userspace to control vq cpu affinity Stefano Garzarella
2020-12-04 17:10 ` Mike Christie
2020-12-04 17:33 ` Mike Christie
2020-12-09 15:58 ` Stefano Garzarella
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=30746f1c-ed8c-d2ae-9513-54fca8f52739@oracle.com \
--to=michael.christie@oracle.com \
--cc=jasowang@redhat.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=target-devel@vger.kernel.org \
--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