From: He Kuang <hekuang@huawei.com>
To: <peterz@infradead.org>, <will.deacon@arm.com>, <mingo@redhat.com>,
<acme@kernel.org>, <alexander.shishkin@linux.intel.com>,
<mhiramat@kernel.org>, <jolsa@redhat.com>, <hekuang@huawei.com>
Cc: <wangnan0@huawei.com>, <bintian.wang@huawei.com>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH v2 2/3] perf tools: Enable bpf prologue for arm64
Date: Fri, 3 Feb 2017 11:06:06 +0000 [thread overview]
Message-ID: <20170203110607.97529-2-hekuang@huawei.com> (raw)
In-Reply-To: <20170203110607.97529-1-hekuang@huawei.com>
Since HAVE_KPROBES can be enabled in arm64, this patch introduces
regs_query_register_offset() to convert register name to offset for
arm64, so the BPF prologue feature is ready to use.
Acked-by: Masami Hiramatsu <mhiramat@kernel.org>
Signed-off-by: He Kuang <hekuang@huawei.com>
---
tools/perf/arch/arm64/Makefile | 1 +
tools/perf/arch/arm64/util/dwarf-regs.c | 20 ++++++++++++++++++++
2 files changed, 21 insertions(+)
diff --git a/tools/perf/arch/arm64/Makefile b/tools/perf/arch/arm64/Makefile
index 18b1351..eebe1ec 100644
--- a/tools/perf/arch/arm64/Makefile
+++ b/tools/perf/arch/arm64/Makefile
@@ -2,3 +2,4 @@ ifndef NO_DWARF
PERF_HAVE_DWARF_REGS := 1
endif
PERF_HAVE_JITDUMP := 1
+PERF_HAVE_ARCH_REGS_QUERY_REGISTER_OFFSET := 1
diff --git a/tools/perf/arch/arm64/util/dwarf-regs.c b/tools/perf/arch/arm64/util/dwarf-regs.c
index 090f36b..6d17a31 100644
--- a/tools/perf/arch/arm64/util/dwarf-regs.c
+++ b/tools/perf/arch/arm64/util/dwarf-regs.c
@@ -9,6 +9,8 @@
*/
#include <stddef.h>
+#include <errno.h> /* for EINVAL */
+#include <string.h> /* for strcmp */
#include <linux/ptrace.h> /* for struct user_pt_regs */
#include <dwarf-regs.h>
@@ -75,3 +77,21 @@ const char *get_arch_regstr(unsigned int n)
{
return (n < ARCH_MAX_REGS) ? regoffset_table[n].name : NULL;
}
+
+/* Reuse code from arch/arm64/kernel/ptrace.c */
+/**
+ * regs_query_register_offset() - query register offset from its name
+ * @name: the name of a register
+ *
+ * regs_query_register_offset() returns the offset of a register in struct
+ * user_pt_regs from its name. If the name is invalid, this returns -EINVAL;
+ */
+int regs_query_register_offset(const char *name)
+{
+ const struct pt_regs_offset *roff;
+
+ for (roff = regoffset_table; roff->name != NULL; roff++)
+ if (!strcmp(roff->name, name))
+ return roff->offset;
+ return -EINVAL;
+}
--
1.8.5.2
next prev parent reply other threads:[~2017-02-03 11:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 11:06 [PATCH v2 1/3] perf tools: Use offset instead of dwarfnum in register table He Kuang
2017-02-03 11:06 ` He Kuang [this message]
2017-02-03 11:06 ` [PATCH v2 3/3] perf tools: Add missing newline in debug messages He Kuang
2017-02-03 13:00 ` [PATCH v2 1/3] perf tools: Use offset instead of dwarfnum in register table Will Deacon
2017-02-04 9:03 ` [PATCH v3] perf tools arm64: Add support for generating bpf prologue He Kuang
2017-02-04 9:03 ` [PATCH v2 1/3] perf tools: Use offset instead of dwarfnum in register table Hekuang
2017-02-06 13:02 ` Will Deacon
2017-02-07 0:54 ` Masami Hiramatsu
2017-02-07 9:20 ` Will Deacon
2017-02-07 12:17 ` 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=20170203110607.97529-2-hekuang@huawei.com \
--to=hekuang@huawei.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=bintian.wang@huawei.com \
--cc=jolsa@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=wangnan0@huawei.com \
--cc=will.deacon@arm.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
all inboxes | Powered by JetHome®