From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:59692)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <chenwj@cs.nctu.edu.tw>) id 1T5Iot-0008Tq-3C
	for qemu-devel@nongnu.org; Sat, 25 Aug 2012 12:02:49 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <chenwj@cs.nctu.edu.tw>) id 1T5Ion-0005nr-Hd
	for qemu-devel@nongnu.org; Sat, 25 Aug 2012 12:02:43 -0400
Received: from csmailer.cs.nctu.edu.tw ([140.113.235.130]:49427)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <chenwj@cs.nctu.edu.tw>) id 1T5Ion-0005nZ-0y
	for qemu-devel@nongnu.org; Sat, 25 Aug 2012 12:02:37 -0400
Date: Sun, 26 Aug 2012 00:02:32 +0800
From: =?utf-8?B?6Zmz6Z+L5Lu7IChXZWktUmVuIENoZW4p?= <chenwj@iis.sinica.edu.tw>
Message-ID: <20120825160230.GA85191@cs.nctu.edu.tw>
References: <50382073.60503@eagerm.com> <20120825125742.GA72482@cs.nctu.edu.tw>
	<5038F055.7060300@eagerm.com>
	<20120825153827.GA53801@cs.nctu.edu.tw>
	<5038F445.9010800@eagerm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <5038F445.9010800@eagerm.com>
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] How to add new architecture?
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Michael Eager <eager@eagerm.com>
Cc: qemu-devel@nongnu.org, =?utf-8?B?IumZs+mfi+S7uyAoV2VpLVJlbiBDaGVuKSI=?= <chenwj@iis.sinica.edu.tw>

On Sat, Aug 25, 2012 at 08:50:29AM -0700, Michael Eager wrote:
> On 08/25/2012 08:38 AM, =E9=99=B3=E9=9F=8B=E4=BB=BB (Wei-Ren Chen) wrot=
e:
> >> I want to add a new guest architecture.
> >>
> >> Is there any description of what the configuration options mean?
> >
> >    You mean the options list in `../${QEMU_SRC}/configure --help`?
> > Not sure why you need to care about that.
>=20
> In $QEMU_SRC/configure, architectures have these configuration options
> (and several more):
>      target_nptl=3D"yes"
>      target_phys_bits=3D32
>      target_libs_softmmu=3D"$fdt_libs"
>=20
> In the target-*/cpu.h, there are defines like:
>=20
>      #define TARGET_LONG_BITS 32
>      #define TARGET_HAS_ICE 1
>      #define TARGET_PAGE_BITS 12
>      #define TARGET_PAGE_BITS 10
>      #define TARGET_PHYS_ADDR_SPACE_BITS 40
>      #define TARGET_VIRT_ADDR_SPACE_BITS 32
>=20
> There are also required specification like CPUState or CPUArchState.
>=20
> Is there any description of these configuration options?

  Well, you need to read the source code. :) Basically, TARGET_XXX
describes guest characteristics. QEMU now is refactoring its code base,
for example, perfer to use CPUArchState rather than CPUState. OpenRISC
port is a good example/template you can use.

Regards,
chenwj

--=20
Wei-Ren Chen (=E9=99=B3=E9=9F=8B=E4=BB=BB)
Computer Systems Lab, Institute of Information Science,
Academia Sinica, Taiwan (R.O.C.)
Tel:886-2-2788-3799 #1667
Homepage: http://people.cs.nctu.edu.tw/~chenwj