From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:43850) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TkyHJ-0001WS-Pc for qemu-devel@nongnu.org; Tue, 18 Dec 2012 09:36:22 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TkyHF-0007Fd-7c for qemu-devel@nongnu.org; Tue, 18 Dec 2012 09:36:17 -0500 Received: from mx1.redhat.com ([209.132.183.28]:6166) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TkyHE-0007FO-Ud for qemu-devel@nongnu.org; Tue, 18 Dec 2012 09:36:13 -0500 Message-ID: <50D07F50.6010800@redhat.com> Date: Tue, 18 Dec 2012 15:36:00 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <1354887155-32281-1-git-send-email-fred.konrad@greensocs.com> <20121217154508.GA28712@redhat.com> <20121218110153.GC22586@redhat.com> <50D05898.9030506@redhat.com> <20121218131043.GA26110@redhat.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC PATCH v6 0/6] Virtio refactoring. List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: aliguori@us.ibm.com, e.voevodin@samsung.com, "Michael S. Tsirkin" , mark.burton@greensocs.com, qemu-devel@nongnu.org, stefanha@redhat.com, cornelia.huck@de.ibm.com, afaerber@suse.de, fred.konrad@greensocs.com Il 18/12/2012 15:00, Peter Maydell ha scritto: > On 18 December 2012 13:10, Michael S. Tsirkin wrote: >> > And what makes virtio so special anyway? e1000 can be used without >> > exposing users to internal buses and all kind of nastiness like this. > Congratulations, you're using an architecture that has a pluggable > discoverable bus implemented by just about all machines using that > architecture. That makes things much easier for you. Yes, that's true. And you're basically using virtio as the pluggable discoverable bus, which is actually a pretty good idea. However, what you are doing is very similar to what virtio-s390 does, and it manages to do it just fine with the existing virtio.c infrastructure. The only difference is that you have a 1:1 relationship between virtio-mmio "slots" described by the board and virtio-mmio devices added by the user. True, it is not pure qdev, but it is much simpler and doesn't require convincing grumpy maintainers. :) Paolo