From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: supriya kannery <supriyak@in.ibm.com>,
linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: Incorrect order of last two arguments of ptrace for requests PPC_PTRACE_GETREGS, SETREGS, GETFPREGS, SETFPREGS
Date: Thu, 23 Nov 2006 08:35:43 +1100 [thread overview]
Message-ID: <1164231343.5653.30.camel@localhost.localdomain> (raw)
In-Reply-To: <1164220580.12365.8.camel@hades.cambridge.redhat.com>
On Wed, 2006-11-22 at 18:36 +0000, David Woodhouse wrote:
> On
> > This is because PPC_PTRACE_GETREGS option for powerpc is implemented
> > such that general purpose
> > registers of the child process get copied to the address variable
> > instead of data variable. Same is
> > the case with other PPC request options PPC_PTRACE_SETREGS, GETFPREGS
> > and SETFPREGS.
> >
> > Prepared a patch for this problem and tested with 2.6.18-rc6 kernel.
> > This patch can be applied directly to 2.6.19-rc3 kernel.
>
> A more appropriate place to send this would be the linux-ppc development
> list.
Also it's possible that existing code like gcc relies on that "feature"
no ?
Ben.
next prev parent reply other threads:[~2006-11-22 21:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 10:53 Incorrect order of last two arguments of ptrace for requests PPC_PTRACE_GETREGS, SETREGS, GETFPREGS, SETFPREGS supriya kannery
2006-10-25 20:43 ` David Miller
2006-10-27 7:20 ` supriya kannery
2006-10-27 7:10 ` David Miller
2006-10-31 12:18 ` supriya kannery
2006-11-22 18:36 ` David Woodhouse
2006-11-22 21:35 ` Benjamin Herrenschmidt [this message]
2006-12-04 21:58 ` Anton Blanchard
2007-04-30 5:42 ` Paul Mackerras
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=1164231343.5653.30.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=supriyak@in.ibm.com \
/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