From: Segher Boessenkool <segher@kernel.crashing.org>
To: christophe leroy <christophe.leroy@c-s.fr>
Cc: Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org,
Markus Elfring <elfring@users.sourceforge.net>,
Christian Lamparter <chunkeey@gmail.com>
Subject: Re: [PATCH] powerpc/4xx/ocm: fix compiler error
Date: Sat, 22 Dec 2018 17:04:51 -0600 [thread overview]
Message-ID: <20181222230451.GB23740@gate.crashing.org> (raw)
In-Reply-To: <f365c733-6a1d-1ae9-067a-2a9490388c38@c-s.fr>
On Sat, Dec 22, 2018 at 08:37:28PM +0100, christophe leroy wrote:
> Le 22/12/2018 à 18:16, Segher Boessenkool a écrit :
> >On Sat, Dec 22, 2018 at 02:08:02PM +0100, christophe leroy wrote:
> >>
> >>Usually, Guarded implies no exec (at least on 6xx and 8xx).
> >
> >Huh? What do you mean here?
>
> From the 885 Reference Manual:
>
> Address translation: the EA is translated by using the MMU’s TLB
> mechanism. Instructions are not fetched from no-execute or guarded
> memory and data accesses are not executed speculatively to or from the
> guarded memory.
>
> 6.1.3.4 Instruction TLB Error Exception (0x01300)
> This type of exception occurs as a result of one of the following
> conditions if MSR[IR] = 1:
> - The EA cannot be translated.
> - The fetch access violates memory protection
> - The fetch access is to guarded memory
>
>
> From e300core reference manual:
>
> Translation Exception Conditions:
> Exception condition: Instruction fetch from guarded memory
> with MSR[IR] = 1 ==> ISI interrupt SRR1[3] = 1
Right, but you said 6xx as well, i.e. pure PowerPC.
If for example IR=0 you cannot have N=1, but you do have G=1. There is
no case where G=1 implies N=1 afaik, or where fetch is prohibited some
other way (causes an ISI, say).
Segher
next prev parent reply other threads:[~2018-12-22 23:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-22 10:09 [PATCH] powerpc/4xx/ocm: fix compiler error Christian Lamparter
2018-12-22 10:59 ` christophe leroy
2018-12-22 11:27 ` Christian Lamparter
2018-12-22 13:08 ` christophe leroy
2018-12-22 14:32 ` Christian Lamparter
2018-12-22 17:16 ` Segher Boessenkool
2018-12-22 19:37 ` christophe leroy
2018-12-22 23:04 ` Segher Boessenkool [this message]
2018-12-23 8:29 ` Gabriel Paubert
2018-12-23 9:31 ` Segher Boessenkool
2018-12-23 9:58 ` christophe leroy
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=20181222230451.GB23740@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=christophe.leroy@c-s.fr \
--cc=chunkeey@gmail.com \
--cc=elfring@users.sourceforge.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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