From: "Mike Frysinger" <vapier.adi@gmail.com>
To: "David Howells" <dhowells@redhat.com>
Cc: "Pekka J Enberg" <penberg@cs.helsinki.fi>,
"Andrew Morton" <akpm@linux-foundation.org>,
bryan.wu@analog.com, linux-kernel@vger.kernel.org,
"Hugh Dickins" <hugh@veritas.com>,
"Alan Cox" <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH -mm] Revoke core code: fix nommu arch compiling error bug
Date: Mon, 26 Mar 2007 16:21:51 -0400 [thread overview]
Message-ID: <8bd0f97a0703261321h356a849am1ab617f0e732fa67@mail.gmail.com> (raw)
In-Reply-To: <22674.1174915478@redhat.com>
On 3/26/07, David Howells <dhowells@redhat.com> wrote:
> [*] The FRV, for example, does have some limited protection capability - but
> it is really limited and not really useful in this case.
how so ? the Blackfin processor lacks a MMU but it does have a MPU
(memory protection unit) which allows granularity down to 1k page
sizes ... so for future releases, we plan on integrating optional
support for this so that you could have processes protected from each
other and the kernel protected from all the processes ... so in our
case, we might actually be able to support revoking of maps because we
would have that region of memory ear marked as unaccessible ...
note that the Blackfin processor manuals confusingly call this aspect
of the chip an "MMU" ... dont be fooled !
-mike
next prev parent reply other threads:[~2007-03-26 20:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 10:23 Wu, Bryan
2007-03-26 10:37 ` Pekka J Enberg
2007-03-26 10:41 ` Andrew Morton
2007-03-26 11:25 ` David Howells
2007-03-26 11:30 ` Pekka J Enberg
2007-03-26 11:44 ` David Howells
2007-03-26 11:55 ` Pekka J Enberg
2007-03-26 12:22 ` David Howells
2007-03-26 12:37 ` Pekka J Enberg
2007-03-26 13:24 ` David Howells
2007-03-26 20:21 ` Mike Frysinger [this message]
2007-03-27 3:29 ` Wu, Bryan
2007-03-27 6:57 ` Pekka J Enberg
2007-03-27 7:20 ` Mike Frysinger
2007-03-27 10:05 ` David Howells
2007-03-27 17:00 ` Mike Frysinger
2007-03-27 19:06 ` David Howells
2007-03-26 13:03 ` Alan Cox
2007-03-26 11:50 ` Andrew Morton
2007-03-26 11:58 ` David Howells
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=8bd0f97a0703261321h356a849am1ab617f0e732fa67@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bryan.wu@analog.com \
--cc=dhowells@redhat.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/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
all inboxes | Powered by JetHome®