From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55743) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V1dXY-0007B4-KX for qemu-devel@nongnu.org; Tue, 23 Jul 2013 10:26:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V1dXW-0002ro-Qn for qemu-devel@nongnu.org; Tue, 23 Jul 2013 10:26:12 -0400 Received: from mail-ob0-f178.google.com ([209.85.214.178]:38802) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V1dXW-0002rb-Md for qemu-devel@nongnu.org; Tue, 23 Jul 2013 10:26:10 -0400 Received: by mail-ob0-f178.google.com with SMTP id fb19so10237785obc.37 for ; Tue, 23 Jul 2013 07:26:10 -0700 (PDT) From: Anthony Liguori In-Reply-To: References: <1374515411-43818-1-git-send-email-agraf@suse.de> <51EE74D8.5060609@redhat.com> <51EE7864.1030408@redhat.com> Date: Tue, 23 Jul 2013 09:26:07 -0500 Message-ID: <87haflnyio.fsf@codemonkey.ws> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: [Qemu-devel] [PATCH 0/9] Add platform bus List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell , Paolo Bonzini Cc: "qemu-ppc@nongnu.org list:PowerPC" , Alexander Graf , qemu-devel Developers Peter Maydell writes: > On 23 July 2013 13:34, Paolo Bonzini wrote: >> Il 23/07/2013 14:22, Peter Maydell ha scritto: >>> On 23 July 2013 13:19, Paolo Bonzini wrote: > Yes, we should have easy support for defining a pluggable > bus as a collection of pins. > >> In fact, the main thing I dislike about Alex's patch is adding a new bus >> instead of making sysbus devices "just work" as pluggable devices. > > Agreed, more or less. Actually I'd rather sysbus devices > went away -- the requirement for interrupt and GPIO and > memory regions to all be defined as single arrays (so you > have to know what interrupt line 3 happens to be, and > that memory region 1 is the registers, and so on) is > pretty unfriendly. We should be able to define all these > as named connections. The concrete next steps here are well known. 1) Make MemoryRegion's QOM objects and add them as children to the devices that own them. 2) Make qemu_irq a QOM object. Then you could use -device to plumb up all of these things without SysBus being involved. But the above is a lot of work for a use-case that while interesting academically so far hasn't proven to be all that important. Regards, Anthony Liguori > > -- PMM