From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jared Hulbert <jaredeh@gmail.com>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [RFC] Changing VM_PFNMAP assumptions and rules
Date: Tue, 13 Nov 2007 11:24:33 +1100 [thread overview]
Message-ID: <1194913473.18185.80.camel@pasglop> (raw)
In-Reply-To: <6934efce0711121553s6b88d1qe48b19adee1b7a85@mail.gmail.com>
On Mon, 2007-11-12 at 15:53 -0800, Jared Hulbert wrote:
> > > I have a page that is at a hardware level read-only. What kind of
> > > rules can that page live under? More importantly these PFN's get
> > > mapped in with a call to ioremap() in the mtd drivers. So once I
> > > figure out how to SPARSE_MEM, hotplug these pages in I've got to
> hack
> > > the MTD to work with real pages. Or something like that. I'm not
> > > ready to take that on yet, I just don't understand it all enough
> yet.
> >
> > I think vm_normal_page() could use something like pfn_normal() which
> > isn't quite the same as pfn_valid()... or just use pfn_valid() but
> in
> > that case, that would mean removing a bunch of the BUG_ON's indeed.
>
> That's exactly what my original patch does. Would my patch break
> spufs? Nick said my patch would break /dev/mem I think.
I missed your original patch. Can you resend it to me ? Nick, how would
it break /dev/mem ?
Cheers,
Ben.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-11-13 0:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 19:15 Jared Hulbert
2007-11-11 0:09 ` Nick Piggin
2007-11-12 22:03 ` Jared Hulbert
2007-11-12 22:29 ` Benjamin Herrenschmidt
2007-11-12 23:53 ` Jared Hulbert
2007-11-13 0:24 ` Benjamin Herrenschmidt [this message]
2007-11-13 12:08 ` Nick Piggin
2007-11-14 1:29 ` Jared Hulbert
2007-11-13 17:26 ` Nick Piggin
2007-11-14 18:52 ` Jared Hulbert
2007-11-16 23:42 ` Jared Hulbert
2007-11-19 0:17 ` Nick Piggin
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=1194913473.18185.80.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=jaredeh@gmail.com \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
/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