[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251023154841.36007-1-zihong.plct@isrc.iscas.ac.cn>
Date: Thu, 23 Oct 2025 23:48:18 +0800
From: Yao Zihong <zihong.plct@...c.iscas.ac.cn>
To: ajones@...tanamicro.com
Cc: alex@...ti.fr,
alexghiti@...osinc.com,
aou@...s.berkeley.edu,
cleger@...osinc.com,
evan@...osinc.com,
linux-kernel@...r.kernel.org,
linux-riscv@...ts.infradead.org,
palmer@...belt.com,
pjw@...nel.org,
samuel.holland@...ive.com,
shuah@...nel.org,
zhangyin2018@...as.ac.cn,
zihong.plct@...c.iscas.ac.cn,
zihongyao@...look.com
Subject: Re: [PATCH v3 2/2] selftests/riscv: Add Zicbop prefetch test
> Undesired reformatting
My bad. It will be fixed in the next version.
> Should we just unconditionally register handlers for SIGSEGV and SIGBUS?
I think it depends on what the flags --sig{segv,ill,bus} are intended to mean:
a) We intend to handle these faults that might be raised inside the test
(i.e., catch and convert them into pass/fail results without crashing the
test binary, rather than letting something else handle them externally).
b) We expect these signals to be raised as part of the test scenario and
handle them within the test program accordingly.
I'm not sure if (a) is appropriate, since it might mess up someone’s CI
or other automation setups.
If we’re going with (b), then registering handlers for SIGSEGV and SIGBUS
based on flags would be inconsistent with that semantics, since prefetch.*
should never legitimately raise them. In that case, this design probably
doesn’t make sense. Would it also make sense to rename the '--sigill' flag
to make this clearer?
Thanks,
Zihong
Powered by blists - more mailing lists