From: Paul Mackerras <paulus@samba.org>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Kumar Gala <kumar.gala@motorola.com>,
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
Subject: Re: AltiVec register ptrace support
Date: Mon, 17 Dec 2001 08:11:10 +1100 (EST) [thread overview]
Message-ID: <15389.3566.531070.447917@argo.ozlabs.ibm.com> (raw)
In-Reply-To: <3C1AB0A5.7040102@cygnus.com>
Andrew Cagney writes:
> The Linux/PPC kernel supports PEEK/POKE for fetching registers. The
> proposed Kernel interface _consistently_ extends that interface using
> the exact same mechanims to obtain the altivec regiters. All the
> required changes for this have been posted and have been demonstrated to
> work.
>
> Separate to that, it has been _proposed_ that the PPC ptrace() interface
> be changed so that get/set reg for all register classes be added
> (incomplete patch posted). Isn't this separate to the problem at hand?
If we are going to add a get/set reg interface for the altivec vector
registers, I would rather not extend the peek/poke interface to do
that as well.
Paul.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-12-16 21:11 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-04 16:13 Changes to PPC Linux required for GCC 3.1 Corey Minyard
2001-12-04 16:16 ` David Edelsohn
2001-12-04 16:39 ` Corey Minyard
2001-12-05 12:55 ` Franz Sirl
2001-12-05 16:18 ` Corey Minyard
2001-12-05 17:37 ` Tom Rini
2001-12-05 17:50 ` Benjamin Herrenschmidt
2001-12-05 19:45 ` Tom Rini
2001-12-05 20:30 ` Franz Sirl
2001-12-07 13:01 ` Gabriel Paubert
2001-12-07 20:57 ` AltiVec register ptrace support Kumar Gala
2001-12-07 22:23 ` Kevin Buettner
2001-12-07 22:34 ` Daniel Jacobowitz
2001-12-14 18:52 ` Kumar Gala
2001-12-14 19:16 ` Jason R Thorpe
2001-12-15 2:08 ` Andrew Cagney
2001-12-15 17:44 ` Kumar Gala
2001-12-16 21:11 ` Paul Mackerras [this message]
2002-01-10 18:58 ` Kumar Gala
2001-12-05 21:59 ` Changes to PPC Linux required for GCC 3.1 Paul Mackerras
2001-12-05 20:17 ` Daniel Jacobowitz
2001-12-05 20:20 ` David Edelsohn
2001-12-05 20:30 ` Franz Sirl
2001-12-06 0:59 ` Corey Minyard
2001-12-06 3:38 ` Tom Rini
2001-12-07 5:22 ` Corey Minyard
2001-12-05 20:51 ` Franz Sirl
2001-12-06 1:41 ` Corey Minyard
-- strict thread matches above, loose matches on Subject: below --
2001-03-06 16:03 who loads argc in elf binary??????? Alexandre Nikolaev
2001-03-07 19:10 ` Daniel Jacobowitz
2001-03-07 19:15 ` David Edelsohn
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=15389.3566.531070.447917@argo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=ac131313@cygnus.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 \
/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).