From: Saket Kumar Bhaskar <skb99@linux.ibm.com>
To: bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: ast@kernel.org, hbathini@linux.ibm.com, andrii@kernel.org,
daniel@iogearbox.net, martin.lau@linux.dev, eddyz87@gmail.com,
song@kernel.org, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me,
haoluo@google.com, jolsa@kernel.org, shuah@kernel.org,
mykolal@fb.com
Subject: [PATCH 0/3] Fix test_bpf_syscall_macro selftest on powerpc
Date: Mon, 4 Nov 2024 10:30:04 +0530 [thread overview]
Message-ID: <20241104050007.13812-1-skb99@linux.ibm.com> (raw)
Since, syscall wrapper is supported on powerpc with syscall
entry symbols as sys_*, changes done to fix selftests like
test_bpf_syscall_macro, attach_probe/auto, etc.
Saket Kumar Bhaskar (3):
libbpf: Fix accessing the syscall argument on powerpc
libbpf: Remove powerpc prefix from syscall function names
selftests/bpf: Define SYS_PREFIX for powerpc
tools/lib/bpf/bpf_tracing.h | 9 +++++++--
tools/lib/bpf/libbpf.c | 10 ++++++++--
tools/testing/selftests/bpf/progs/bpf_misc.h | 3 +++
3 files changed, 18 insertions(+), 4 deletions(-)
--
2.43.5
next reply other threads:[~2024-11-04 5:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 5:00 Saket Kumar Bhaskar [this message]
2024-11-04 5:00 ` [PATCH 1/3] libbpf: Fix accessing the syscall argument on powerpc Saket Kumar Bhaskar
2024-11-04 5:00 ` [PATCH 2/3] libbpf: Remove powerpc prefix from syscall function names Saket Kumar Bhaskar
2024-11-08 18:43 ` Andrii Nakryiko
2024-11-20 14:52 ` Saket Kumar Bhaskar
2024-11-22 0:00 ` Andrii Nakryiko
2025-01-10 10:49 ` Saket Kumar Bhaskar
2025-01-10 22:29 ` Andrii Nakryiko
2025-01-11 19:53 ` Saket Kumar Bhaskar
2025-01-14 22:40 ` Andrii Nakryiko
2025-01-15 14:15 ` Saket Kumar Bhaskar
2025-01-16 23:19 ` Andrii Nakryiko
2024-11-04 5:00 ` [PATCH 3/3] selftests/bpf: Define SYS_PREFIX for powerpc Saket Kumar Bhaskar
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=20241104050007.13812-1-skb99@linux.ibm.com \
--to=skb99@linux.ibm.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=hbathini@linux.ibm.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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