kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: dhylands@gmail.com (Dave Hylands)
To: kernelnewbies@lists.kernelnewbies.org
Subject: VMA of processes and CPU registers
Date: Wed, 20 Apr 2011 18:22:29 -0700	[thread overview]
Message-ID: <BANLkTikxhBA_5pbzMOTxbnhDo-o2dJ+TLQ@mail.gmail.com> (raw)
In-Reply-To: <201104202338.00339.mindentropy@gmail.com>

Hi,

On Wed, Apr 20, 2011 at 11:08 AM, mindentropy <mindentropy@gmail.com> wrote:
> On Wednesday 20 Apr 2011 11:00:17 pm Dave Hylands wrote:
>
>> I think that this is true for all of the architectures I've worked
>> with (ARM, MIPS, x86). Some architectures (like MIPS) have a
>> combination of spaces which are linearly mapped between virtual and
>> physical, and mapped spaces (which go through an MMU).
>
> Is this just identity mapping or does it bypass the paging unit for some
> addresses? Just out of curiosity how do you tell the bypassing info?

On the MIPS core I was working with (which I think was R3000 based),
they use the upper 2 or 3 bits of the address to determine the type of
access.

This page has the details (the table about 1/3 of the way down the web page):
<http://tams-www.informatik.uni-hamburg.de/applets/hades/webdemos/mips.html>

-- 
Dave Hylands
Shuswap, BC, Canada
http://www.davehylands.com

  reply	other threads:[~2011-04-21  1:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-19 22:56 VMA of processes and CPU registers limp
2011-04-19 23:20 ` Dave Hylands
2011-04-20 11:01   ` limp
2011-04-20 16:03     ` mindentropy
2011-04-25  8:55       ` Prabhu nath
2011-04-25 16:38         ` mindentropy
2011-04-27  4:33           ` Prabhu nath
2011-04-27  4:48             ` Mulyadi Santosa
2011-04-27 18:30             ` mindentropy
2011-04-20 17:30     ` Dave Hylands
2011-04-20 18:08       ` mindentropy
2011-04-21  1:22         ` Dave Hylands [this message]
2011-04-21 19:54           ` mindentropy

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=BANLkTikxhBA_5pbzMOTxbnhDo-o2dJ+TLQ@mail.gmail.com \
    --to=dhylands@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).