From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Dave Martin <Dave.Martin@arm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: fix alignement of __bug_table section entries
Date: Sun, 06 Sep 2015 00:12:59 +0200 [thread overview]
Message-ID: <87pp1wwm50.fsf@belgarion.home> (raw)
In-Reply-To: <20150905203818.GO21084@n2100.arm.linux.org.uk> (Russell King's message of "Sat, 5 Sep 2015 21:38:18 +0100")
Russell King - ARM Linux <linux@arm.linux.org.uk> writes:
>> Moreover, this is consistent with the fact that this commit is in linux-next but
>> not in v4.1 :
>> a5e090acbf54 ("ARM: software-based priviledged-no-access support")
>>
>> So the issue is around this SW_DOMAIN_PAN, at least on PXA.
>
> Is it only PXA which seems to be affected?
Sorry I don't know, I only own pxa platforms.
> If so, you may need to add:
>
> mrc p15, 0, \rd, c2, c0, 0
> mov \rd, \rd
> sub pc, pc, #4
>
> to the places we update the domain access register to ensure that the
> Xscale pipeline stalls to allow the CP15 DACR update to hit.
Okay, I'll try that.
By the way, the ARMv5 manual states in chapter "B4.5.1 MMU Fault" that for a
DACR update, a "PrefetchFlush" operation has to be done (chapter B2.6.3
PrefetchFlush CP15 register 7), quoting :
Changes to the Domain Access Control register are synchronized by performing
a PrefetchFlush operation (or as result of an exception or exception
return). See Changes to CP15 registers and the memory order model on page
B2-24 for details.
Cheers.
--
Robert
next prev parent reply other threads:[~2015-09-05 22:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 6:23 [PATCH] ARM: fix alignement of __bug_table section entries Robert Jarzmik
2015-09-02 10:39 ` Dave Martin
2015-09-05 13:48 ` Robert Jarzmik
2015-09-05 14:25 ` Russell King - ARM Linux
2015-09-05 17:10 ` Robert Jarzmik
2015-09-05 20:38 ` Russell King - ARM Linux
2015-09-05 22:12 ` Robert Jarzmik [this message]
2015-09-06 17:25 ` Robert Jarzmik
2015-09-06 19:48 ` Russell King - ARM Linux
2015-09-06 21:31 ` Robert Jarzmik
2015-09-06 23:54 ` Russell King - ARM Linux
2015-09-08 17:01 ` Robert Jarzmik
2015-09-08 20:08 ` Russell King - ARM Linux
2015-09-08 20:46 ` Robert Jarzmik
2015-09-09 23:06 ` Robert Jarzmik
2015-09-10 19:01 ` Robert Jarzmik
2015-09-10 19:16 ` Russell King - ARM Linux
2015-09-10 20:53 ` Robert Jarzmik
2015-09-11 9:54 ` Russell King - ARM Linux
2015-09-11 9:56 ` [PATCH 1/2] ARM: domains: thread_info.h no longer needs asm/domains.h Russell King
2015-09-11 9:56 ` [PATCH 2/2] ARM: domains: add memory dependencies to get_domain/set_domain Russell King
2015-09-11 14:56 ` Robert Jarzmik
2015-09-11 15:10 ` Russell King - ARM Linux
2015-09-11 15:40 ` Robert Jarzmik
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=87pp1wwm50.fsf@belgarion.home \
--to=robert.jarzmik@free.fr \
--cc=Dave.Martin@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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