From: Andi Kleen <andi@firstfloor.org>
To: Marco Stornelli <marco.stornelli@gmail.com>
Cc: Andi Kleen <andi@firstfloor.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux Embedded <linux-embedded@vger.kernel.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Tim Bird <tim.bird@am.sony.com>,
linux-mm@kvack.org
Subject: Re: [PATCH 14(16] pramfs: memory protection
Date: Tue, 12 Oct 2010 09:45:22 +0200 [thread overview]
Message-ID: <20101012074522.GA20436@basil.fritz.box> (raw)
In-Reply-To: <4CB34A1A.3030003@gmail.com>
On Mon, Oct 11, 2010 at 07:32:10PM +0200, Marco Stornelli wrote:
> Il 10/10/2010 18:46, Andi Kleen ha scritto:
> > This won't work at all on x86 because you don't handle large
> > pages.
> >
> > And it doesn't work on x86-64 because the first 2GB are double
> > mapped (direct and kernel text mapping)
> >
> > Thirdly I expect it won't either on architectures that map
> > the direct mapping with special registers (like IA64 or MIPS)
>
> Andi, what do you think to use the already implemented follow_pte
> instead?
Has all the same problems. Really you need an per architecture
function. Perhaps some architectures could use a common helper,
but certainly not all.
x86 already has some infrastructure for this, but it currently
has serious problems too (like not merging mappings on unmap)
and is generally overdesigned ugly code.
-Andi
--
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:[~2010-10-12 7:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-10 16:36 [PATCH 14(16] pramfs: memory protection Marco Stornelli
2010-10-10 16:46 ` Andi Kleen
2010-10-11 6:57 ` Marco Stornelli
2010-10-11 17:32 ` Marco Stornelli
2010-10-12 7:45 ` Andi Kleen [this message]
2010-10-12 10:47 ` Marco Stornelli
2010-10-12 11:56 ` Andi Kleen
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=20101012074522.GA20436@basil.fritz.box \
--to=andi@firstfloor.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=marco.stornelli@gmail.com \
--cc=tim.bird@am.sony.com \
/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;
as well as URLs for NNTP newsgroup(s).