From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: [PATCH RFC 1/2] Allow recvmsg for qemu char devices Date: Thu, 30 Jul 2009 13:28:57 -0500 Message-ID: <4A71E669.9070801@codemonkey.ws> References: <1248971307-8421-1-git-send-email-cam@cs.ualberta.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org To: Cam Macdonell Return-path: Received: from qw-out-2122.google.com ([74.125.92.25]:9298 "EHLO qw-out-2122.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750967AbZG3S3A (ORCPT ); Thu, 30 Jul 2009 14:29:00 -0400 Received: by qw-out-2122.google.com with SMTP id 8so894215qwh.37 for ; Thu, 30 Jul 2009 11:29:00 -0700 (PDT) In-Reply-To: <1248971307-8421-1-git-send-email-cam@cs.ualberta.ca> Sender: kvm-owner@vger.kernel.org List-ID: 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MWaNH-0005v6-34 for qemu-devel@nongnu.org; Thu, 30 Jul 2009 14:29:07 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MWaNB-0005uu-NM for qemu-devel@nongnu.org; Thu, 30 Jul 2009 14:29:05 -0400 Received: from [199.232.76.173] (port=41965 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MWaNB-0005ur-HT for qemu-devel@nongnu.org; Thu, 30 Jul 2009 14:29:01 -0400 Received: from mail-qy0-f174.google.com ([209.85.221.174]:38594) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MWaNB-0005Ho-7i for qemu-devel@nongnu.org; Thu, 30 Jul 2009 14:29:01 -0400 Received: by qyk4 with SMTP id 4so2078950qyk.4 for ; Thu, 30 Jul 2009 11:29:00 -0700 (PDT) Message-ID: <4A71E669.9070801@codemonkey.ws> Date: Thu, 30 Jul 2009 13:28:57 -0500 From: Anthony Liguori MIME-Version: 1.0 References: <1248971307-8421-1-git-send-email-cam@cs.ualberta.ca> In-Reply-To: <1248971307-8421-1-git-send-email-cam@cs.ualberta.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [PATCH RFC 1/2] Allow recvmsg for qemu char devices List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Cam Macdonell Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org 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