From: Dave Martin <dave.martin@linaro.org>
To: linux-kernel@vger.kernel.org
Cc: Will Deacon <Will.Deacon@arm.com>,
Nicolas Pitre <nicolas.pitre@linaro.org>,
Ulrich Weigand <ulrich.weigand@linaro.org>,
Suresh Siddha <suresh.b.siddha@intel.com>
Subject: RFC: ptrace: Enabling PTRACE_{GET,SET}REGSET calls without CONFIG_HAVE_ARCH_TRACEHOOK
Date: Fri, 1 Apr 2011 17:47:13 +0100 [thread overview]
Message-ID: <20110401164713.GA16870@arm.com> (raw)
Hi all,
I notice in kernel/ptrace.c that the generic regset ptrace calls
PTRACE_GETREGSET and PTRACE_SETREGSET are predicated on
CONFIG_HAVE_ARCH_TRACEHOOK.
However, if I'm reading the code correctly then all these calls
really depend on is regsets implemented in the target arch.
Since I'm separately proposing a regsets implementation for ARM,
it would be nice to enable these ptrace calls; but I don't think
we're ready to enable CONFIG_HAVE_ARCH_TRACEHOOK there for now.
Does anyone know whether it would be safe/straightforward to
change the #ifdef in kernel/ptrace.c to something else,
such as CORE_DUMP_USE_REGSET? I think all arches which implement
regsets define this, though I haven't researched this thoroughly.
Any views welcome.
Cheers
---Dave
reply other threads:[~2011-04-01 16:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20110401164713.GA16870@arm.com \
--to=dave.martin@linaro.org \
--cc=Will.Deacon@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=suresh.b.siddha@intel.com \
--cc=ulrich.weigand@linaro.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