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: Sun, 16 Dec 2001 13:13:00 -0000 [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.
next prev parent reply other threads:[~2001-12-16 21:13 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
2001-12-14 18:08 ` Andrew Cagney
2001-12-15 9:44 ` Kumar Gala
2001-12-16 13:13 ` Paul Mackerras [this message]
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=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