From: ynorov@caviumnetworks.com (Yury Norov)
To: linux-arm-kernel@lists.infradead.org
Subject: arm64: kernel v4.6-rc1 hangs on QEMU
Date: Wed, 30 Mar 2016 01:52:16 +0300 [thread overview]
Message-ID: <20160329225216.GB31869@yury-N73SV> (raw)
In-Reply-To: <3334343.7r57EH3qRj@wuerfel>
On Wed, Mar 30, 2016 at 12:32:42AM +0200, Arnd Bergmann wrote:
> On Wednesday 30 March 2016 01:22:17 Yury Norov wrote:
> > >
> > > Undefined instruction in cpuinfo_store_boot_cpu() could be related
> > > to the SYS_ID_AA64MMFR2_EL1 access that was recently added.
> > >
> > > What does the architecture say about reading unknown cpuid registers?
> > >
> > > Arnd
> >
> > ThunderX has some unimplemented system registers. AFAIR, attempt to access it
> > causes data abort.
>
> Ok, if that is the case, maybe the read_cpuid() macro can be changed
> so it contains a fixup for the trap? That should handle both data abort
> and undefinstr.
>
> Arnd
Sounds alluring, but not clear what we'd return that way. I mean, how
we'd distinguish between correct value and error code (0, -1 or whatever).
But I think, we can do like this:
val = read_cpuid_safe(reg, impossible_val);
if (val == impossible_val)
goto err;
I think it will work for many cases.
Yury.
next prev parent reply other threads:[~2016-03-29 22:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 22:05 arm64: kernel v4.6-rc1 hangs on QEMU Yury Norov
2016-03-29 22:12 ` Arnd Bergmann
2016-03-29 22:22 ` Yury Norov
2016-03-29 22:32 ` Arnd Bergmann
2016-03-29 22:52 ` Yury Norov [this message]
2016-03-30 6:44 ` Kefeng Wang
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=20160329225216.GB31869@yury-N73SV \
--to=ynorov@caviumnetworks.com \
--cc=linux-arm-kernel@lists.infradead.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