From: Grant Grundler <grundler@parisc-linux.org>
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: Sun, 14 May 2006 00:27:17 -0600 [thread overview]
Message-ID: <20060514062717.GA25973@colo.lackof.org> (raw)
In-Reply-To: <200605132335.k4DNZmAY002050@hiauly1.hia.nrc.ca>
On Sat, May 13, 2006 at 07:35:48PM -0400, John David Anglin wrote:
> > Are you trying to say that userspace code shouldn't be using the full
> > registers width when running a 32bit (narrow) kernel?
>
> 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 believe later 10.20 updates/patches to support PA2.0 processors did
in fact support saving/restoring 64-bits. But it's been a _long_
time since I've look at that.
> 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.
Correct. Mostly in the form of 10.20 patches.
> Wide kernels were introduced with HP-UX 11.
Trivia: 10.30 was a T600/customer specific release that
provided 64-bit support before 11.00 was ready.
...
> Personally, I think the wide register support is most important
> when running a 64-bit kernel and that's the place it would be
> easiest to implement. I can see that there are situations where
> it would be nice to use 64-bit registers on a narrow kernel but
> this would change the size of register files, the context passed
> to signal handlers, etc.
Oh..good point. I'm really not willing to tolerate an ABI event
for this kind of perf optimization. I'd much rather start advocating
use of 64-bit kernels in order to enable use of MAX insns.
Until HP 24-bit color gfx PCI cards work on pa2.0, I don't
see a good reason to implement this. Maybe 8-bit color with
a private color map is sufficient...
thanks,
grant
grant
_______________________________________________
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 6:27 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
2006-05-14 6:27 ` Grant Grundler [this message]
[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=20060514062717.GA25973@colo.lackof.org \
--to=grundler@parisc-linux.org \
--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