From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mi7vN-00045y-A0 for qemu-devel@nongnu.org; Mon, 31 Aug 2009 10:32:01 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mi7vH-000437-1v for qemu-devel@nongnu.org; Mon, 31 Aug 2009 10:32:00 -0400 Received: from [199.232.76.173] (port=38261 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mi7vF-00042j-TI for qemu-devel@nongnu.org; Mon, 31 Aug 2009 10:31:54 -0400 Received: from mx1.redhat.com ([209.132.183.28]:41409) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mi7vF-0007M1-AU for qemu-devel@nongnu.org; Mon, 31 Aug 2009 10:31:53 -0400 Date: Mon, 31 Aug 2009 20:01:01 +0530 From: Amit Shah Message-ID: <20090831143101.GA16943@amit-x200.redhat.com> References: <1251181044-3696-1-git-send-email-amit.shah@redhat.com> <20090826112718.GA11117@amit-x200.redhat.com> <4A980D18.30106@codemonkey.ws> <20090830101057.GB32563@amit-x200.redhat.com> <4A9A7525.6010707@codemonkey.ws> <20090830131738.GC3401@amit-x200.redhat.com> <4A9BCD61.2040903@codemonkey.ws> <20090831135147.GA16371@amit-x200.redhat.com> <4A9BDC59.1090801@codemonkey.ws> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A9BDC59.1090801@codemonkey.ws> Subject: [Qemu-devel] Re: Extending virtio_console to support multiple ports List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org, virtualization@lists.linux-foundation.org On (Mon) Aug 31 2009 [09:21:13], Anthony Liguori wrote: > Amit Shah wrote: >> Can you please explain your rationale for being so rigid about merging >> the two drivers? >> > > Because they do the same thing. I'm not going to constantly rehash > this. It's been explained multiple times. It hardly looks like the same thing each passing day. I've also mentioned that each minimal virtio device would start out looking the same. We're ending up having to compromise on the performance or functionality or simplicity the devices just because of this restriction. > If there are implementation issues within the Linux drivers because of > peculiarities of hvc then hvc needs to be fixed. It has nothing to do > with the driver ABI which is what qemu cares about. I'd welcome that effort as well. But we all know that's not going to happen anytime soon. Also, there's no driver ABI for virtio-serial yet. Amit