From: Samuel Holland <samuel.holland@sifive.com>
To: Yunhui Cui <cuiyunhui@bytedance.com>
Cc: ajones@ventanamicro.com, alexghiti@rivosinc.com,
andybnac@gmail.com, aou@eecs.berkeley.edu, charlie@rivosinc.com,
cleger@rivosinc.com, conor.dooley@microchip.com,
conor@kernel.org, corbet@lwn.net, evan@rivosinc.com,
jesse@rivosinc.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-riscv@lists.infradead.org, palmer@dabbelt.com,
paul.walmsley@sifive.com, shuah@kernel.org
Subject: Re: [PATCH v4 3/3] RISC-V: selftests: Add TEST_ZICBOM into CBO tests
Date: Mon, 13 Jan 2025 23:32:45 -0600 [thread overview]
Message-ID: <fa984379-29b6-4093-9213-6a291ccc7e23@sifive.com> (raw)
In-Reply-To: <20250114021936.17234-4-cuiyunhui@bytedance.com>
On 2025-01-13 8:19 PM, Yunhui Cui wrote:
> Add test for Zicbom and its block size into CBO tests, when
> Zicbom is present, test that cbo.clean/flush may be issued and works.
> As the software can't verify the clean/flush functions, we just judged
> that cbo.clean/flush isn't executed illegally.
>
> Signed-off-by: Yunhui Cui <cuiyunhui@bytedance.com>
> ---
> tools/testing/selftests/riscv/hwprobe/cbo.c | 66 +++++++++++++++++----
> 1 file changed, 55 insertions(+), 11 deletions(-)
Reviewed-by: Samuel Holland <samuel.holland@sifive.com>
next prev parent reply other threads:[~2025-01-14 5:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 2:19 [PATCH v4 0/3] Enable Zicbom in usermode Yunhui Cui
2025-01-14 2:19 ` [PATCH v4 1/3] RISC-V: Enable cbo.clean/flush " Yunhui Cui
2025-01-14 2:19 ` [PATCH v4 2/3] RISC-V: hwprobe: Expose Zicbom extension and its block size Yunhui Cui
2025-01-14 5:28 ` Samuel Holland
2025-01-14 12:17 ` [External] " yunhui cui
2025-01-14 12:42 ` Andrew Jones
2025-01-14 2:19 ` [PATCH v4 3/3] RISC-V: selftests: Add TEST_ZICBOM into CBO tests Yunhui Cui
2025-01-14 5:32 ` Samuel Holland [this message]
2025-01-14 8:18 ` Andrew Jones
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=fa984379-29b6-4093-9213-6a291ccc7e23@sifive.com \
--to=samuel.holland@sifive.com \
--cc=ajones@ventanamicro.com \
--cc=alexghiti@rivosinc.com \
--cc=andybnac@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=charlie@rivosinc.com \
--cc=cleger@rivosinc.com \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=corbet@lwn.net \
--cc=cuiyunhui@bytedance.com \
--cc=evan@rivosinc.com \
--cc=jesse@rivosinc.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=shuah@kernel.org \
/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