From: "Björn Töpel" <bjorn@kernel.org>
To: ast@kernel.org, daniel@iogearbox.net, netdev@vger.kernel.org,
bpf@vger.kernel.org
Cc: "Björn Töpel" <bjorn@kernel.org>, linux-riscv@lists.infradead.org
Subject: [PATCH bpf-next 0/4] Various RISC-V BPF improvements
Date: Thu, 28 Oct 2021 15:20:37 +0200 [thread overview]
Message-ID: <20211028132041.516820-1-bjorn@kernel.org> (raw)
Unfortunately selftest/bpf does not build for RV64. This series fixes
that.
* JIT requires more iterations to converge
* Some Makefile issues
* bpf_tracing.h was missing RISC-V macros for PT_REGS
More details are in each commit.
There are still many failing tests, but this is a start.
Cheers,
Björn
Björn Töpel (4):
riscv, bpf: Increase the maximum number of iterations
tools build: Add RISC-V to HOSTARCH parsing
riscv, libbpf: Add RISC-V (RV64) support to bpf_tracing.h
selftests/bpf: Fix broken riscv build
arch/riscv/net/bpf_jit_core.c | 2 +-
tools/lib/bpf/bpf_tracing.h | 32 ++++++++++++++++++++++++++++
tools/scripts/Makefile.arch | 3 ++-
tools/testing/selftests/bpf/Makefile | 3 ++-
4 files changed, 37 insertions(+), 3 deletions(-)
base-commit: b066abba3ef16a4a085d237e95da0de3f0b87713
--
2.32.0
next reply other threads:[~2021-10-28 13:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 13:20 Björn Töpel [this message]
2021-10-28 13:20 ` [PATCH bpf-next 1/4] riscv, bpf: Increase the maximum number of iterations Björn Töpel
2021-10-28 13:20 ` [PATCH bpf-next 2/4] tools build: Add RISC-V to HOSTARCH parsing Björn Töpel
2021-10-28 13:20 ` [PATCH bpf-next 3/4] riscv, libbpf: Add RISC-V (RV64) support to bpf_tracing.h Björn Töpel
2021-10-28 13:20 ` [PATCH bpf-next 4/4] selftests/bpf: Fix broken riscv build Björn Töpel
2021-10-28 15:58 ` Björn Töpel
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=20211028132041.516820-1-bjorn@kernel.org \
--to=bjorn@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-riscv@lists.infradead.org \
--cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).