From: dave.long@linaro.org (David Long)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 1/6] arm64: Add HAVE_REGS_AND_STACK_ACCESS_API feature
Date: Mon, 20 Apr 2015 03:15:06 -0400 [thread overview]
Message-ID: <5534A77A.8040509@linaro.org> (raw)
In-Reply-To: <20150325134410.GA26903@localhost>
On 03/25/15 09:44, Catalin Marinas wrote:
> On Tue, Feb 17, 2015 at 06:11:36PM -0500, David Long wrote:
>> diff --git a/arch/arm64/include/uapi/asm/ptrace.h b/arch/arm64/include/uapi/asm/ptrace.h
>> index 6913643..700d28b 100644
>> --- a/arch/arm64/include/uapi/asm/ptrace.h
>> +++ b/arch/arm64/include/uapi/asm/ptrace.h
>> @@ -61,6 +61,42 @@
>>
>> #ifndef __ASSEMBLY__
>>
>> +#define ARM_cpsr pstate
>
> There is no CPSR on AArch64, it's just called PSTATE. But more
> importantly, what's the point of all these macros?
>
>> diff --git a/arch/arm64/kernel/ptrace.c b/arch/arm64/kernel/ptrace.c
>> index d882b83..adc1f39 100644
>> --- a/arch/arm64/kernel/ptrace.c
>> +++ b/arch/arm64/kernel/ptrace.c
>> @@ -48,6 +48,122 @@
>> #define CREATE_TRACE_POINTS
>> #include <trace/events/syscalls.h>
>>
>> +struct pt_regs_offset {
>> + const char *name;
>> + int offset;
>> +};
>> +
>> +#define REG_OFFSET_NAME(r) \
>> + {.name = #r, .offset = offsetof(struct pt_regs, ARM_##r)}
>> +#define REG_OFFSET_END {.name = NULL, .offset = 0}
>> +
>> +static const struct pt_regs_offset regoffset_table[] = {
>> + REG_OFFSET_NAME(x0),
>
> If it is just for defining a name, just change the REG_OFFSET_NAME macro
> to take a string argument and remove all the ARM_ macros.
>
> I'm also not sure why we need the ARM_ prefix. Do you see them used
> outside the arm64 context?
>
Sorry Catalin, I don't have a record of having replied to this yet so
this is a quite late reply.
The macros were taken from the 32-bit ARM implementation, which in turn
looks to be taken from x86/sh/powerpc for
HAVE_REGS_AND_STACK_ACCESS_API. I've replaced the hacky define of cpsr
with pstate. The macros create symbolic names that can be looked up by,
for example, event tracing strings entered through debugfs. This is
consistent across multiple platforms.
-dl
next prev parent reply other threads:[~2015-04-20 7:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-17 23:11 [PATCH v5 0/6] arm64: Add kernel probes (kprobes) support David Long
2015-02-17 23:11 ` [PATCH v5 1/6] arm64: Add HAVE_REGS_AND_STACK_ACCESS_API feature David Long
2015-02-18 14:59 ` Masami Hiramatsu
2015-03-25 13:44 ` Catalin Marinas
2015-04-20 7:15 ` David Long [this message]
2015-02-17 23:11 ` [PATCH v5 2/6] arm64: Add more test functions to insn.c David Long
2015-02-18 15:00 ` Masami Hiramatsu
2015-02-17 23:11 ` [PATCH v5 3/6] arm64: Kprobes with single stepping support David Long
2015-02-18 14:59 ` Masami Hiramatsu
2015-02-27 6:38 ` David Long
2015-02-27 8:27 ` Masami Hiramatsu
2015-04-08 6:07 ` Pratyush Anand
2015-04-08 11:01 ` David Long
2015-02-17 23:11 ` [PATCH v5 4/6] arm64: kprobes instruction simulation support David Long
2015-03-06 11:39 ` Steve Capper
2015-03-06 14:42 ` David Long
2015-02-17 23:11 ` [PATCH v5 5/6] arm64: Add kernel return probes support (kretprobes) David Long
2015-02-19 14:49 ` Masami Hiramatsu
2015-02-17 23:11 ` [PATCH v5 6/6] kprobes: Add arm64 case in kprobe example module David Long
2015-02-19 14:18 ` Masami Hiramatsu
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=5534A77A.8040509@linaro.org \
--to=dave.long@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).