From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MZ3Zz-0003qU-9j for qemu-devel@nongnu.org; Thu, 06 Aug 2009 10:04:27 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MZ3Zu-0003pi-Jr for qemu-devel@nongnu.org; Thu, 06 Aug 2009 10:04:26 -0400 Received: from [199.232.76.173] (port=53912 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MZ3Zu-0003pf-DP for qemu-devel@nongnu.org; Thu, 06 Aug 2009 10:04:22 -0400 Received: from mx2.redhat.com ([66.187.237.31]:35485) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MZ3Zt-0005YH-QA for qemu-devel@nongnu.org; Thu, 06 Aug 2009 10:04:22 -0400 Date: Thu, 6 Aug 2009 19:34:04 +0530 From: Amit Shah Subject: Re: [Qemu-devel] Re: virtio-serial: An interface for host-guest communication Message-ID: <20090806140404.GA12083@amit-x200.redhat.com> References: <20090727204627.GA32432@shareable.org> <4A6E3BDC.8050101@codemonkey.ws> <20090728140029.GA16067@amd.home.annexia.org> <4A77410D.4090804@codemonkey.ws> <20090805175713.GB28738@shareable.org> <4A79C8D9.5030606@codemonkey.ws> <20090806103843.GC9222@amit-x200.redhat.com> <4A7ADAC4.70902@codemonkey.ws> <20090806134103.GC11733@amit-x200.redhat.com> <4A7AE169.4000606@codemonkey.ws> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A7AE169.4000606@codemonkey.ws> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Rusty Russell , virtualization@lists.linux-foundation.org, qemu-devel@nongnu.org, kvm@vger.kernel.org, "Richard W.M. Jones" On (Thu) Aug 06 2009 [08:58:01], Anthony Liguori wrote: > Amit Shah wrote: >> On (Thu) Aug 06 2009 [08:29:40], Anthony Liguori wrote: >> >>> Amit Shah wrote: >>> >>>> Sure; but there's been no resistance from anyone from including the >>>> virtio-serial device driver so maybe we don't need to discuss that. >>>> >>> There certainly is from me. The userspace interface is not >>> reasonable for guest applications to use. >>> >> >> One example that would readily come to mind is dbus. A daemon running on >> the guest that reads data off the port and interacts with the desktop by >> appropriate dbus commands. All that's needed is a stream of bytes and >> virtio-serial provides just that. >> > > dbus runs as an unprivileged user, how does dbus know which > virtio-serial port to open and who sets the permissions on that port? The permission part can be handled by package maintainers and sysadmins via udev policies. So all data destined for dbus consumption gets to a daemon and that daemon then sends it over to dbus. Amit