From: Scott Wood <scottwood@freescale•com>
To: Kumar Gala <galak@kernel•crashing.org>
Cc: linuxppc-dev@ozlabs•org, Paul Mackerras <paulus@samba•org>,
hollisb@us•ibm.com
Subject: Re: [RFC][PATCH] initial port of fixmap over from x86 for ppc32
Date: Mon, 7 Apr 2008 11:20:53 -0500 [thread overview]
Message-ID: <20080407162053.GB2688@loki.buserror.net> (raw)
In-Reply-To: <279F1861-9605-46FD-A917-DF5B95B8C4F6@kernel.crashing.org>
On Mon, Apr 07, 2008 at 08:09:57AM -0500, Kumar Gala wrote:
> On Apr 6, 2008, at 6:48 PM, Paul Mackerras wrote:
>> More generally, I think we need to take an overall look at what things
>> we are using fixed virtual addresses for, and why they need to be
>> fixed. If there are indeed several such things then we can introduce
>> the fixmap stuff.
>
> The list as I see it:
> * kmap
> * pci-e config for 4xx/83xx
> * kexec/kdump (ben commented on this when Dale posted his patches for
> ppc32 support)
>
> future:
> * possible usage by HV
>
> since we already have three users and a possible fourth it seems like a
> useful change.
Another possible use is a BAT/TLB1 mapping for SoC registers (or anything
else on the board which is frequently accessed), which can be reused by
ioremap() to avoid wasting normal TLB entries, and to facilitate early
debugging.
-Scott
next prev parent reply other threads:[~2008-04-07 16:20 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 [this message]
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
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=20080407162053.GB2688@loki.buserror.net \
--to=scottwood@freescale$(echo .)com \
--cc=galak@kernel$(echo .)crashing.org \
--cc=hollisb@us$(echo .)ibm.com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=paulus@samba$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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