From: David Edelsohn <dje@watson.ibm.com>
To: Holger Bettag <hobold@informatik.uni-bremen.de>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Apple Job Posting and Good News for LinuxPPC developers
Date: Fri, 02 Apr 1999 12:11:12 -0500 [thread overview]
Message-ID: <9904021711.AA35268@marc.watson.ibm.com> (raw)
In-Reply-To: Message from Holger Bettag <hobold@informatik.uni-bremen.de> of "02 Apr 1999 14:11:16 +0200." <8x677fp6hn.fsf@s52.informatik.uni-bremen.de>
>>>>> Holger Bettag writes:
Holger> I have heard rumours that the "Max" core has provisions to physically address
Holger> more than 4GB of memory (via the MMU's segment registers). Processes would
Holger> still be limited to a 4GB logical address space, though.
The PowerPC architecture always has been able to address more than
32-bits of "logical" address space. That is the reason for the PowerPC
terminology of "effective address", "virtual address", and "real address".
The intermediate "virtual address" space of a 32-bit PowerPC
implementation is 52 bits.
Pointers still are 32-bits, but a cooperating operating system and
compiler can allow an application to address more virtual memory through
runtime modifications to the virtual segments mapped by the segment
registers, like memory overlays. That was the original reason for the
design of the MMU in the POWER (predecessor of PowerPC) architecture. I
do not believe that any compiler / OS combination takes advantage of this
facility.
David
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-04-02 17:11 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-14 13:35 Blue G3 and machine check Benjamin Herrenschmidt
1999-03-15 16:42 ` Ryuichi Oikawa
1999-03-15 17:09 ` Geert Uytterhoeven
1999-03-24 9:30 ` Gabriel Paubert
1999-03-24 23:12 ` Paul Mackerras
1999-03-25 11:20 ` Gabriel Paubert
1999-03-25 16:46 ` Apple Job Posting and Good News for LinuxPPC developers Kevin B. Hendricks
1999-03-25 19:12 ` David Edelsohn
1999-03-26 11:31 ` Gabriel Paubert
1999-03-26 16:13 ` David Edelsohn
1999-03-27 6:27 ` Guy Sotomayor
1999-03-27 20:44 ` David Edelsohn
1999-04-02 12:11 ` Holger Bettag
1999-04-02 17:11 ` David Edelsohn [this message]
1999-04-02 22:19 ` Douglas Godfrey
1999-04-03 17:42 ` Holger Bettag
1999-04-05 16:11 ` Gabriel Paubert
1999-04-05 16:06 ` Gabriel Paubert
1999-04-06 5:53 ` Douglas Godfrey
1999-03-26 6:08 ` Nathan Hurst
1999-03-26 13:51 ` sean o'malley
1999-03-28 5:08 ` Cort Dougan
1999-03-26 20:33 ` N.G. Temme
1999-03-29 23:44 ` Blue G3 and machine check Paul Mackerras
1999-03-30 11:41 ` Gabriel Paubert
1999-03-31 16:20 ` Ryuichi Oikawa
1999-03-31 18:39 ` Gabriel Paubert
1999-04-05 16:36 ` Ryuichi Oikawa
1999-04-05 17:11 ` Gabriel Paubert
1999-04-04 1:17 ` Joel Klecker
1999-04-09 5:58 ` Joel Klecker
1999-04-09 16:12 ` Ryuichi Oikawa
1999-03-25 12:10 ` Benjamin Herrenschmidt
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=9904021711.AA35268@marc.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=hobold@informatik.uni-bremen.de \
--cc=linuxppc-dev@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 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).