qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Towers <atowers@gmail.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Paul Brook <paul@codesourcery.com>,
	Andrew Towers <atowers@gmail.com>
Subject: [Qemu-devel] [PATCH] ARM: Permit any ARMv6K CPU to read the MVFR0 and MVFR1 VFP registers.
Date: Thu, 29 Mar 2012 01:37:28 +1100	[thread overview]
Message-ID: <1332945448-31266-1-git-send-email-atowers@gmail.com> (raw)

From: Andrew Towers <atowers@gmail.com>

Replaces the ARM_FEATURE_VFP3 check when reading MVFR0/1 with a check for
ARM_FEATURE_V6K. Rationale: MVFR0/1 were introduced in the ARM1136 at the
same time as ARMv6K, and a survey of TRMs indicates support in later models.

According to reference documentation on arm.com, MVFR0 and MVFR1 were
introduced in ARM1136JF-S r1p1 (ARMv6K, VFPv2). They are also present in
ARM1156T2F-S and ARM1176JZF-S, which contain VFP11 r5, and in ARM11 MPCore
r1 which contains VFP11 r4.

Reference (ARM DDI 0211H, 0290G, 0301H, 0360E)
http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0211h/Ffbefjag.html

Without this change, the linux kernel will not boot with VFP support enabled
under ARM1176 system emulation, due to the unconditional use of MVFR1 at the
end of vfp_init() in arch/arm/vfp/vfpmodule.c in the kernel:

  VFP support v0.3: implemetor 41 architecture 1 part 20 variant b rev 5
  Internal error: Oops - undefined instruction: 0 [#1]

Yes, I am slightly abusing the versatilepb hw emulation, but then so is
everyone else in the world who is still waiting for their Raspberry Pi ;)

Signed-off-by: Andrew Towers <atowers@gmail.com>
---
 target-arm/translate.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/target-arm/translate.c b/target-arm/translate.c
index 81725d1..b5861c8 100644
--- a/target-arm/translate.c
+++ b/target-arm/translate.c
@@ -2906,7 +2906,7 @@ static int disas_vfp_insn(CPUARMState * env, DisasContext *s, uint32_t insn)
                         case ARM_VFP_MVFR0:
                         case ARM_VFP_MVFR1:
                             if (IS_USER(s)
-                                || !arm_feature(env, ARM_FEATURE_VFP3))
+                                || !arm_feature(env, ARM_FEATURE_V6K))
                                 return 1;
                             tmp = load_cpu_field(vfp.xregs[rn]);
                             break;
-- 
1.7.5.4

             reply	other threads:[~2012-03-28 14:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-28 14:37 Andrew Towers [this message]
2012-03-28 15:24 ` [Qemu-devel] [PATCH] ARM: Permit any ARMv6K CPU to read the MVFR0 and MVFR1 VFP registers Peter Maydell
2012-03-29 12:41   ` [Qemu-devel] [PATCH v2] " Andrew Towers
2012-03-29 13:10     ` Andreas Färber
2012-03-29 13:46     ` 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=1332945448-31266-1-git-send-email-atowers@gmail.com \
    --to=atowers@gmail.com \
    --cc=paul@codesourcery.com \
    --cc=peter.maydell@linaro.org \
    --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).