From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MVnyL-0005m3-7R for qemu-devel@nongnu.org; Tue, 28 Jul 2009 10:48:09 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MVnyI-0005lH-Ar for qemu-devel@nongnu.org; Tue, 28 Jul 2009 10:48:07 -0400 Received: from [199.232.76.173] (port=34882 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MVnyI-0005lD-70 for qemu-devel@nongnu.org; Tue, 28 Jul 2009 10:48:06 -0400 Received: from mail-px0-f201.google.com ([209.85.216.201]:56497) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MVnyH-0008Ja-N4 for qemu-devel@nongnu.org; Tue, 28 Jul 2009 10:48:05 -0400 Received: by pxi39 with SMTP id 39so43733pxi.4 for ; Tue, 28 Jul 2009 07:48:04 -0700 (PDT) Message-ID: <4A6F0FA0.4010101@codemonkey.ws> Date: Tue, 28 Jul 2009 09:48:00 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: virtio-serial: An interface for host-guest communication References: <1248717876-17630-1-git-send-email-amit.shah@redhat.com> <4A6E0C9E.10908@codemonkey.ws> <20090727203214.GG15020@redhat.com> <20090727204627.GA32432@shareable.org> <4A6E3BDC.8050101@codemonkey.ws> <20090728140029.GA16067@amd.home.annexia.org> In-Reply-To: <20090728140029.GA16067@amd.home.annexia.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Richard W.M. Jones" Cc: Amit Shah , qemu-devel@nongnu.org, kvm@vger.kernel.org, virtualization@lists.linux-foundation.org Richard W.M. Jones wrote: > On Mon, Jul 27, 2009 at 06:44:28PM -0500, Anthony Liguori wrote: > >> It really suggests that you need _one_ vmchannel that's exposed to >> userspace with a single userspace daemon that consumes it. >> > > ... or a more flexible API. I don't like having fixed /dev/vmch* > devices either. > Indeed. > A long time ago (on a mailing list not so far away) there was a much > better userspace API proposed, which had a separate AF_VMCHANNEL > address family. > > That API works much more like TCP sockets, except without requiring > network devices: > Dave Miller nacked that approach with a sledgehammer instead preferring that we just use standard TCP/IP which is what led to the current implementation using slirp. A userspace daemon with unix domain sockets could give a similar solution. Regards, Anthony Liguori