From: Paul Mackerras <paulus@samba.org>
To: Roland McGrath <roland@redhat.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: how to check for "optional" ppc chip features (MSR_BE)
Date: Tue, 13 May 2008 21:55:22 +1000 [thread overview]
Message-ID: <18473.33194.781010.826872@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20080504231207.8377E26FA08@magilla.localdomain>
Roland McGrath writes:
> Yeah, all that stuff I could figure out as needed. What I really meant
> was, where is the big official table of which chips behave which ways that
> you base all code that on? Actually, I don't really care as long as you
> all are happy to be responsible for figuring out what matters. With the
> patch I posted to use MSR_BE, I took Kumar Gala's word as gospel that all
> the chips on which we use MSR_SE also have MSR_BE. If that's not right,
> then I hope you'd like to pick a feature bit, populate the tables, etc.,
> and fix the definition of arch_has_block_step() as appropriate.
It turns out that the 601 doesn't support MSR_BE. It looks like all
the "classic" 32-bit implementations after that (603, 604, 7xx, 7xxx)
implemented BE, as do POWER3 and RS64. I'll check the later 64-bit
processors -- I think they all implement BE. 4xx and Book E have it
in a different form. I'll let Kumar find out about 8xx and 82xx.
So it looks like we need to define a new feature bit to mean "supports
block-step". Is this something that userspace will expect to be told
about via the AT_HWCAP entry in the aux vector?
Paul.
next prev parent reply other threads:[~2008-05-13 11:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 1:21 how to check for "optional" ppc chip features (MSR_BE) Roland McGrath
2008-05-02 3:48 ` Kumar Gala
2008-05-04 21:45 ` Benjamin Herrenschmidt
2008-05-04 23:12 ` Roland McGrath
2008-05-05 0:49 ` Benjamin Herrenschmidt
2008-05-13 11:55 ` Paul Mackerras [this message]
2008-05-13 13:47 ` Kumar Gala
2008-05-13 19:33 ` Roland McGrath
2008-06-11 16:05 ` Kumar Gala
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=18473.33194.781010.826872@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=roland@redhat.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;
as well as URLs for NNTP newsgroup(s).