From: Frank Rowand <frank_rowand@hp.com>
To: Philipp Rumpf <Philipp.H.Rumpf@mathe.stud.uni-erlangen.de>
Cc: Stan Sieler <sieler@allegro.com>, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] depi?
Date: Wed, 17 Nov 1999 16:43:17 -0800 [thread overview]
Message-ID: <38334BA5.BAA898D@hp.com> (raw)
In-Reply-To: 19991118010930.G10209@mathe.stud.uni-erlangen.de
Philipp Rumpf wrote:
>
> > I must be missing something...the above should branch
> > to: sr7.0xc008dbc0, not to "0xc008dbc0". I.e., you specified SR7
> > in the BE instruction, so it gets used.
>
> No, we didn't. We set the space register selection field to '00' which
> according to the documentation means you select SR7 but in reality means
> you don't want to have anything to do with space registers. Just think
> of it as flat address 0xc008dbc0 and of SR[123]:0xc008dbc0 as "real"
> segmented addresses.
When address translation is enabled, a space register is *always* used.
You cannot turn that off. Specifying '00' in the space register
select bits really does mean that you use space register 7 to calculate
the 64 bit virtual address. (Humor me, and pretend that all
implementations of space registers are 32 bits, even though they aren't.)
If you "don't want to have anything to do with space registers", you
can put the same value (such as zero) in all of the space registers.
> > So, SR7 indeed needs to be set correctly...but since I haven't
> > looked at the surrounding code...
>
> SR0, SR4, SR5, SR6, SR7 shouldn't ever need to be set to different values
> for flat 4 gig code. SR1, SR2, SR3 you use only for "real" segmented code.
>
> (This is based on what the C compiler does, and what changed with PA2.0)
>
> Philipp Rumpf
I don't understand. Are you saying that there is a single 4gByte virtual
address range that is shared by the kernel and all user processes? Or
do you plan to provide a separate 4gByte virtual address range to each
process/task/thread/whatever?
-Frank
next prev parent reply other threads:[~1999-11-18 0:41 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-15 8:08 [parisc-linux] depi? Alex deVries
1999-11-15 7:24 ` Jeffrey A Law
1999-11-15 7:36 ` Stan Sieler
1999-11-15 8:25 ` Philipp Rumpf
1999-11-15 23:14 ` Frank Rowand
1999-11-16 0:26 ` John David Anglin
1999-11-16 12:39 ` Matthew Wilcox
1999-11-16 17:17 ` Philipp Rumpf
1999-11-16 8:26 ` Philippe Benard
1999-11-16 12:20 ` Alan Cox
1999-11-16 11:53 ` Philippe Benard
1999-11-16 12:58 ` Alan Cox
1999-11-16 15:55 ` John David Anglin
1999-11-17 13:00 ` Philipp Rumpf
1999-11-16 12:35 ` Matthew Wilcox
1999-11-16 16:08 ` Philipp Rumpf
1999-11-16 17:14 ` Alan Cox
1999-11-16 16:47 ` Philipp Rumpf
1999-11-16 17:50 ` Alan Cox
1999-11-17 0:06 ` Grant Grundler
1999-11-17 6:21 ` Philipp Rumpf
1999-11-17 18:57 ` Stan Sieler
1999-11-17 19:29 ` Philipp Rumpf
1999-11-17 20:01 ` Stan Sieler
1999-11-17 20:33 ` Philipp Rumpf
1999-11-16 21:43 ` Frank Rowand
1999-11-17 6:12 ` Philipp Rumpf
1999-11-17 18:56 ` Frank Rowand
1999-11-17 22:05 ` Philipp Rumpf
1999-11-17 22:39 ` John David Anglin
1999-11-17 22:52 ` Philipp Rumpf
1999-11-17 23:37 ` Stan Sieler
1999-11-18 0:09 ` Philipp Rumpf
1999-11-18 0:43 ` Frank Rowand [this message]
1999-11-18 1:35 ` Frank Rowand
1999-11-18 5:33 ` John David Anglin
1999-11-18 8:02 ` Philippe Benard
1999-11-18 20:37 ` John David Anglin
1999-11-18 22:38 ` Frank Rowand
1999-11-19 4:12 ` Philipp Rumpf
1999-11-19 9:08 ` Philippe Benard
1999-11-17 23:02 ` Frank Rowand
1999-11-17 23:25 ` Philipp Rumpf
1999-11-17 8:14 ` Philippe Benard
1999-11-15 8:19 ` Philipp Rumpf
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=38334BA5.BAA898D@hp.com \
--to=frank_rowand@hp.com \
--cc=Philipp.H.Rumpf@mathe.stud.uni-erlangen.de \
--cc=frowand@cup.hp.com \
--cc=parisc-linux@thepuffingroup.com \
--cc=sieler@allegro.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