From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NSbrw-0008Q2-LO
	for qemu-devel@nongnu.org; Wed, 06 Jan 2010 14:48:36 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NSbrs-0008KW-GU
	for qemu-devel@nongnu.org; Wed, 06 Jan 2010 14:48:36 -0500
Received: from [199.232.76.173] (port=34645 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NSbrs-0008K6-74
	for qemu-devel@nongnu.org; Wed, 06 Jan 2010 14:48:32 -0500
Received: from mx1.redhat.com ([209.132.183.28]:47667)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <pbonzini@redhat.com>) id 1NSbrr-0006Kh-Jn
	for qemu-devel@nongnu.org; Wed, 06 Jan 2010 14:48:31 -0500
Message-ID: <4B44E900.1000305@redhat.com>
Date: Wed, 06 Jan 2010 20:48:16 +0100
From: Paolo Bonzini <pbonzini@redhat.com>
MIME-Version: 1.0
References: <4B4333DF.8090303@linux.vnet.ibm.com>	<20100105213350.GC30921@redhat.com>	<4B43DA17.8080001@codemonkey.ws>
	<20100106104903.GA2248@redhat.com>	<4B4483CA.2030101@linux.vnet.ibm.com>	<20100106132043.GC2248@redhat.com>	<4B449162.9040107@linux.vnet.ibm.com>	<20100106135527.GE2248@redhat.com>
	<4B44A7E6.5030300@linux.vnet.ibm.com>
In-Reply-To: <4B44A7E6.5030300@linux.vnet.ibm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] Re: Planning for 0.13
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Anthony Liguori <aliguori@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>

On 01/06/2010 04:10 PM, Anthony Liguori wrote:
> We have ones that require read/write, ones that require send/recv, and
> ones that require vhost interaction.  Really, the first two are the same
> but the distinction is necessary for Windows.

Not necessarily, you can open sockets on Windows so that they support 
read/write.  Just create it with

   fh = WSASocket (domain, type, protocol, NULL, 0, 0);

instead of socket.  Since Windows already has enough problems passing 
file descriptors to processes, imposing the above on an external 
management interface is not a huge chore.

Paolo