From: Song Liu <songliubraving@fb.com>
To: Pu Lehui <pulehui@huawei.com>
Cc: bpf <bpf@vger.kernel.org>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"bjorn@kernel.org" <bjorn@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
"andrii@kernel.org" <andrii@kernel.org>,
"luke.r.nels@gmail.com" <luke.r.nels@gmail.com>,
"xi.wang@gmail.com" <xi.wang@gmail.com>,
Martin Lau <kafai@fb.com>, Yonghong Song <yhs@fb.com>,
"john.fastabend@gmail.com" <john.fastabend@gmail.com>,
"kpsingh@kernel.org" <kpsingh@kernel.org>
Subject: Re: [PATCH bpf-next] riscv, bpf: Implement more atomic operations for RV64
Date: Mon, 11 Apr 2022 05:44:57 +0000 [thread overview]
Message-ID: <1ACA6849-7960-4BA7-9F85-449E9EDD0C74@fb.com> (raw)
In-Reply-To: <20220410101246.232875-1-pulehui@huawei.com>
> On Apr 10, 2022, at 3:12 AM, Pu Lehui <pulehui@huawei.com> wrote:
>
> This patch implement more bpf atomic operations for RV64.
> The added operations are shown below:
>
> atomic[64]_[fetch_]add
> atomic[64]_[fetch_]and
> atomic[64]_[fetch_]or
> atomic[64]_xchg
> atomic[64]_cmpxchg
>
> Since riscv specification does not provide AMO instruction for
> CAS operation, we use lr/sc instruction for cmpxchg operation,
> and AMO instructions for the rest ops. Tests "test_bpf.ko" and
> "test_progs -t atomic" have passed, as well as "test_verifier"
> with no new failure ceses.
>
> Signed-off-by: Pu Lehui <pulehui@huawei.com>
LGTM.
Acked-by: Song Liu <songliubraving@fb.com>
next prev parent reply other threads:[~2022-04-11 5:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-10 10:12 [PATCH bpf-next] riscv, bpf: Implement more atomic operations for RV64 Pu Lehui
2022-04-11 5:44 ` Song Liu [this message]
2022-04-11 12:49 ` Björn Töpel
2022-04-11 15:00 ` 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=1ACA6849-7960-4BA7-9F85-449E9EDD0C74@fb.com \
--to=songliubraving@fb.com \
--cc=andrii@kernel.org \
--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-riscv@lists.infradead.org \
--cc=luke.r.nels@gmail.com \
--cc=pulehui@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox