All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Malek <dan@mvista.com>
To: Gong Zhuo <gongzhuo@163.net>
Cc: Linux PPC Mailing List <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Any docments analyzing linuxppc kernel and it's policy?
Date: Wed, 13 Sep 2000 12:34:41 -0400	[thread overview]
Message-ID: <39BFACA1.1C6F7CAF@mvista.com> (raw)
In-Reply-To: 014301c01d7f$a1592540$4607a8c0@LocalHost


Gong Zhuo wrote:

>   I am reading the source code of linuxppc mm.

Okay.......

> ....  It seems that the process
> uses the logical address 0 - 0x7fffffff, and the kernel uses the logical
> address 0xc0000000 -- (0xc0000000 + maxium memory). The rest logical address
> will not be used by anyone. Am I right?

You got the user process part right.....The kernel will map anything
over 0x80000000 in a variety of useful and interesting ways.  The system
memory is usually mapped to 0xc0000000, the remainder of the space is
used for mapping I/O devices, other pages of memory with different
attributes (uncached for example).  This is processor/board dependent,
so there are many different mappings for this space, although we do
try to keep them somewhat consistent.

>   Is there any document analyzing the linuxppc kernel and how does the
> kernel arrange all the logical space ?

I don't know.  I do know this could change daily.....


	-- Dan

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

       reply	other threads:[~2000-09-13 16:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <014301c01d7f$a1592540$4607a8c0@LocalHost>
2000-09-13 16:34 ` Dan Malek [this message]
2000-09-13 12:27 Any docments analyzing linuxppc kernel and it's policy? Gong Zhuo
2000-09-14  0:22 ` Graham Stoney

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=39BFACA1.1C6F7CAF@mvista.com \
    --to=dan@mvista.com \
    --cc=gongzhuo@163.net \
    --cc=linuxppc-embedded@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.