Date: Fri, 1 Apr 2011 17:47:13 +0100
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
Message-ID: <20110401164713.GA16870@arm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1009
Lines: 27

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/