qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Michael Eager <eager@eagerm.com>
To: "\"陳韋任 (Wei-Ren Chen)\"" <chenwj@iis.sinica.edu.tw>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] How to add new architecture?
Date: Sat, 25 Aug 2012 08:50:29 -0700	[thread overview]
Message-ID: <5038F445.9010800@eagerm.com> (raw)
In-Reply-To: <20120825153827.GA53801@cs.nctu.edu.tw>

On 08/25/2012 08:38 AM, 陳韋任 (Wei-Ren Chen) wrote:
>> 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.

In $QEMU_SRC/configure, architectures have these configuration options
(and several more):
     target_nptl="yes"
     target_phys_bits=32
     target_libs_softmmu="$fdt_libs"

In the target-*/cpu.h, there are defines like:

     #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

There are also required specification like CPUState or CPUArchState.

Is there any description of these configuration options?

 >    I suggest you take a look on openrisc patchset [1], it's a relative
 > new added guest support.
 >
 > [1] https://lists.gnu.org/archive/html/qemu-devel/2012-07/msg02567.html

Thanks.

-- 
Michael Eager	 eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306  650-325-8077

  reply	other threads:[~2012-08-25 15:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-25  0:46 [Qemu-devel] How to add new architecture? Michael Eager
2012-08-25 12:57 ` 陳韋任 (Wei-Ren Chen)
2012-08-25 15:33   ` Michael Eager
2012-08-25 15:38     ` 陳韋任 (Wei-Ren Chen)
2012-08-25 15:50       ` Michael Eager [this message]
2012-08-25 16:02         ` 陳韋任 (Wei-Ren Chen)
2012-08-25 15:43     ` 陳韋任 (Wei-Ren Chen)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5038F445.9010800@eagerm.com \
    --to=eager@eagerm.com \
    --cc=chenwj@iis.sinica.edu.tw \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).