From: Andreas Schwab <schwab@linux-m68k.org>
To: Radu Rendec <radu.rendec@gmail.com>
Cc: Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org, Oleg Nesterov <oleg@redhat.com>,
Daniel Axtens <dja@axtens.net>
Subject: Re: [PATCH 0/1] PPC32: fix ptrace() access to FPU registers
Date: Tue, 18 Jun 2019 20:09:34 +0200 [thread overview]
Message-ID: <875zp2rcip.fsf@igel.home> (raw)
In-Reply-To: <fbf9f9cbb99fc40c7d7af86fee3984427c61b799.camel__46559.9162316479$1560860409$gmane$org@gmail.com> (Radu Rendec's message of "Tue, 18 Jun 2019 08:16:25 -0400")
On Jun 18 2019, Radu Rendec <radu.rendec@gmail.com> wrote:
> Since you already have a working setup, it would be nice if you could
> add a printk to arch_ptrace() to print the address and confirm what I
> believe happens (by reading the gdb source code).
A ppc32 ptrace syscall goes through compat_arch_ptrace.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2019-06-18 18:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 23:27 [PATCH 0/1] PPC32: fix ptrace() access to FPU registers Radu Rendec
2019-06-10 23:27 ` [PATCH 1/1] " Radu Rendec
2019-06-13 7:59 ` [PATCH 0/1] " Daniel Axtens
2019-06-17 1:19 ` Daniel Axtens
2019-06-17 2:27 ` Radu Rendec
2019-06-18 6:42 ` Daniel Axtens
2019-06-18 12:16 ` Radu Rendec
[not found] ` <fbf9f9cbb99fc40c7d7af86fee3984427c61b799.camel__46559.9162316479$1560860409$gmane$org@gmail.com>
2019-06-18 18:09 ` Andreas Schwab [this message]
2019-06-19 0:36 ` Daniel Axtens
2019-06-19 12:57 ` Radu Rendec
2021-06-11 6:02 ` Christophe Leroy
2021-06-11 14:37 ` Radu Rendec
2021-07-18 18:07 ` Radu Rendec
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=875zp2rcip.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=dja@axtens.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=oleg@redhat.com \
--cc=paulus@samba.org \
--cc=radu.rendec@gmail.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;
as well as URLs for NNTP newsgroup(s).