From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:48753) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TCYsx-0008MT-Dv for qemu-devel@nongnu.org; Fri, 14 Sep 2012 12:36:59 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TCYsr-0007uR-JP for qemu-devel@nongnu.org; Fri, 14 Sep 2012 12:36:55 -0400 Received: from mail-pz0-f45.google.com ([209.85.210.45]:48733) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TCYsr-0007to-DS for qemu-devel@nongnu.org; Fri, 14 Sep 2012 12:36:49 -0400 Received: by dadn15 with SMTP id n15so2631424dad.4 for ; Fri, 14 Sep 2012 09:36:47 -0700 (PDT) Sender: Paolo Bonzini Message-ID: <50535D18.9030104@redhat.com> Date: Fri, 14 Sep 2012 18:36:40 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <50532E80.5060905@redhat.com> <50534127.6010604@weilnetz.de> In-Reply-To: <50534127.6010604@weilnetz.de> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] directory hierarchy List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Weil Cc: qemu-devel Il 14/09/2012 16:37, Stefan Weil ha scritto: > Here are some more ideas: > > * Move the target-xxx directories (currently 15) to target/xxx. Yes, of course. > * Add host/xxx for host specific files (xxx = posix, wxx). > Here the currently used win32 might be replaced by either > wxx or by win as most of it also applies to w64. > An alternative solution would add host specific subdirectories > to include/qemu and util. This makes sense, though it becomes more problematic as the host files are scattered around the tree. > * Move machine implementations (code which calls machine_init) > to the respective architecture directories (hw/arm, ...). > Meanwhile we have more than 50 machine implementations in hw. > We could also replace hw/alpha, hw/arm, hw/cris, ... to > hw/arch/alpha and so on. > > * Move hardware implementations which are architecture specific > to the architecture directories. This is sometimes less obvious > than the machine implementations. This I left out purposedly. :) Paolo