From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:40407) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UI4wd-0005xo-Ue for qemu-devel@nongnu.org; Tue, 19 Mar 2013 18:23:49 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UI4wb-0005D5-OB for qemu-devel@nongnu.org; Tue, 19 Mar 2013 18:23:47 -0400 Received: from mail-vc0-f181.google.com ([209.85.220.181]:42908) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UI4wb-0005Ch-Jj for qemu-devel@nongnu.org; Tue, 19 Mar 2013 18:23:45 -0400 Received: by mail-vc0-f181.google.com with SMTP id hv10so825887vcb.26 for ; Tue, 19 Mar 2013 15:23:44 -0700 (PDT) Sender: Paolo Bonzini Message-ID: <5148E56A.4010105@redhat.com> Date: Tue, 19 Mar 2013 23:23:38 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <1363628125-5310-1-git-send-email-pbonzini@redhat.com> <5147572E.8040501@redhat.com> <51475A00.8070304@redhat.com> <5147738F.7070803@redhat.com> <51482F56.4070604@redhat.com> <51483DAB.4040101@redhat.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 00/35] hw/ reorganization, part 2 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: "Edgar E. Iglesias" , Richard Henderson , qemu-devel@nongnu.org, =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= Il 19/03/2013 11:32, Peter Maydell ha scritto: > On 19 March 2013 10:27, Paolo Bonzini wrote: >> Il 19/03/2013 11:10, Peter Maydell ha scritto: >>> Well, for the CPU to be a proper QOM object it should be exposing >>> the IRQ/FIQ lines normally, not via the code in hw/arm/pic_cpu.c. >> >> That applies to everything else that was put in hw/ARCH. Everything >> could become a QOM property. > > Yes. If we clean this stuff up I can kick it back out of hw/ARCH :-) > >>> My point is that the QOM abstraction should encapsulate the CPU >>> cores just like any other piece of hardware. We're not there yet >>> but that's where we should be going. You can't really put the >>> CPUs into the a9mpcore &c containers until we've done that >>> abstraction properly anyway. >> >> Why not? It would remove a bunch of code that is currently duplicated >> in the boards. > > Hmm, maybe. So, okay to put these in hw/arm and then I'll work on patches moving cpu_arm_init to a*mpcore.c? Paolo