Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Pete Popov <ppopov@pacbell.net>
To: sjhill@cotw.com
Cc: Hartvig Ekner <hartvige@mips.com>, linux-mips <linux-mips@oss.sgi.com>
Subject: Re: What is the maximum physical RAM for a 32bit MIPS core?
Date: 05 Feb 2002 13:15:09 -0800	[thread overview]
Message-ID: <1012943709.10659.106.camel@zeus> (raw)
In-Reply-To: <3C6044A7.13FEB2E2@cotw.com>

On Tue, 2002-02-05 at 12:46, Steven J. Hill wrote:
> Hartvig Ekner wrote:
> > 
> > You have to distinguish between physical and virtual memory. The MIPS32
> > architecture supports implementations with up to 36 bits of physical
> > address space, however the virtual address space in kernel and user mode
> > is as you describe below.
> > 
> I wasn't talking about the MIP32[tm] cores specifically, I was using a
> generalization of 32bit. However, this is good to know. All of the data
> sheets that I just downloaded from the MIPS site for the R4k[X] cores
> don't mention the 36-bit PA item. Care to elaborate?
> 
> > One note: Many MIPS32 implementations choose not to implement all 36 PA
> > bits, but limit themselves to 32 bits. This saves a few bits in the TLB
> > and a few address lines.
> > 
> So, if someone did want 36 PA bits on Linux, the TLB exception handlers
> and a little of the page table construction/management code would have to
> change. The userspace contraints and such would still remain. Cool.

I'm not sure if it's a "little" though.  Ralf has already done the work
for 64bit memory support on 32bit kernels, but that only works currently
on 64bit CPUs.  I started hacking on the 64bit memory patch to get it to
work on 32bit processors, but had to put that aside for a few weeks. I
hope to get back to it soon.

Pete

  parent reply	other threads:[~2002-02-05 21:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-05 16:50 What is the maximum physical RAM for a 32bit MIPS core? Steven J. Hill
2002-02-05 17:47 ` Hartvig Ekner
2002-02-05 20:46   ` Steven J. Hill
2002-02-05 20:53     ` Hartvig Ekner
2002-02-05 20:53       ` Hartvig Ekner
2002-02-05 21:15     ` Pete Popov [this message]
2002-02-05 21:24       ` Steven J. Hill
2002-02-05 21:44         ` Pete Popov
2002-02-05 21:58         ` Bradley D. LaRonde
2002-02-05 21:58           ` Bradley D. LaRonde
2002-02-06  8:49           ` Geert Uytterhoeven
2002-02-06 11:16             ` nick
2002-02-06 12:07               ` Geert Uytterhoeven
2002-02-06 14:14             ` Bradley D. LaRonde
2002-02-06 14:14               ` Bradley D. LaRonde
2002-02-06  5:29     ` Ralf Baechle
2002-02-06  2:33 ` Ralf Baechle
2002-02-06 13:17   ` William Lee Irwin III

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=1012943709.10659.106.camel@zeus \
    --to=ppopov@pacbell.net \
    --cc=hartvige@mips.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=sjhill@cotw.com \
    /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