All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Bykowski <marek.bykowski@gmail.com>
To: u-boot@lists.denx.de
Subject: [PATCHv2] armv8: MMU: Mark code memory Executable, any other Non-Executable
Date: Wed, 19 Aug 2020 15:17:24 +0200	[thread overview]
Message-ID: <20200819131723.GA2195@marek-VirtualBox> (raw)
In-Reply-To: <20200722125110.GM6227@bill-the-cat>

> I think this will have to wait for you to return from holidays and
> investigate more.  All I know is that the QEMU models are working as
> expected prior to the patch and fail with it.
>
> --
> Tom

From the esr (Exception Syndrome Register) = 0x9600004F:
- EC (Exception Class) -> it is an exception from data abort
- from ISS (Instruction specific syndrome) -> WnR field set = Abort caused
  by Write (not Read), Data Fault Status Code = Permission fault, third level

It looks like it results as a Write attempted to a read-only region.
Are you sure the tests are devised/designed so that they are not trying to
write to a read-only region?

@Tom
Probably I could send you a patch with debugging in that will print out all
the necessary information before reaching a prompt (or after a command).
Would you agree to apply and run it?

What I'm really looking for is the address map with the attributes. Sth around
it:
EL2N:0x00000000-0x3FD35FFF NP:0x00000000-0x3FD35FFF Normal RW C S XN

Marek

  reply	other threads:[~2020-08-19 13:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-19 11:24 [PATCH] armv8: MMU: Mark code memory Executable, any other Non-Executable marek.bykowski at gmail.com
2020-06-19 12:53 ` [PATCHv2] " marek.bykowski at gmail.com
2020-06-24 12:35   ` Marek Bykowski
2020-07-18 15:34   ` Tom Rini
2020-07-21  0:33     ` Marek
2020-07-22 12:51       ` Tom Rini
2020-08-19 13:17         ` Marek Bykowski [this message]
2020-08-19 13:35           ` Tom Rini

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=20200819131723.GA2195@marek-VirtualBox \
    --to=marek.bykowski@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.