Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Mike Shaver <shaver@netscape.com>
To: hppa-linux@thepuffingroup.com
Subject: Re: [hppa-linux] memory layout
Date: Thu, 18 Mar 1999 00:55:53 -0500	[thread overview]
Message-ID: <36F09569.F609A7B3@netscape.com> (raw)
In-Reply-To: Pine.LNX.3.96.990317212138.2685A-100000@quark.ix.netcom.com

Kumar wrote:
> 
> Talking about only pa1.1 or 32 bit CPUs, I would say the same layout
> can be used as Linux on Intel does. That is kernel mapped at 0xc0000000.
> So 3 Gig for User space and 1 Gig for kernel. Of course, other ppl may
> have different ideas.

OpenBSD has the same idea, it seems.  From
sys/arch/hppa/include/vmparam.h:

/* user/kernel map constants */
#define VM_MIN_ADDRESS          ((vm_offset_t)0)
#define VM_MAXUSER_ADDRESS      ((vm_offset_t)0xc0000000)
#define VM_MAX_ADDRESS          VM_MAXUSER_ADDRESS
#define VM_MIN_KERNEL_ADDRESS   ((vm_offset_t)0)
#define VM_MAX_KERNEL_ADDRESS   ((vm_offset_t)0xF0000000)

I'll start filling in the x86 numbers blindly, I guess.

> PA has this strange concept of Spaces and they have those
> space registers %sr0 to %sr7. This reminds me of Intel's segment
> registers. And whoever wanted to do any serious OS like Unix on 80386
> never liked segments.

Yeah, I've been trying to figure out whether we should do anything
special with those, but I don't quite understand the whole architecture
yet.

Mike

-- 
311774.80 264634.54

  reply	other threads:[~1999-03-18  5:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-18  4:11 [hppa-linux] memory layout Mike Shaver
1999-03-18  5:29 ` Kumar
1999-03-18  5:55   ` Mike Shaver [this message]
1999-03-18 10:24   ` Alan Cox
1999-03-18 19:10     ` Mike Shaver
1999-03-19 18:53       ` Michael Shalayeff

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=36F09569.F609A7B3@netscape.com \
    --to=shaver@netscape.com \
    --cc=hppa-linux@thepuffingroup.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