From: John Marvin <jsm@fc.hp.com>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: parisc-linux@lists.parisc-linux.org,
Thibaut VARENE <T-Bone@parisc-linux.org>
Subject: Re: [parisc-linux] [RFC] using 64bit wide registers with 32bit kernel
Date: Sat, 13 May 2006 23:06:59 -0600 [thread overview]
Message-ID: <4466BAF3.8060608@fc.hp.com> (raw)
In-Reply-To: <200605132335.k4DNZmAY002050@hiauly1.hia.nrc.ca>
John David Anglin wrote:
>
> I don't believe that it's impossible to support the full register width
> with a 32bit (narrow) kernel. However, hpux to my knowledge doesn't
> support 64-bit registers when using a narrow kernel. I think this
> reflects the historical development of hpux. The first PA 2.0 kernels
> were narrow and based on the 32-bit PA 1.1 implementation. Wide kernels
> were introduced with HP-UX 11.
>
You are correct.
If you are running a 32 bit version of hpux on a 64 bit machine then the
upper halfs of registers are not saved. I will note that there are not
many (and may no longer be any) 64 bit machines that HP supports running
a 32 bit kernel on.
If you are running a 64 bit version of hpux then the upper halfs of
registers are saved during context switches, even if you are running a
32 bit app. It gets interesting in a signal handler, since the registers
are saved in the signal context twice, i.e. the 32 bit lower halfs are
saved in one place (for backwards object compatibility), and then the 64
bit versions are saved in another. I forget all the details about what
happens if you want to change the saved value in the signal context.
John
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2006-05-14 5:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-13 15:41 [parisc-linux] [RFC] using 64bit wide registers with 32bit kernel Thibaut VARENE
2006-05-13 16:33 ` [parisc-linux] " Thibaut VARENE
2006-05-13 17:03 ` [parisc-linux] " James Bottomley
2006-05-13 22:32 ` Thibaut VARENE
[not found] ` <yq0ves7psaw.fsf@jaguar.mkp.net>
[not found] ` <7d01f9f00605150255u5846f144u9c95cab3ffd35133@mail.gmail.com>
2006-05-15 10:56 ` Jes Sorensen
2006-05-15 11:53 ` Kyle McMartin
2006-05-13 17:07 ` John David Anglin
2006-05-13 22:43 ` Thibaut VARENE
2006-05-13 23:35 ` John David Anglin
2006-05-14 5:06 ` John Marvin [this message]
2006-05-14 6:27 ` Grant Grundler
[not found] ` <200605141510.k4EFAUv7006350@hiauly1.hia.nrc.ca>
2006-05-15 1:06 ` Grant Grundler
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=4466BAF3.8060608@fc.hp.com \
--to=jsm@fc.hp.com \
--cc=T-Bone@parisc-linux.org \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=parisc-linux@lists.parisc-linux.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