All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Felipe Franciosi <felipe@nutanix.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Marc-André Lureau" <marcandre.lureau@gmail.com>
Subject: Re: [Qemu-devel] Question on unixsocket-based chardevs and vhost-user
Date: Thu, 29 Sep 2016 09:09:40 +0100	[thread overview]
Message-ID: <20160929080940.GC5312@redhat.com> (raw)
In-Reply-To: <F19FC4E6-2FD7-4C23-8128-D34CFEC81D1D@nutanix.com>

On Wed, Sep 28, 2016 at 05:30:24PM +0000, Felipe Franciosi wrote:
> 
> > On 28 Sep 2016, at 18:03, Felipe Franciosi <felipe@nutanix.com> wrote:
> > 
> > Hi Paolo,
> > 
> >> On 28 Sep 2016, at 17:59, Paolo Bonzini <pbonzini@redhat.com> wrote:
> >> 
> >> On 28/09/2016 18:56, Felipe Franciosi wrote:
> >>> Hi Daniel/Paolo,
> >>> 
> >>> 
> >>> 
> >>> I have a question regarding this commit:
> >>> 
> >>> -------------8<-------------
> >>> Author:     Daniel P. Berrange <berrange@redhat.com>
> >>> AuthorDate: Tue Jan 19 11:14:29 2016 +0000
> >>> Commit:     Paolo Bonzini <pbonzini@redhat.com>
> >>> CommitDate: Tue Jan 26 15:58:11 2016 +0100
> >>> -------------8<-------------
> >>> 
> >>> One of the hunks replace unix_send_msgfds() with io_channel_send_full():
> >>> 
> >>> According to the code (qemu-char.c:968), io_channel_send_full() is just
> >>> ignoring the s->write_msgfds parameter.
> >> 
> >> Hmm, no, it's passing it down:
> >> 
> >>       ret = qio_channel_writev_full(
> >>           ioc, &iov, 1,
> >>           fds, nfds, NULL);
> >> 
> >> See the implementation of qio_channel_socket_writev in io/channel-socket.c.
> > 
> > Ah, so my socket has been plumbed with qio_channel_file_writev() for some reason. That's definitely ignoring the fds. I'll look into why it's not qio_channel_socket_writev().
> 
> Got to the bottom of it. So I was basing myself on this example:
> http://git.qemu.org/?p=qemu.git;a=blob;f=qemu-char.c;h=fb456cec345b10b12a051d44067cce29cb1bdf44;hb=HEAD#l1117
> 
> It says "open a character device to a unix fd" and then uses the QIO File API. Worth checking if that's correct.

That comment is misleading - when it says "unix fd" is really means a POSIX
file descriptor, as distinct from a Win32 file descriptor. It has nothing
todo with UNIX sockets.


Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://entangle-photo.org       -o-    http://search.cpan.org/~danberr/ :|

      reply	other threads:[~2016-09-29  8:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-28 16:56 [Qemu-devel] Question on unixsocket-based chardevs and vhost-user Felipe Franciosi
2016-09-28 16:59 ` Paolo Bonzini
2016-09-28 17:03   ` Felipe Franciosi
2016-09-28 17:30     ` Felipe Franciosi
2016-09-29  8:09       ` Daniel P. Berrange [this message]

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=20160929080940.GC5312@redhat.com \
    --to=berrange@redhat.com \
    --cc=felipe@nutanix.com \
    --cc=marcandre.lureau@gmail.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.