From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MJ5l1-0001ut-67 for qemu-devel@nongnu.org; Tue, 23 Jun 2009 09:09:51 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MJ5kw-0001o2-FH for qemu-devel@nongnu.org; Tue, 23 Jun 2009 09:09:50 -0400 Received: from [199.232.76.173] (port=47332 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MJ5kw-0001nf-89 for qemu-devel@nongnu.org; Tue, 23 Jun 2009 09:09:46 -0400 Received: from mx20.gnu.org ([199.232.41.8]:9078) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MJ5kv-0003ox-TL for qemu-devel@nongnu.org; Tue, 23 Jun 2009 09:09:46 -0400 Received: from mail.codesourcery.com ([65.74.133.4]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MJ5ku-0006Sg-Ef for qemu-devel@nongnu.org; Tue, 23 Jun 2009 09:09:45 -0400 From: Paul Brook Subject: Re: [Qemu-devel] virtio-serial: A guest <-> host interface for simple communication Date: Tue, 23 Jun 2009 14:09:40 +0100 References: <1245760953-32139-1-git-send-email-amit.shah@redhat.com> <200906231355.53557.paul@codesourcery.com> <20090623130023.GA32110@amit-x200.redhat.com> In-Reply-To: <20090623130023.GA32110@amit-x200.redhat.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200906231409.41428.paul@codesourcery.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Amit Shah Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org, virtualization@lists.linux-foundation.org On Tuesday 23 June 2009, Amit Shah wrote: > On (Tue) Jun 23 2009 [13:55:52], Paul Brook wrote: > > > Here are two patches. One implements a virtio-serial device in qemu > > > and the other is the driver for a guest kernel. > > > > So I'll ask again. Why is this separate from virtio-console? > > I'm basically writing a vmchannel and found out that a lot can be shared > between some virtio devices. So I'm just trying to abstract out those > things in virtio-serial. Once we're sure virtio-serial is good and ready > to be merged, I will look at converting over virtio-console to the > virtio-serial interface. That doesn't really answer my question. We already have a virtual serial device (called virtio-console). Why are you inventing another one? Paul