From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: mst@redhat.com, marcandre.lureau@gmail.com, vkaplans@redhat.com,
jasowang@redhat.com, wexu@redhat.com,
yuanhan.liu@linux.intel.com, qemu-devel@nongnu.org,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [Qemu-devel] [RFC v2 3/4] vhost-user: add slave-req-fd support
Date: Wed, 19 Apr 2017 09:23:30 +0200 [thread overview]
Message-ID: <edb96a11-49b8-5483-0160-9855989822b6@redhat.com> (raw)
In-Reply-To: <20170417032958.GA16703@pxdev.xzpeter.org>
On 04/17/2017 05:29 AM, Peter Xu wrote:
> On Fri, Apr 14, 2017 at 07:40:55PM +0200, Maxime Coquelin wrote:
>
> [...]
>
>> @@ -486,6 +500,18 @@ Message types
>> If VHOST_USER_PROTOCOL_F_REPLY_ACK is negotiated, slave must respond
>> with zero in case the specified MTU is valid, or non-zero otherwise.
>>
>> + * VHOST_USER_SET_SLAVE_REQ_FD
>> +
>> + Id: 21
>> + Equivalent ioctl: N/A
>> + Master payload: N/A
>> +
>> + Set the socket file descriptor for slave initiated requests. It is passed
>> + in the ancillary data.
>> + This request should be sent only when VHOST_USER_F_PROTOCOL_FEATURES
>> + has been negotiated, and protocol feature bit VHOST_USER_PROTOCOL_F_SLAVE_REQ
>> + bit is present in VHOST_USER_GET_PROTOCOL_FEATURES.
>
> Here, do we need to mention REPLY_ACK as well? Like:
>
> If VHOST_USER_PROTOCOL_F_REPLY_ACK is negotiated, slave must
> respond with zero in case the slave request channel is setup
> correctly, or non-zero otherwise.
>
> Since I see the other two users are mentioning it.
Sure, it won't hurt. I'll add this in next revision.
> [...]
>
>> +static int vhost_setup_slave_channel(struct vhost_dev *dev)
>> +{
>> + VhostUserMsg msg = {
>> + .request = VHOST_USER_SET_SLAVE_REQ_FD,
>> + .flags = VHOST_USER_VERSION,
>> + };
>> + struct vhost_user *u = dev->opaque;
>> + int sv[2];
>> + bool reply_supported = virtio_has_feature(dev->protocol_features,
>> + VHOST_USER_PROTOCOL_F_REPLY_ACK);
>> +
>> + if (!virtio_has_feature(dev->protocol_features,
>> + VHOST_USER_PROTOCOL_F_SLAVE_REQ)) {
>> + return 0;
>> + }
>> +
>> + if (socketpair(PF_UNIX, SOCK_STREAM, 0, sv) == -1) {
>> + error_report("socketpair() failed");
>> + return -1;
>> + }
>> +
>> + u->slave_fd = sv[0];
>> + qemu_set_fd_handler(u->slave_fd, slave_read, NULL, dev);
>> +
>> + if (reply_supported) {
>> + msg.flags |= VHOST_USER_NEED_REPLY_MASK;
>> + }
>> +
>> + vhost_user_write(dev, &msg, &sv[1], 1);
>
> Do we need to close(sv[1]) afterward?
Right, thanks. It will be leaked otherwise.
>> +
>> + if (reply_supported) {
>> + return process_message_reply(dev, msg.request);
>
> Here do we need to cleanup u->slave_fd if backend replied something
> wrong? Or I guess it might be leaked.
That make sense, I'll fix this.
Thanks!
Maxime
> Thanks,
>
>> + }
>> +
>> + return 0;
>> +}
>> +
>
next prev parent reply other threads:[~2017-04-19 7:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-14 17:40 [Qemu-devel] [RFC v2 0/4] vhost-user: Specify and implement device IOTLB support Maxime Coquelin
2017-04-14 17:40 ` [Qemu-devel] [RFC v2 1/4] vhost: propagate errors in vhost_device_iotlb_miss() Maxime Coquelin
2017-04-14 17:40 ` [Qemu-devel] [RFC v2 2/4] vhost-user: add vhost_user to hold the chr Maxime Coquelin
2017-04-14 17:40 ` [Qemu-devel] [RFC v2 3/4] vhost-user: add slave-req-fd support Maxime Coquelin
2017-04-17 3:29 ` Peter Xu
2017-04-19 7:23 ` Maxime Coquelin [this message]
2017-04-14 17:40 ` [Qemu-devel] [RFC v2 4/4] spec/vhost-user spec: Add IOMMU support Maxime Coquelin
2017-04-14 17:47 ` Maxime Coquelin
2017-04-17 3:50 ` Peter Xu
2017-04-19 7:34 ` Maxime Coquelin
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=edb96a11-49b8-5483-0160-9855989822b6@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=jasowang@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vkaplans@redhat.com \
--cc=wexu@redhat.com \
--cc=yuanhan.liu@linux.intel.com \
/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;
as well as URLs for NNTP newsgroup(s).