qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cam Macdonell <cam@cs.ualberta.ca>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Passing fds through a qemu char device
Date: Fri, 22 May 2009 16:32:32 -0600	[thread overview]
Message-ID: <4A172800.8080406@cs.ualberta.ca> (raw)


Hi,

I'm trying to pass eventfds between qemu processes and I'm trying to use 
a qemu char device to do this.  AFAICT with a qemu_chr_device the 
polling handler only has support to call read()/write(), not 
send/recvmsg() which are necessary to send and receive fds with 
SCM_RIGHTS through the socket.  Is this true or is there support in Qemu 
for recvmsg() that I'm not seeing?

If not, some options I can see are to add qemu support for 
qemu_chr_recvmsg() to call on the char device.  Or I can simply manage 
the socket outside of qemu_chr_device, but the polling is helpful for 
notifications and I'd prefer to leverage qemu's existing support for that.

Thanks,
Cam

             reply	other threads:[~2009-05-22 22:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-22 22:32 Cam Macdonell [this message]
2009-05-23  2:10 ` [Qemu-devel] Passing fds through a qemu char device Anthony Liguori
2009-05-26 17:47   ` Cam Macdonell

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=4A172800.8080406@cs.ualberta.ca \
    --to=cam@cs.ualberta.ca \
    --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 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).