From: Dong Yang <dayss1224@gmail.com>
To: Andrew Jones <ajones@ventanamicro.com>
Cc: pbonzini@redhat.com, shuah@kernel.org, anup@brainfault.org,
atish.patra@linux.dev, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
kvm@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, kvm-riscv@lists.infradead.org,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH v3 0/3] KVM: riscv: selftests: Enable supported test cases
Date: Thu, 4 Sep 2025 17:48:21 +0800 [thread overview]
Message-ID: <aLlf6ZQ1uNjs8XS+@days-ASUSLaptop> (raw)
In-Reply-To: <20250902-9cc0d0dad59ba680062dbbf8@orel>
On Tue, Sep 02, 2025 at 10:36:10AM -0500, Andrew Jones wrote:
> On Mon, Sep 01, 2025 at 03:35:48PM +0800, dayss1224@gmail.com wrote:
> > From: Dong Yang <dayss1224@gmail.com>
> >
> > Add supported KVM test cases and fix the compilation dependencies.
> > ---
> > Changes in v3:
> > - Reorder patches to fix build dependencies
> > - Sort common supported test cases alphabetically
> > - Move ucall_common.h include from common header to specific source files
> >
> > Changes in v2:
> > - Delete some repeat KVM test cases on riscv
> > - Add missing headers to fix the build for new RISC-V KVM selftests
> >
> > Dong Yang (1):
> > KVM: riscv: selftests: Add missing headers for new testcases
> >
> > Quan Zhou (2):
> > KVM: riscv: selftests: Use the existing RISCV_FENCE macro in
> > `rseq-riscv.h`
> > KVM: riscv: selftests: Add common supported test cases
> >
> > tools/testing/selftests/kvm/Makefile.kvm | 6 ++++++
> > tools/testing/selftests/kvm/access_tracking_perf_test.c | 1 +
> > tools/testing/selftests/kvm/include/riscv/processor.h | 1 +
> > .../selftests/kvm/memslot_modification_stress_test.c | 1 +
> > tools/testing/selftests/kvm/memslot_perf_test.c | 1 +
> > tools/testing/selftests/rseq/rseq-riscv.h | 3 +--
> > 6 files changed, 11 insertions(+), 2 deletions(-)
> >
> > --
> > 2.34.1
>
> In the future please CC previous reviewers on the entire series
> (particularly when they have reviewed the entire previous series).
Okay, I will pay attention to this in the future. Thanks.
>
> For the series,
>
> Reviewed-by: Andrew Jones <ajones@ventanamicro.com>
next prev parent reply other threads:[~2025-09-04 9:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 7:35 [PATCH v3 0/3] KVM: riscv: selftests: Enable supported test cases dayss1224
2025-09-01 7:35 ` [PATCH v3 1/3] KVM: riscv: selftests: Use the existing RISCV_FENCE macro in `rseq-riscv.h` dayss1224
2025-09-01 7:35 ` [PATCH v3 2/3] KVM: riscv: selftests: Add missing headers for new testcases dayss1224
2025-09-01 7:35 ` [PATCH v3 3/3] KVM: riscv: selftests: Add common supported test cases dayss1224
2025-09-02 15:36 ` [PATCH v3 0/3] KVM: riscv: selftests: Enable " Andrew Jones
2025-09-04 9:48 ` Dong Yang [this message]
2025-09-03 14:31 ` Anup Patel
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=aLlf6ZQ1uNjs8XS+@days-ASUSLaptop \
--to=dayss1224@gmail.com \
--cc=ajones@ventanamicro.com \
--cc=alex@ghiti.fr \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atish.patra@linux.dev \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@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=pbonzini@redhat.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