mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH 3/3] arm64: Set PXN/UXN attributes for uncached mem
Date: Tue, 31 Mar 2020 11:20:47 +0200	[thread overview]
Message-ID: <20200331092047.GN27288@pengutronix.de> (raw)
In-Reply-To: <20200331090135.GM27288@pengutronix.de>

On Tue, Mar 31, 2020 at 11:01:35AM +0200, Sascha Hauer wrote:
> On Tue, Mar 31, 2020 at 10:33:54AM +0200, Ahmad Fatoum wrote:
> > 
> > 
> > On 3/31/20 10:01 AM, Sascha Hauer wrote:
> > > The attributes should be set to avoid speculative access to memory-mapped
> > > peripherals.
> > > 
> > > The patch has been tested with:
> > > 
> > > noinline unsigned long nox(void)
> > > {
> > > 	return get_pc();
> > > }
> > > 
> > > static void xn_test(void)
> > > {
> > > 	void *adr = (void *)SOME_SRAM_ADDRESS;
> > > 	unsigned long ret;
> > > 	unsigned long (*fn)(void) = adr;
> > > 
> > > 	memcpy(adr, nox, 0x1000);
> > > 
> > > 	sync_caches_for_execution();
> > > 
> > > 	ret = fn();
> > > 	printf("pc: 0x%08lx\n", ret);
> > > }
> > > 
> > > Without this patch nox() gets executed in SRAM, with it runs into a
> > > abort as expected.
> > > 
> > > Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> > > ---
> > >  arch/arm/cpu/mmu_64.h | 3 ++-
> > >  1 file changed, 2 insertions(+), 1 deletion(-)
> > > 
> > > diff --git a/arch/arm/cpu/mmu_64.h b/arch/arm/cpu/mmu_64.h
> > > index a2a5477569..f5b7624037 100644
> > > --- a/arch/arm/cpu/mmu_64.h
> > > +++ b/arch/arm/cpu/mmu_64.h
> > > @@ -6,7 +6,8 @@
> > >  			 PTE_BLOCK_AF)
> > >  #define UNCACHED_MEM    (PTE_BLOCK_MEMTYPE(MT_DEVICE_nGnRnE) | \
> > >  			 PTE_BLOCK_OUTER_SHARE | \
> > > -			 PTE_BLOCK_AF)
> > > +			 PTE_BLOCK_AF | \
> > > +			 PTE_BLOCK_UXN)
> > 
> > Don't we need PXN in EL1?
> 
> We are not in EL1 currently. What happens if we change the exception
> level after the MMU setup? In that case we would have to adjust the
> attributes of the existing page tables when doing so. We are currently
> not prepared for that so I am not sure how much sense it makes to test
> for the EL here.

Hm, this is no reason for not honoring the current EL in the first
place, I'll update the patch accordingly.

Sascha


-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2020-03-31  9:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-31  8:01 [PATCH 1/3] ARM64: Setup vectors in all lower execption levels Sascha Hauer
2020-03-31  8:01 ` [PATCH 2/3] ARM64: attribute argument to create_sections() is 64bit Sascha Hauer
2020-03-31  8:01 ` [PATCH 3/3] arm64: Set PXN/UXN attributes for uncached mem Sascha Hauer
2020-03-31  8:33   ` Ahmad Fatoum
2020-03-31  9:01     ` Sascha Hauer
2020-03-31  9:20       ` Sascha Hauer [this message]
2020-03-31 10:10         ` Ahmad Fatoum
2020-03-31 10:12   ` [PATCH v2] " Sascha Hauer
2020-03-31 10:18     ` Sascha Hauer
2020-03-31 10:17   ` Sascha Hauer
2020-03-31 10:27     ` Ahmad Fatoum

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=20200331092047.GN27288@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@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