linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@mvista.com>
To: Okehee Goh <ogoh@asu.edu>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: MMU in MBX860
Date: Thu, 25 Oct 2001 00:01:12 -0400	[thread overview]
Message-ID: <3BD78E88.90337302@mvista.com> (raw)
In-Reply-To: CPEELCODKANPCLBCAGOFKEBKCAAA.ogoh@asu.edu


Okehee Goh wrote:

>  My question:
>  In MPC860, is there any way for supervisor mode's kernel to access all
> memory space

That's the purpose of the SHARED indicator in the TLB.  It effectively
disables ASID checking and if you mark pages SHARED but not user access
the kernel can access all pages while the applications are still protected.


	-- Dan

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-10-25  4:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-24 22:46 MMU in MBX860 Okehee Goh
2001-10-25  4:01 ` Dan Malek [this message]
2001-10-25  4:51   ` Okehee Goh
2001-10-25 15:19     ` Dan Malek
2001-10-25 15:45       ` 405GP Dhrystone Benchmark ibm405.linux
2001-10-25 16:26         ` Mark Hatle

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=3BD78E88.90337302@mvista.com \
    --to=dan@mvista.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=ogoh@asu.edu \
    /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).