From: Dan Malek <dan@mvista•com>
To: minyard@acm•org
Cc: linuxppc-dev@lists•linuxppc.org
Subject: Re: Allowing signal handlers to modify SE and BE
Date: Tue, 17 Oct 2000 00:14:12 -0400 [thread overview]
Message-ID: <39EBD214.56C034EA@mvista.com> (raw)
In-Reply-To: m2lmvoqimb.fsf@c469597-a.grlnd1.tx.home.com
Corey Minyard wrote:
> Is this really the case? I noticed in the x86 version that setting
> the equivalent of the SE bit is allowed, how does the x86 get away
> with this while the PPC can't?
These bits are optionally supported by processors. As I recall,
the 601 doesn't but I don't know of any others. You may find a
processor where they don't have any effect. I can't think of any
other reason.
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-10-17 4:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-17 2:58 Allowing signal handlers to modify SE and BE Corey Minyard
2000-10-17 4:14 ` Dan Malek [this message]
2000-10-17 8:25 ` Gabriel Paubert
2000-10-17 14:55 ` Corey Minyard
2000-10-23 18:11 ` Frank Rowand
2000-10-18 0:01 ` Paul Mackerras
2000-10-18 1:38 ` Kevin Buettner
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=39EBD214.56C034EA@mvista.com \
--to=dan@mvista$(echo .)com \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
--cc=minyard@acm$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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