From: Huacai Chen <chenhuacai@kernel.org>
To: Song Gao <gaosong@loongson.cn>
Cc: maobibo@loongson.cn, loongarch@lists.linux.dev,
kernel@xen0n.name, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] KVM: LoongArch: selftests: Add PMU test cases
Date: Wed, 8 Apr 2026 18:31:09 +0800 [thread overview]
Message-ID: <CAAhV-H7FuX6AE3TiC_O1ZEs=HRemDoZx9LOGC42q+6q8QF+8eA@mail.gmail.com> (raw)
In-Reply-To: <20260310092657.1023650-1-gaosong@loongson.cn>
Applied, thanks.
Huacai
On Tue, Mar 10, 2026 at 5:52 PM Song Gao <gaosong@loongson.cn> wrote:
>
> This series adds KVM selftests for the LoongArch Performance Monitoring Unit (PMU),
> covering basic event counting and overflow interrupt functionality.
>
> Thanks.
> Song Gao
>
> Song Gao (3):
> KVM: LoongArch: selftests: Add cpucfg read/write helpers
> KVM: LoongArch: selftests: Add basic PMU event counting test
> KVM: LoongArch: selftests: Add PMU overflow interrupt test
>
> tools/testing/selftests/kvm/Makefile.kvm | 1 +
> .../selftests/kvm/include/loongarch/pmu.h | 66 ++++++
> .../kvm/include/loongarch/processor.h | 15 ++
> .../selftests/kvm/lib/loongarch/processor.c | 14 +-
> .../selftests/kvm/loongarch/guest_pmu_test.c | 205 ++++++++++++++++++
> 5 files changed, 300 insertions(+), 1 deletion(-)
> create mode 100644 tools/testing/selftests/kvm/include/loongarch/pmu.h
> create mode 100644 tools/testing/selftests/kvm/loongarch/guest_pmu_test.c
>
> --
> 2.47.3
>
prev parent reply other threads:[~2026-04-08 10:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 9:26 [PATCH 0/3] KVM: LoongArch: selftests: Add PMU test cases Song Gao
2026-03-10 9:26 ` [PATCH 1/3] KVM: LoongArch: selftests: Add cpucfg read/write helpers Song Gao
2026-03-10 9:26 ` [PATCH 2/3] KVM: LoongArch: selftests: Add basic PMU event counting test Song Gao
2026-03-10 9:26 ` [PATCH 3/3] KVM: LoongArch: selftests: Add PMU overflow interrupt test Song Gao
2026-04-08 10:31 ` Huacai Chen [this message]
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='CAAhV-H7FuX6AE3TiC_O1ZEs=HRemDoZx9LOGC42q+6q8QF+8eA@mail.gmail.com' \
--to=chenhuacai@kernel.org \
--cc=gaosong@loongson.cn \
--cc=kernel@xen0n.name \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=maobibo@loongson.cn \
/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).