From: gdavis@mvista.com (George G. Davis)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] Prohibit ioremap() on kernel managed RAM
Date: Wed, 5 May 2010 12:33:13 -0400 [thread overview]
Message-ID: <20100505163313.GC3169@mvista.com> (raw)
In-Reply-To: <20100505163012.GA17678@n2100.arm.linux.org.uk>
Hi,
On Wed, May 05, 2010 at 05:30:12PM +0100, Russell King - ARM Linux wrote:
> On Wed, May 05, 2010 at 12:23:45PM -0400, George G. Davis wrote:
> > So could we similarly we relax this "Prohibit ioremap() on kernel managed
> > RAM" change for reserved pages? Like so:
> >
> > /*
> > * Don't allow RAM to be mapped - this causes problems with ARMv6+
> > */
> > if (WARN_ON(pfn_valid(pfn) && !PageReserved(pfn_to_page(pfn)))
> > return NULL;
> >
>
> Only once the rest of the solution gets implemented; making this change
> on its own doesn't mean very much or have very much effect.
That's fine, I'm just (trying ; ) to think ahead.
Thanks!
--
Regards,
George
next prev parent reply other threads:[~2010-05-05 16:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 14:40 [RFC] Prohibit ioremap() on kernel managed RAM Russell King
2010-04-30 16:33 ` 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 [this message]
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=20100505163313.GC3169@mvista.com \
--to=gdavis@mvista.com \
--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.