loongarch.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Tiezhu Yang <yangtiezhu@loongson.cn>
To: Huacai Chen <chenhuacai@kernel.org>
Cc: Hengqi Chen <hengqi.chen@gmail.com>,
	loongarch@lists.linux.dev, bpf@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/5] LoongArch: BPF: Support more atomic instructions
Date: Tue, 21 Apr 2026 21:46:56 +0800	[thread overview]
Message-ID: <db1df5cf-40a8-2968-7f58-fdd6ec367032@loongson.cn> (raw)
In-Reply-To: <4a6c89b6-72a8-a80b-1f7c-9a620ed24505@loongson.cn>

On 4/21/26 21:25, Tiezhu Yang wrote:
> On 4/21/26 20:38, Huacai Chen wrote:
>> Hi, Tiezhu,
>>
>> Maybe we need V4? If so, please submit as soon as possible.
> 
> For now, TBH, I do not want to do that.
> 
> Patch #1 is OK.
> 
> Patch #2 is OK.
> 
> Patch #3 is OK according to Wang Rui's reply.
> 
> Patch #4 has no big problems, the current testcases passed,
> I am not sure whether it has problem, I can fix it if there
> is a real problem, maybe it needs to update the testcase first.
> 
> patch #5 is OK, hope you can replace "usable" with "enable" in
> the patch subject and commit message when applying.

For patch #5, correct myself, enable is verb, usable is adjective,
so just keep it as is, or modify the log as following:

---
selftests/bpf: Enable CAN_USE_LOAD_ACQ_STORE_REL for LoongArch

In order to do the following load-acquire and store-release tests
on LoongArch:

   sudo ./test_progs -t verifier_load_acquire
   sudo ./test_progs -t verifier_store_release
   sudo ./test_progs -t verifier_precision/bpf_load_acquire
   sudo ./test_progs -t verifier_precision/bpf_store_release
   sudo ./test_progs -t compute_live_registers/atomic_load_acq_store_rel

it needs to enable CAN_USE_LOAD_ACQ_STORE_REL for LoongArch.
---

For short, replace "make ... usable" with "enable ...".

Thanks,
Tiezhu


  reply	other threads:[~2026-04-21 13:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-13  4:05 [PATCH v3 0/5] LoongArch: BPF: Support more atomic instructions Tiezhu Yang
2026-04-13  4:05 ` [PATCH v3 1/5] LoongArch: Define instruction formats for AM{SWAP/ADD}.{B/H} and DBAR Tiezhu Yang
2026-04-15  2:24   ` Hengqi Chen
2026-04-13  4:05 ` [PATCH v3 2/5] LoongArch: BPF: Add the default case in emit_atomic() and rename it Tiezhu Yang
2026-04-15  2:24   ` Hengqi Chen
2026-04-13  4:05 ` [PATCH v3 3/5] LoongArch: BPF: Support 8 and 16 bit read-modify-write instructions Tiezhu Yang
2026-04-13  4:49   ` bot+bpf-ci
2026-04-13  8:05     ` WANG Rui
2026-04-13  4:05 ` [PATCH v3 4/5] LoongArch: BPF: Support load-acquire and store-release instructions Tiezhu Yang
2026-04-15  2:25   ` Hengqi Chen
2026-04-13  4:05 ` [PATCH v3 5/5] selftests/bpf: Make CAN_USE_LOAD_ACQ_STORE_REL usable for LoongArch Tiezhu Yang
2026-04-15  2:27   ` Hengqi Chen
2026-04-21 12:38 ` [PATCH v3 0/5] LoongArch: BPF: Support more atomic instructions Huacai Chen
2026-04-21 13:25   ` Tiezhu Yang
2026-04-21 13:46     ` Tiezhu Yang [this message]
2026-04-22  8:15     ` Huacai Chen
2026-04-23  2:56       ` Tiezhu Yang

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=db1df5cf-40a8-2968-7f58-fdd6ec367032@loongson.cn \
    --to=yangtiezhu@loongson.cn \
    --cc=bpf@vger.kernel.org \
    --cc=chenhuacai@kernel.org \
    --cc=hengqi.chen@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loongarch@lists.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).