From: Jason R Thorpe <thorpej@wasabisystems.com>
To: Kumar Gala <kumar.gala@motorola.com>
Cc: linuxppc-dev@lists.linuxppc.org,
Daniel Jacobowitz <drow@mvista.com>,
Kevin Buettner <kevinb@redhat.com>,
gdb@sources.redhat.com, ezannoni@cygnus.com,
fsirl@kernel.crashing.org, paulus@samba.org
Subject: Re: AltiVec register ptrace support
Date: Fri, 14 Dec 2001 11:17:00 -0000 [thread overview]
Message-ID: <20011214111620.U9607@dr-evil.shagadelic.org> (raw)
In-Reply-To: <Pine.GSO.4.40.0112141249070.21737-100000@softail.somerset.sps.mot.com>; from kumar.gala@motorola.com on Fri, Dec 14, 2001 at 12:52:33PM -0600
On Fri, Dec 14, 2001 at 12:52:33PM -0600, Kumar Gala wrote:
> Is there any reason that we can not spport both methods. There are
> applications in which having the ability to get all the registers is a
> single syscall is a major performance improvement.
I'll chime in...
Other systems that support ptrace(2) don't have PEEK/POKE/READ_U/WRITE_U
methods.
I'm currently working on AltiVec for NetBSD/powerpc, and ptrace(2) interface
for AltiVec is going to look like:
PT_GETALTIVECREGS
PT_SETALTIVECREGS
...both of which using the following structure as an argument:
struct vreg {
uint32_t vreg[32][4]; /* vector register contents */
register_t vscr; /* vector status and control reg */
register_t vrsave; /* SPR 238 */
};
This is consistent with how e.g. SSE/SSE2 registers are handled on
NetBSD/i386 (PT_GETXMMREGS/PT_SETXMMREGS).
--
-- Jason R. Thorpe <thorpej@wasabisystems.com>
next prev parent reply other threads:[~2001-12-14 19:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.GSO.4.40.0112071443310.2903-300000@softail.somerset.sps.mot.com>
2001-12-07 14:24 ` Kevin Buettner
2001-12-07 14:34 ` Daniel Jacobowitz
2001-12-14 10:53 ` Kumar Gala
2001-12-14 11:17 ` Jason R Thorpe [this message]
2001-12-14 18:08 ` Andrew Cagney
2001-12-15 9:44 ` Kumar Gala
2001-12-16 13:13 ` Paul Mackerras
2002-01-10 10:59 ` 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=20011214111620.U9607@dr-evil.shagadelic.org \
--to=thorpej@wasabisystems.com \
--cc=drow@mvista.com \
--cc=ezannoni@cygnus.com \
--cc=fsirl@kernel.crashing.org \
--cc=gdb@sources.redhat.com \
--cc=kevinb@redhat.com \
--cc=kumar.gala@motorola.com \
--cc=linuxppc-dev@lists.linuxppc.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