mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Andrey Smirnov <andrew.smirnov@gmail.com>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [RFC] ARM: mmu: Do not try to pick early TTB up
Date: Mon, 28 May 2018 14:05:32 +0200	[thread overview]
Message-ID: <20180528120532.2imhhmkfu74rb2zr@pengutronix.de> (raw)
In-Reply-To: <CAHQ1cqG9v=mcKjhusqZYPtqv_sC9U0sxaxh0Tk6E0c_UVmgOaQ@mail.gmail.com>

On Fri, May 25, 2018 at 10:09:52AM -0700, Andrey Smirnov wrote:
> On Fri, May 25, 2018 at 2:01 AM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> > On Thu, May 24, 2018 at 08:14:40PM -0700, Andrey Smirnov wrote:
> >> On Wed, May 23, 2018 at 1:43 AM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> >> > On Tue, May 22, 2018 at 10:10:12PM -0700, Andrey Smirnov wrote:
> >> >> The call to create_flat_mapping() in mmu.c will change both memory
> >> >> type and shareability of all RAM in use by barebox while MMU is on
> >> >> when done in conjunction with CONFIG_MMU_EARLY.
> >> >
> >> > I notice that with MMU_EARLY enabled we call create_flat_mapping()
> >> > twice, once in the early MMU code and once when setting up the MMU for
> >> > real. In between we remap the the SDRAM cached which then is reverted
> >> > during the second call to create_flat_mapping().
> >> >
> >> > This seems unnecessary. Does the following help you?
> >>
> >> Yeah, this, disabling MMU before or having a tlb_invalidate() after
> >> all seem to help. Your patch works fine, but it has a slight weirdness
> >> in my case because early MMU code would mark OCRAM as cached and
> >> regular MMU code wouldn't undo it without the call to
> >> create_flat_mapping(), so I'd end up with slightly different memory
> >> configuration depending on if EARLY_MMU is enabled or not. Other than
> >> that it should work fine.
> >>
> >> The main reason I chose to go "disable MMU" route is because that
> >> follows what ARMv8 MMU code does, but I am perfectly happy with either
> >> solution.
> >
> > Disabling the MMU probably has a performance impact (I would have to
> > remeasure, maybe this is not true at all), that's why I would prefer
> > keeping it enabled.
> >
> 
> OK, sure. Where do we go from here? Do you want to just take your
> patch or should I update mine, with its War And Peace of a commit
> message, and incorporate what you proposed?

I applied my patch for now. We can still disable the MMU between PBL and
barebox later should we have to.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 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

  parent reply	other threads:[~2018-05-28 12:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-23  5:10 Andrey Smirnov
2018-05-23  8:43 ` Sascha Hauer
2018-05-25  3:14   ` Andrey Smirnov
2018-05-25  9:01     ` Sascha Hauer
2018-05-25  9:09       ` Lucas Stach
2018-05-25 17:07         ` Andrey Smirnov
2018-05-25 17:09       ` Andrey Smirnov
2018-05-25 17:35         ` Sam Ravnborg
2018-05-28 12:05         ` Sascha Hauer [this message]
2018-05-28 18:08           ` Andrey Smirnov

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=20180528120532.2imhhmkfu74rb2zr@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=andrew.smirnov@gmail.com \
    --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