From: Frank Rowand <frank_rowand@mvista.com>
To: linuxppc-dev@lists.linuxppc.org
Cc: frowand@mvista.com
Subject: program exception emulates mfspr PVR
Date: Thu, 15 Feb 2001 14:39:17 -0800 [thread overview]
Message-ID: <3A8C5A95.9A94F914@mvista.com> (raw)
In-Reply-To: 20010215160658.P26702@altus.drgw.net
Why did emulate_instruction() get added into traps.c to emulate the
mfspr PVR instruction? What user space application is using this
instruction?
And why add this extra cruft? The information is already available to
user applications (one example, /proc/cpuinfo reports the cpu and revision).
Thanks,
Frank
--
Frank Rowand <frank_rowand@mvista.com>
MontaVista Software, Inc
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-02-15 22:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-15 22:06 calling giveup_altivec on machine with no altivec!? Troy Benjegerdes
2001-02-15 22:20 ` Frank Rowand
2001-02-15 22:33 ` Troy Benjegerdes
2001-02-15 22:47 ` Frank Rowand
2001-02-15 22:39 ` Frank Rowand [this message]
2001-02-15 22:52 ` program exception emulates mfspr PVR Dan Malek
2001-02-15 23:41 ` Mark Hatle
2001-02-15 22:57 ` calling giveup_altivec on machine with no altivec!? Dan Malek
2001-02-18 2:41 ` Troy Benjegerdes
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=3A8C5A95.9A94F914@mvista.com \
--to=frank_rowand@mvista.com \
--cc=frowand@mvista.com \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).