From: Sergey Matyukevich <geomatsi@gmail.com>
To: bpf@vger.kernel.org
Cc: Vladimir Isaev <isaev@synopsys.com>,
Vineet Gupta <vgupta@kernel.org>,
Sergey Matyukevich <sergey.matyukevich@synopsys.com>
Subject: [PATCH] ARC: bpf: define uapi for BPF_PROG_TYPE_PERF_EVENT program type
Date: Thu, 14 Apr 2022 11:11:26 +0300 [thread overview]
Message-ID: <20220414081126.3176820-1-geomatsi@gmail.com> (raw)
From: Sergey Matyukevich <sergey.matyukevich@synopsys.com>
Define appropriate uapi for the BPF_PROG_TYPE_PERF_EVENT program type
by exporting the user_regs_struct structure instead of the pt_regs
structure that is in-kernel only.
Signed-off-by: Sergey Matyukevich <sergey.matyukevich@synopsys.com>
---
Originally I sent this patch via linux-snps-arc mailing list: see [1].
However this patch accompanies ARC support for libbpf bpf_tracing.h
accepted to bpf kernel tree: see [2].
So it looks like it makes sense to post this patch here as well.
I will also update linux-snps-arc patch series accordingly.
Regards,
Sergey
[1] https://lore.kernel.org/linux-snps-arc/20220408155804.587197-1-geomatsi@gmail.com/
[2] https://lore.kernel.org/bpf/20220408224442.599566-1-geomatsi@gmail.com/
arch/arc/include/asm/perf_event.h | 4 ++++
arch/arc/include/uapi/asm/bpf_perf_event.h | 9 +++++++++
2 files changed, 13 insertions(+)
create mode 100644 arch/arc/include/uapi/asm/bpf_perf_event.h
diff --git a/arch/arc/include/asm/perf_event.h b/arch/arc/include/asm/perf_event.h
index 4c919c0f4b30..d5719a260864 100644
--- a/arch/arc/include/asm/perf_event.h
+++ b/arch/arc/include/asm/perf_event.h
@@ -63,4 +63,8 @@ struct arc_reg_cc_build {
#define PERF_COUNT_ARC_HW_MAX (PERF_COUNT_HW_MAX + 8)
+#ifdef CONFIG_PERF_EVENTS
+#define perf_arch_bpf_user_pt_regs(regs) (struct user_regs_struct *)regs
+#endif
+
#endif /* __ASM_PERF_EVENT_H */
diff --git a/arch/arc/include/uapi/asm/bpf_perf_event.h b/arch/arc/include/uapi/asm/bpf_perf_event.h
new file mode 100644
index 000000000000..6cb1c2823288
--- /dev/null
+++ b/arch/arc/include/uapi/asm/bpf_perf_event.h
@@ -0,0 +1,9 @@
+/* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
+#ifndef _UAPI__ASM_BPF_PERF_EVENT_H__
+#define _UAPI__ASM_BPF_PERF_EVENT_H__
+
+#include <asm/ptrace.h>
+
+typedef struct user_regs_struct bpf_user_pt_regs_t;
+
+#endif /* _UAPI__ASM_BPF_PERF_EVENT_H__ */
--
2.35.1
next reply other threads:[~2022-04-14 8:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 8:11 Sergey Matyukevich [this message]
2022-04-18 19:11 ` [PATCH] ARC: bpf: define uapi for BPF_PROG_TYPE_PERF_EVENT program type Vineet Gupta
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=20220414081126.3176820-1-geomatsi@gmail.com \
--to=geomatsi@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=isaev@synopsys.com \
--cc=sergey.matyukevich@synopsys.com \
--cc=vgupta@kernel.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