From: Andrew Jones <ajones@ventanamicro.com>
To: Atish Patra <atishp@rivosinc.com>
Cc: Anup Patel <anup@brainfault.org>,
Atish Patra <atishp@atishpatra.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Shuah Khan <shuah@kernel.org>,
kvm@vger.kernel.org, kvm-riscv@lists.infradead.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 2/4] KVM: riscv: selftests: Do not start the counter in the overflow handler
Date: Thu, 27 Feb 2025 09:44:15 +0100 [thread overview]
Message-ID: <20250227-3799414d0651c86f6a815046@orel> (raw)
In-Reply-To: <20250226-kvm_pmu_improve-v1-2-74c058c2bf6d@rivosinc.com>
On Wed, Feb 26, 2025 at 12:25:04PM -0800, Atish Patra wrote:
> There is no need to start the counter in the overflow handler as we
> intend to trigger precise number of LCOFI interrupts through these
> tests. The overflow irq handler has already stopped the counter. As
> a result, the stop call from the test function may return already
> supported error which is fine as well.
^ stopped
>
> Signed-off-by: Atish Patra <atishp@rivosinc.com>
> ---
> tools/testing/selftests/kvm/riscv/sbi_pmu_test.c | 9 ++-------
> 1 file changed, 2 insertions(+), 7 deletions(-)
>
> diff --git a/tools/testing/selftests/kvm/riscv/sbi_pmu_test.c b/tools/testing/selftests/kvm/riscv/sbi_pmu_test.c
> index f45c0ecc902d..284bc80193bd 100644
> --- a/tools/testing/selftests/kvm/riscv/sbi_pmu_test.c
> +++ b/tools/testing/selftests/kvm/riscv/sbi_pmu_test.c
> @@ -118,8 +118,8 @@ static void stop_counter(unsigned long counter, unsigned long stop_flags)
>
> ret = sbi_ecall(SBI_EXT_PMU, SBI_EXT_PMU_COUNTER_STOP, counter, 1, stop_flags,
> 0, 0, 0);
> - __GUEST_ASSERT(ret.error == 0, "Unable to stop counter %ld error %ld\n",
> - counter, ret.error);
> + __GUEST_ASSERT(ret.error == 0 || ret.error == SBI_ERR_ALREADY_STOPPED,
> + "Unable to stop counter %ld error %ld\n", counter, ret.error);
> }
>
> static void guest_illegal_exception_handler(struct ex_regs *regs)
> @@ -137,7 +137,6 @@ static void guest_irq_handler(struct ex_regs *regs)
> unsigned int irq_num = regs->cause & ~CAUSE_IRQ_FLAG;
> struct riscv_pmu_snapshot_data *snapshot_data = snapshot_gva;
> unsigned long overflown_mask;
> - unsigned long counter_val = 0;
>
> /* Validate that we are in the correct irq handler */
> GUEST_ASSERT_EQ(irq_num, IRQ_PMU_OVF);
> @@ -151,10 +150,6 @@ static void guest_irq_handler(struct ex_regs *regs)
> GUEST_ASSERT(overflown_mask & 0x01);
>
> WRITE_ONCE(vcpu_shared_irq_count, vcpu_shared_irq_count+1);
> -
> - counter_val = READ_ONCE(snapshot_data->ctr_values[0]);
> - /* Now start the counter to mimick the real driver behavior */
> - start_counter(counter_in_use, SBI_PMU_START_FLAG_SET_INIT_VALUE, counter_val);
> }
>
> static unsigned long get_counter_index(unsigned long cbase, unsigned long cmask,
>
> --
> 2.43.0
>
Other than the commit message,
Reviewed-by: Andrew Jones <ajones@ventanamicro.com>
next prev parent reply other threads:[~2025-02-27 8:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 20:25 [PATCH 0/4] RISC-V KVM PMU fix and selftest improvement Atish Patra
2025-02-26 20:25 ` [PATCH 1/4] RISC-V: KVM: Disable the kernel perf counter during configure Atish Patra
2025-02-27 8:49 ` Andrew Jones
2025-02-26 20:25 ` [PATCH 2/4] KVM: riscv: selftests: Do not start the counter in the overflow handler Atish Patra
2025-02-27 8:44 ` Andrew Jones [this message]
2025-02-26 20:25 ` [PATCH 3/4] KVM: riscv: selftests: Change command line option Atish Patra
2025-02-27 8:08 ` Andrew Jones
2025-03-03 20:53 ` Atish Kumar Patra
2025-02-26 20:25 ` [PATCH 4/4] KVM: riscv: selftests: Allow number of interrupts to be configurable Atish Patra
2025-02-27 8:16 ` Andrew Jones
2025-03-03 21:27 ` Atish Kumar Patra
2025-03-04 8:58 ` 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=20250227-3799414d0651c86f6a815046@orel \
--to=ajones@ventanamicro.com \
--cc=anup@brainfault.org \
--cc=atishp@atishpatra.org \
--cc=atishp@rivosinc.com \
--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