public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: dhowells@redhat.com, linux-kernel@vger.kernel.org,
	uclinux-dist-devel@blackfin.uclinux.org,
	Bernd Schmidt <bernds_cb1@t-online.de>,
	Bryan Wu <cooloney@kernel.org>
Subject: Re: [PATCH v2] NOMMU: add support for Memory Protection Units (MPU)
Date: Tue, 14 Jul 2009 18:22:06 +0100	[thread overview]
Message-ID: <6206.1247592126@redhat.com> (raw)
In-Reply-To: <1247591665-12000-1-git-send-email-vapier@gentoo.org>

Mike Frysinger <vapier@gentoo.org> wrote:

> Some architectures (like the Blackfin arch) implement some of the
> "simpler" features that one would expect out of a MMU such as memory
> protection.  In our case, we actually get read/write/exec protection
> down to the page boundary so processes can't stomp on each other let
> alone the kernel.  There is a performance decrease (which depends greatly
> on the workload) however as the hardware/software interaction was not
> optimized at design time.

It occurs to me that I could probably test this on FRV by using the MMU in a
limited way.  How do you actually keep track of the protections applied?  Do
you have a single global page table that is managed by the mmap code on a
per-VMA basis?

David

  reply	other threads:[~2009-07-14 17:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-14 14:22 [PATCH] NOMMU: add support for Memory Protection Units (MPU) Mike Frysinger
2009-07-14 16:14 ` Johannes Weiner
2009-07-14 16:19   ` Mike Frysinger
2009-07-14 17:14   ` [PATCH v2] " Mike Frysinger
2009-07-14 17:22     ` David Howells [this message]
2009-07-14 21:59       ` Bernd Schmidt
2009-07-15 10:31         ` David Howells
2009-07-15 11:18           ` [Uclinux-dist-devel] " Mike Frysinger
2009-07-15 10:37         ` David Howells
2009-07-15 11:12           ` [Uclinux-dist-devel] " Mike Frysinger
2009-07-15 11:45             ` David Howells
2009-07-15 11:55               ` Mike Frysinger
2009-07-15 12:25                 ` David Howells
2009-07-15 12:52                   ` Mike Frysinger
2009-07-15  9:24       ` Paul Mundt
2009-09-14  3:52     ` Mike Frysinger
2009-09-16 10:09       ` David Howells
2009-09-16 13:57 ` [PATCH] " Mike Frysinger

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=6206.1247592126@redhat.com \
    --to=dhowells@redhat.com \
    --cc=bernds_cb1@t-online.de \
    --cc=cooloney@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=uclinux-dist-devel@blackfin.uclinux.org \
    --cc=vapier@gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox