From: patchwork-bot+netdevbpf@kernel.org
To: tongtiangen <tongtiangen@huawei.com>
Cc: paul.walmsley@sifive.com, palmer@dabbelt.com,
palmerdabbelt@google.com, aou@eecs.berkeley.edu,
bjorn@kernel.org, luke.r.nels@gmail.com, xi.wang@gmail.com,
ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next,v3] riscv, bpf: Add BPF exception tables
Date: Wed, 27 Oct 2021 23:10:07 +0000 [thread overview]
Message-ID: <163537620786.14362.5033693418821355895.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211027111822.3801679-1-tongtiangen@huawei.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Wed, 27 Oct 2021 11:18:22 +0000 you wrote:
> When a tracing BPF program attempts to read memory without using the
> bpf_probe_read() helper, the verifier marks the load instruction with
> the BPF_PROBE_MEM flag. Since the riscv JIT does not currently recognize
> this flag it falls back to the interpreter.
>
> Add support for BPF_PROBE_MEM, by appending an exception table to the
> BPF program. If the load instruction causes a data abort, the fixup
> infrastructure finds the exception table and fixes up the fault, by
> clearing the destination register and jumping over the faulting
> instruction.
>
> [...]
Here is the summary with links:
- [bpf-next,v3] riscv, bpf: Add BPF exception tables
https://git.kernel.org/bpf/bpf-next/c/252c765bd764
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@kernel.org
To: tongtiangen <tongtiangen@huawei.com>
Cc: paul.walmsley@sifive.com, palmer@dabbelt.com,
palmerdabbelt@google.com, aou@eecs.berkeley.edu,
bjorn@kernel.org, luke.r.nels@gmail.com, xi.wang@gmail.com,
ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next,v3] riscv, bpf: Add BPF exception tables
Date: Wed, 27 Oct 2021 23:10:07 +0000 [thread overview]
Message-ID: <163537620786.14362.5033693418821355895.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211027111822.3801679-1-tongtiangen@huawei.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Wed, 27 Oct 2021 11:18:22 +0000 you wrote:
> When a tracing BPF program attempts to read memory without using the
> bpf_probe_read() helper, the verifier marks the load instruction with
> the BPF_PROBE_MEM flag. Since the riscv JIT does not currently recognize
> this flag it falls back to the interpreter.
>
> Add support for BPF_PROBE_MEM, by appending an exception table to the
> BPF program. If the load instruction causes a data abort, the fixup
> infrastructure finds the exception table and fixes up the fault, by
> clearing the destination register and jumping over the faulting
> instruction.
>
> [...]
Here is the summary with links:
- [bpf-next,v3] riscv, bpf: Add BPF exception tables
https://git.kernel.org/bpf/bpf-next/c/252c765bd764
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2021-10-27 23:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 11:18 [PATCH bpf-next,v3] riscv, bpf: Add BPF exception tables Tong Tiangen
2021-10-27 11:18 ` Tong Tiangen
2021-10-27 11:50 ` Mark Rutland
2021-10-27 11:50 ` Mark Rutland
2021-10-27 13:26 ` tongtiangen
2021-10-27 13:26 ` tongtiangen
2021-10-27 16:55 ` Björn Töpel
2021-10-27 16:55 ` Björn Töpel
2021-10-27 23:11 ` Daniel Borkmann
2021-10-27 23:11 ` Daniel Borkmann
2021-10-28 1:01 ` tongtiangen
2021-10-28 1:01 ` tongtiangen
2021-10-28 0:59 ` tongtiangen
2021-10-28 0:59 ` tongtiangen
2021-10-27 23:10 ` patchwork-bot+netdevbpf [this message]
2021-10-27 23:10 ` patchwork-bot+netdevbpf
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=163537620786.14362.5033693418821355895.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=luke.r.nels@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=palmer@dabbelt.com \
--cc=palmerdabbelt@google.com \
--cc=paul.walmsley@sifive.com \
--cc=songliubraving@fb.com \
--cc=tongtiangen@huawei.com \
--cc=xi.wang@gmail.com \
--cc=yhs@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.