From: Mike Frysinger <vapier.adi@gmail.com>
To: David Howells <dhowells@redhat.com>
Cc: Bernd Schmidt <bernds_cb1@t-online.de>,
uclinux-dist-devel@blackfin.uclinux.org,
linux-kernel@vger.kernel.org
Subject: Re: [Uclinux-dist-devel] [PATCH v2] NOMMU: add support for Memory Protection Units (MPU)
Date: Wed, 15 Jul 2009 07:18:40 -0400 [thread overview]
Message-ID: <8bd0f97a0907150418x5190c8e2o31bee10533478372@mail.gmail.com> (raw)
In-Reply-To: <12331.1247653900@redhat.com>
On Wed, Jul 15, 2009 at 06:31, David Howells wrote:
> Bernd Schmidt wrote:
>> No page table, just three bitmaps (r/w/x), with one bit per page, per mm.
>
> That sounds a bit inefficient as you have to make three accesses per page. I
> suppose it depends on how your MPU works.
there isnt any hardware assistance in terms of speeding up misses.
they're treated like any other hardware exception. it does
differentiate between inst and data misses though, so the software
replacement algorithm doesnt have to check all three.
the code for handling CPLB (effectively the same thing as a TLB for
this discussion) is contained in
arch/blackfin/kernel/cplb-mpu/cplbmgr.c. it's a pretty small file --
the entry point is cplb_hdr() and that calls the relevant function to
handle inst or data misses.
-mike
next prev parent reply other threads:[~2009-07-15 11:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 14:22 [PATCH] " 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-09-14 3:52 ` Mike Frysinger
2009-09-16 10:09 ` David Howells
2009-07-14 17:22 ` David Howells
2009-07-14 21:59 ` Bernd Schmidt
2009-07-15 9:24 ` Paul Mundt
2009-07-15 10:31 ` David Howells
2009-07-15 11:18 ` Mike Frysinger [this message]
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-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=8bd0f97a0907150418x5190c8e2o31bee10533478372@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=bernds_cb1@t-online.de \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=uclinux-dist-devel@blackfin.uclinux.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
all inboxes | Powered by JetHome®