From: Roland McGrath <roland@redhat.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: how to check for "optional" ppc chip features (MSR_BE)
Date: Tue, 13 May 2008 12:33:50 -0700 (PDT) [thread overview]
Message-ID: <20080513193350.8B90C26F8D4@magilla.localdomain> (raw)
In-Reply-To: Paul Mackerras's message of Tuesday, 13 May 2008 21:55:22 +1000 <18473.33194.781010.826872@cargo.ozlabs.ibm.com>
> 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?
I don't care to have userland know about it. I'm just concerned with the
arch_has_block_step() definition being right. But, you did previously tell
me that userland can set its own MSR_SE via sigreturn or setcontext or
something. If it can set its own MSR_BE the same way, then perhaps
userland wants to know.
Thanks,
Roland
next prev parent reply other threads:[~2008-05-13 19:34 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
2008-05-13 13:47 ` Kumar Gala
2008-05-13 19:33 ` Roland McGrath [this message]
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=20080513193350.8B90C26F8D4@magilla.localdomain \
--to=roland@redhat.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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