All of lore.kernel.org
 help / color / mirror / Atom feed
From: rmk@ftp.linux.org.uk (Russell King)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] Prohibit ioremap() on kernel managed RAM
Date: Fri, 23 Apr 2010 15:40:58 +0100	[thread overview]
Message-ID: <20100423144058.GA11637@ZenIV.linux.org.uk> (raw)

> Above change is necessary but what an alternative approach is for this. 
> There are many use case where ioremap* is needed.

This is a very difficult issue to answer; the only way we can safely
remap RAM with different attributes is if we disable the existing
mappings - but since we create those with 1MB sections, that's far
from easy to achieve.

I think a viable safe solution is to set aside some RAM at boot (which
the kernel doesn't manage at all) and then use ioremap on that; that
approach will still work with this patch in place.

Note that I've applied this patch to my devel tree, which has been
pushed out; please note that I'm making use of others 'net connections
to do this.

             reply	other threads:[~2010-04-23 14:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-23 14:40 Russell King [this message]
2010-04-30 16:33 ` [RFC] Prohibit ioremap() on kernel managed RAM George G. Davis
2010-04-30 16:38   ` Catalin Marinas
2010-05-01  6:24     ` Shilimkar, Santosh
2010-05-01  9:19       ` Russell King - ARM Linux
2010-05-03 15:59     ` George G. Davis
2010-05-04 15:29       ` Catalin Marinas
2010-05-05 16:23         ` George G. Davis
2010-05-05 16:30           ` Russell King - ARM Linux
2010-05-05 16:33             ` George G. Davis
2010-04-30 18:19   ` Russell King - ARM Linux
2010-04-30 22:30     ` George G. Davis
  -- strict thread matches above, loose matches on Subject: below --
2010-04-08  9:48 Russell King - ARM Linux
2010-04-23 14:15 ` Catalin Marinas
2010-04-23 14:27   ` Shilimkar, Santosh

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=20100423144058.GA11637@ZenIV.linux.org.uk \
    --to=rmk@ftp.linux.org.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.