loongarch.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Tiezhu Yang <yangtiezhu@loongson.cn>
To: bot+bpf-ci@kernel.org, chenhuacai@kernel.org, hengqi.chen@gmail.com
Cc: loongarch@lists.linux.dev, bpf@vger.kernel.org,
	linux-kernel@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, martin.lau@kernel.org, eddyz87@gmail.com,
	yonghong.song@linux.dev, clm@meta.com, ihor.solodrai@linux.dev
Subject: Re: [PATCH v1 1/5] LoongArch: Define format for AM{SWAP/ADD}.{B/H}, DBAR and BSTRINS.D
Date: Thu, 2 Apr 2026 10:48:38 +0800	[thread overview]
Message-ID: <3b8ef23a-e324-4ad8-430c-e02adca44a1c@loongson.cn> (raw)
In-Reply-To: <6089c3c90bd2f2cf2848a39fc0d30219d0f3f95f9c74257a19d01de053eb1c44@mail.kernel.org>

On 2026/4/1 下午4:23, bot+bpf-ci@kernel.org wrote:
>> diff --git a/arch/loongarch/kernel/cpu-probe.c b/arch/loongarch/kernel/cpu-probe.c
>> index 657bbae6c1c7..93466fc7d33d 100644
>> --- a/arch/loongarch/kernel/cpu-probe.c
>> +++ b/arch/loongarch/kernel/cpu-probe.c
>> @@ -177,6 +177,10 @@ static void cpu_probe_common(struct cpuinfo_loongarch *c)
>>   		c->options |= LOONGARCH_CPU_LAM;
>>   		elf_hwcap |= HWCAP_LOONGARCH_LAM;
>>   	}
>> +	if (config & CPUCFG2_LAM_BH) {
>> +		c->options |= LOONGARCH_CPU_LAM_BH;
>> +		elf_hwcap |= HWCAP_LOONGARCH_LAM_BH;
>> +	}
> 
> Should there be a corresponding entry in the "Features" line of
> /proc/cpuinfo for the new lam_bh capability?
> 
> Every other feature that sets elf_hwcap in cpu_probe_common() also
> has a matching seq_puts() in show_cpuinfo() in proc.c:
> 
> arch/loongarch/kernel/proc.c:show_cpuinfo() {
>      ...
>      if (cpu_has_lam)
>              seq_puts(m, " lam");
>      if (cpu_has_scq)
>              seq_puts(m, " scq");
>      ...
> }
> 
> The new cpu_has_lam_bh is missing from this list.

Yes, I think so, thank you.
I will wait for more comments before sending v2.

Thanks,
Tiezhu


  reply	other threads:[~2026-04-02  2:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-01  7:12 [PATCH v1 0/5] LoongArch: BPF: Support more atomic instructions Tiezhu Yang
2026-04-01  7:12 ` [PATCH v1 1/5] LoongArch: Define format for AM{SWAP/ADD}.{B/H}, DBAR and BSTRINS.D Tiezhu Yang
2026-04-01  8:23   ` bot+bpf-ci
2026-04-02  2:48     ` Tiezhu Yang [this message]
2026-04-01  7:12 ` [PATCH v1 2/5] LoongArch: BPF: Add the default case in emit_atomic() and rename it Tiezhu Yang
2026-04-01  7:12 ` [PATCH v1 3/5] LoongArch: BPF: Support 8 and 16 bit read-modify-write instructions Tiezhu Yang
2026-04-01  7:12 ` [PATCH v1 4/5] LoongArch: BPF: Support load-acquire and store-release instructions Tiezhu Yang
2026-04-01  7:12 ` [PATCH v1 5/5] selftests/bpf: Make CAN_USE_LOAD_ACQ_STORE_REL usable for LoongArch 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=3b8ef23a-e324-4ad8-430c-e02adca44a1c@loongson.cn \
    --to=yangtiezhu@loongson.cn \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bot+bpf-ci@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=chenhuacai@kernel.org \
    --cc=clm@meta.com \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=hengqi.chen@gmail.com \
    --cc=ihor.solodrai@linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loongarch@lists.linux.dev \
    --cc=martin.lau@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).