qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Cam Macdonell <cam@cs.ualberta.ca>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: [PATCH RFC 1/2] Allow recvmsg for qemu char devices
Date: Thu, 30 Jul 2009 13:28:57 -0500	[thread overview]
Message-ID: <4A71E669.9070801@codemonkey.ws> (raw)
In-Reply-To: <1248971307-8421-1-git-send-email-cam@cs.ualberta.ca>

Cam Macdonell wrote:
> This patch allows switching from the standard recv to recvmsg for a qemu char
> device.  Switching allows file descriptors to be passed with SCM_RIGHTS to a
> qemu process.  Instead of receiving a buffer of data the recvmsg call back is
> passed a 'struct msghdr'.
>
> The patch also adds a function to add an eventfd as qemu char device.  Perhaps
> this should be a separate patch.
>
> This is not an elegant solution to supporting recvmsg so suggestions are
> especially welcome.
>   

Use the sendfd/closefd commands that Mark introduced.

Regards,

Anthony Liguori

      reply	other threads:[~2009-07-30 18:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-30 16:28 [Qemu-devel] [PATCH RFC 1/2] Allow recvmsg for qemu char devices Cam Macdonell
2009-07-30 18:28 ` Anthony Liguori [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=4A71E669.9070801@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=cam@cs.ualberta.ca \
    --cc=kvm@vger.kernel.org \
    --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).