linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: SCU registers mapping for CA9/CA5 cores
Date: Wed, 26 Jun 2013 20:22:10 +0200	[thread overview]
Message-ID: <201306262022.11103.arnd@arndb.de> (raw)
In-Reply-To: <20130624090640.GZ2718@n2100.arm.linux.org.uk>

On Monday 24 June 2013, Russell King - ARM Linux wrote:
> On Fri, Jun 21, 2013 at 11:29:22AM +0200, Arnd Bergmann wrote:
> > I think we could actually move everything between VMALLOC_END and
> > ffff0000 into a larger fixmap. This would be a substantial change,
> > but it would give us more vmalloc space for most configurations
> > and more flexibility with what else we could put into fixmap.
> 
> ... at the expense of:
> (a) having to look up the PTE table pointer every time we want to add or
> remove a mapping,

Is that a frequent operation? I guess it's not important given the
argument below.

> (b) wasting the top 15 pages from being used.
> 
> Also, the placement of some of these pages matters especially for the
> VIPT aliasing caches, where cache colouring becomes important.  So an
> enum in fixmap isn't going to work for those.

x86 deals with alignment through some extra tricks, it's certainly doable
but I agree it's not improving readability if you do that.

> Really, the value to such a change is very low and is really just churn
> for churn's sake.  "Oh we can do something different!"  No.

Ok, fair enough.

I also saw the patch for early_ioremap, which would basically require
doing something like this. I'll comment on that email separately.

	Arnd

      reply	other threads:[~2013-06-26 18:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-21  6:11 SCU registers mapping for CA9/CA5 cores Chao Xie
2013-06-21  8:13 ` Russell King - ARM Linux
2013-06-21  9:29   ` Arnd Bergmann
2013-06-24  1:22     ` Chao Xie
2013-06-24  9:06     ` Russell King - ARM Linux
2013-06-26 18:22       ` Arnd Bergmann [this message]

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=201306262022.11103.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).