From: Aurelien Jarno <aurelien@aurel32.net>
To: Bobby Bingham <koorogi@koorogi.info>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] target-sh4: move features flag after CPU_COMMON
Date: Mon, 9 Dec 2013 16:59:34 +0100 [thread overview]
Message-ID: <20131209155934.GA14241@ohm.rr44.fr> (raw)
In-Reply-To: <1385323385-25756-1-git-send-email-koorogi@koorogi.info>
On Sun, Nov 24, 2013 at 02:03:05PM -0600, Bobby Bingham wrote:
> Everything before CPU_COMMON in the structure is cleared as part of a
> CPU reset. This included the features flag, which indicates whether SH4A
> instructions are supported or not. As a result, a CPU reset downgraded
> the CPU from an SH4A to an SH4.
>
> Signed-off-by: Bobby Bingham <koorogi@koorogi.info>
> ---
> target-sh4/cpu.h | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/target-sh4/cpu.h b/target-sh4/cpu.h
> index 276d295..c181dda 100644
> --- a/target-sh4/cpu.h
> +++ b/target-sh4/cpu.h
> @@ -157,9 +157,6 @@ typedef struct CPUSH4State {
> /* float point status register */
> float_status fp_status;
>
> - /* The features that we should emulate. See sh_features above. */
> - uint32_t features;
> -
> /* Those belong to the specific unit (SH7750) but are handled here */
> uint32_t mmucr; /* MMU control register */
> uint32_t pteh; /* page table entry high register */
> @@ -180,6 +177,9 @@ typedef struct CPUSH4State {
>
> int id; /* CPU model */
>
> + /* The features that we should emulate. See sh_features above. */
> + uint32_t features;
> +
> void *intc_handle;
> int in_sleep; /* SR_BL ignored during sleep */
> memory_content *movcal_backup;
Thanks, applied.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
prev parent reply other threads:[~2013-12-09 15:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-24 20:03 [Qemu-devel] [PATCH] target-sh4: move features flag after CPU_COMMON Bobby Bingham
2013-11-25 7:52 ` Richard Henderson
2013-12-09 15:59 ` Aurelien Jarno [this message]
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=20131209155934.GA14241@ohm.rr44.fr \
--to=aurelien@aurel32.net \
--cc=koorogi@koorogi.info \
--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).