linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Paul Mackerras <paulus@samba.org>,
	hollisb@us.ibm.com, linuxppc-dev@ozlabs.org
Subject: Re: [RFC][PATCH] initial port of fixmap over from x86 for ppc32
Date: Tue, 8 Apr 2008 11:24:13 -0500	[thread overview]
Message-ID: <20080408162413.GA2552@loki.buserror.net> (raw)
In-Reply-To: <8C415339-5DB0-42B3-A942-17296DE68267@kernel.crashing.org>

On Tue, Apr 08, 2008 at 09:28:12AM -0500, Kumar Gala wrote:
> On Apr 7, 2008, at 6:51 PM, Benjamin Herrenschmidt wrote:
>> As far as the above is concerned, I'm not too fan of fixed virtual
>> addresses. I'd rather dynamically assign it. But we can do it.
>
> I'm in agreement with Ben here.  On Freescale parts that could mean  
> using up to 16M of virtual address space while in reality we may only  
> need a handful of 4k pages to cover SoC registers that we are truly  
> accessing at runtime.

So make it configurable, and turn it off if you're low on address space. 

Most of the time, I'd think saving TLB0 entries would be more beneficial,
especially with heavy I/O workloads where registers get banged on a lot.

It's the early debugging that I'm really concerned with, though.  It gets
old hacking an early mapping in each time.

-Scott

      reply	other threads:[~2008-04-08 16:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-03  6:52 [RFC][PATCH] initial port of fixmap over from x86 for ppc32 Kumar Gala
2008-04-03 18:47 ` Hollis Blanchard
2008-04-03 21:45   ` Benjamin Herrenschmidt
2008-04-06 23:48 ` Paul Mackerras
2008-04-07  0:43   ` Benjamin Herrenschmidt
2008-04-07 13:09   ` Kumar Gala
2008-04-07 16:20     ` Scott Wood
2008-04-07 21:36       ` Kumar Gala
2008-04-07 23:51       ` Benjamin Herrenschmidt
2008-04-08 14:28         ` Kumar Gala
2008-04-08 16:24           ` Scott Wood [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=20080408162413.GA2552@loki.buserror.net \
    --to=scottwood@freescale.com \
    --cc=galak@kernel.crashing.org \
    --cc=hollisb@us.ibm.com \
    --cc=linuxppc-dev@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;
as well as URLs for NNTP newsgroup(s).