From: cminyard@mvista•com (Corey Minyard)
To: linux-arm-kernel@lists•infradead.org
Subject: Conflicting addr value between v6 and v7 for do_PrefetchAbort()
Date: Wed, 21 Aug 2013 21:55:40 -0500 [thread overview]
Message-ID: <52157DAC.4000107@mvista.com> (raw)
I was messing around in this code, talking with someone else about it,
and I discovered that the addr parameter do do_PrefetchAbort() is
different on v6 and v7. For v7 we have:
ENTRY(v7_pabort)
mrc p15, 0, r0, c6, c0, 2 @ get IFAR
mrc p15, 0, r1, c5, c0, 1 @ get IFSR
b do_PrefetchAbort
ENDPROC(v7_pabort)
And for v6:
ENTRY(v6_pabort)
mov r0, r4
mrc p15, 0, r1, c5, c0, 1 @ get IFSR
b do_PrefetchAbort
ENDPROC(v6_pabort)
For v7 that's the address that was accessed to cause the fault. For v6
that appears to be the address of the instruction that caused the
fault. Am I right here? Which of these is correct?
I see
http://lists.infradead.org/pipermail/linux-arm-kernel/2009-September/001051.html
which adds this and
http://lists.infradead.org/pipermail/linux-arm-kernel/2011-June/055019.html
which sets it to r4 for the v6. But you get different values in addr
depending on whether it is v6 or v7.
Thanks,
-corey
reply other threads:[~2013-08-22 2:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=52157DAC.4000107@mvista.com \
--to=cminyard@mvista$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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