From: Arnd Bergmann <arnd@arndb.de>
To: Leif Lindholm <leif.lindholm@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org, nico@linaro.org,
patches@linaro.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org,
"Russell King - ARM Linux" <linux@arm.linux.org.uk>
Subject: Re: [PATCH 0/2] arm: add early_ioremap() support
Date: Wed, 26 Jun 2013 23:23:50 +0200 [thread overview]
Message-ID: <201306262323.50691.arnd@arndb.de> (raw)
In-Reply-To: <20130626192352.GE9078@rocoto.smurfnet.nu>
On Wednesday 26 June 2013, Leif Lindholm wrote:
> On Wed, Jun 26, 2013 at 08:52:09PM +0200, Arnd Bergmann wrote:
> > I made a similar suggestion to extending the use of fixmap recently, see
> > "Re: SCU registers mapping for CA9/CA5 cores". Russell pointed out that
> > fixmap is intentionally limited to just kmap_atomic uses at the moment
> > and changing that would potentially have a significant impact when we
> > run out of pages in the fixmap area.
>
> Is this an issue here, since (unlike x86) this early_ioremap only works
> before paging_init()?
The main problem is that the total fixmap size is only around 900kb,
and we want to reserve at least 64kb per cpu for kmap_atomic.
If you want to fit multiple 128kb mappings in there, you run out of
space really fast.
> > Extending the iotable mechanism on ARM would be the convenient
> > solution for us I think.
>
> Could that easily be extended to give similar semantics sufficiently
> that we can progress with merging more of the UEFI and ACPI support
> together as common code with x86/ia64?
I don't know what the requirements are, but the idea with iotable
is that the mappings stay around at run time, while it seems you want
to discard them at some point.
Arnd
next prev parent reply other threads:[~2013-06-26 21:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 17:46 [PATCH 0/2] arm: add early_ioremap() support Leif Lindholm
2013-06-25 17:46 ` [PATCH 1/2] Documentation: arm: early_ioremap Leif Lindholm
2013-06-30 3:14 ` Rob Landley
2013-06-25 17:46 ` [PATCH 2/2] arm: add early_ioremap support Leif Lindholm
2013-06-26 18:52 ` [PATCH 0/2] arm: add early_ioremap() support Arnd Bergmann
2013-06-26 19:23 ` Leif Lindholm
2013-06-26 21:23 ` Arnd Bergmann [this message]
2013-06-26 21:34 ` Leif Lindholm
2013-06-26 22:13 ` Arnd Bergmann
2013-06-26 23:25 ` Leif Lindholm
2013-06-27 8:47 ` Arnd Bergmann
2013-06-27 9:29 ` Leif Lindholm
2013-06-27 11:55 ` Arnd Bergmann
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=201306262323.50691.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=leif.lindholm@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nico@linaro.org \
--cc=patches@linaro.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