From: "Andreas Färber" <andreas.faerber@web.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Renato Utsch <renatoutsch@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Status of the SH4 / ARM7 emulators
Date: Sun, 20 Nov 2011 21:51:04 +0100 [thread overview]
Message-ID: <4EC96838.9000907@web.de> (raw)
In-Reply-To: <CAFEAcA_vVjC0Qu9X4seu0u+30XjQ_4zEsKehqDO1koRidJtVcg@mail.gmail.com>
Am 19.11.2011 22:53, schrieb Peter Maydell:
> We also don't support having multiple CPUs with different architectures
> in one emulator: you can have an ARM emulator, or an SH4 emulator,
> but not an emulation of a system with both an ARM and an SH4 core.
Although I have recently been investigating exactly that combo.
* Part of the problem is that common CPUState fields are not at the
start of the struct. I have therefore been playing with a
CPU_COMMON_PREFIX at the start of the struct and using a macro for
clearing on reset, which preserves part of the common prefix fields.
* Given a CPUState*, we need a way to differentiate different CPU types.
I used an enum CPUType cpu_type as first field in CPU_COMMON_PREFIX.
* cpu_mmu_index() is static inline, we should #define it to a non-static
function in helper.c.
* How to get declarations for such target-specific functions when
#include "target-xyz/cpu.h" would overwrite cpu_init, TARGET_PAGE_SIZE
and other defines?
I hope this'll get easier with QOM.
Andreas
next prev parent reply other threads:[~2011-11-20 20:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-19 21:20 [Qemu-devel] Status of the SH4 / ARM7 emulators Renato Utsch
2011-11-19 21:53 ` Peter Maydell
2011-11-20 20:51 ` Andreas Färber [this message]
2011-11-20 21:48 ` Peter Maydell
2011-11-23 21:59 ` Richard Henderson
2011-11-24 10:44 ` Andreas Färber
2011-11-29 9:09 ` Tristan Gingold
2011-11-29 15:47 ` Richard Henderson
2011-11-20 18:08 ` Andreas Färber
2011-11-20 19:56 ` Peter Maydell
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=4EC96838.9000907@web.de \
--to=andreas.faerber@web.de \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=renatoutsch@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.