From: Atish Patra <atish.patra@linux.dev>
To: Andrew Jones <ajones@ventanamicro.com>
Cc: Anup Patel <anup@brainfault.org>,
Atish Patra <atishp@atishpatra.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Shuah Khan <shuah@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Alexandre Ghiti <alex@ghiti.fr>,
kvm@vger.kernel.org, kvm-riscv@lists.infradead.org,
linux-riscv@lists.infradead.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/3] KVM: riscv: selftests: Decode stval to identify exact exception type
Date: Wed, 30 Apr 2025 00:20:48 -0700 [thread overview]
Message-ID: <a6cb0396-4bc5-4215-9e2e-a68be83c1c94@linux.dev> (raw)
In-Reply-To: <20250430-b40cd14818cc9264506e61f2@orel>
On 4/30/25 12:09 AM, Andrew Jones wrote:
> On Tue, Apr 29, 2025 at 05:18:46PM -0700, Atish Patra wrote:
>> Currently, the sbi_pmu_test continues if the exception type is illegal
>> instruction because access to hpmcounter will generate that. However
>> illegal instruction exception may occur due to the other reasons
>> which should result in test assertion.
>>
>> Use the stval to decode the exact type of instructions and which csrs are
>> being accessed if it is csr access instructions. Assert in all cases
>> except if it is a csr access instructions that access valid PMU related
>> registers.
>>
>> Reviewed-by: Anup Patel <anup@brainfault.org>
>> Signed-off-by: Atish Patra <atishp@rivosinc.com>
>> ---
>> .../testing/selftests/kvm/include/riscv/processor.h | 13 +++++++++++++
>> tools/testing/selftests/kvm/riscv/sbi_pmu_test.c | 20 ++++++++++++++++++++
>> 2 files changed, 33 insertions(+)
>>
>> diff --git a/tools/testing/selftests/kvm/include/riscv/processor.h b/tools/testing/selftests/kvm/include/riscv/processor.h
>> index 1b5aef87de0f..162f303d9daa 100644
>> --- a/tools/testing/selftests/kvm/include/riscv/processor.h
>> +++ b/tools/testing/selftests/kvm/include/riscv/processor.h
>> @@ -11,6 +11,19 @@
>> #include <asm/csr.h>
>> #include "kvm_util.h"
>>
>> +#define INSN_OPCODE_MASK 0x007c
>> +#define INSN_OPCODE_SHIFT 2
>> +#define INSN_OPCODE_SYSTEM 28
>> +
>> +#define INSN_MASK_FUNCT3 0x7000
>> +#define INSN_SHIFT_FUNCT3 12
>> +
>> +#define INSN_CSR_MASK 0xfff00000
>> +#define INSN_CSR_SHIFT 20
>> +
>> +#define GET_RM(insn) (((insn) & INSN_MASK_FUNCT3) >> INSN_SHIFT_FUNCT3)
>> +#define GET_CSR_NUM(insn) (((insn) & INSN_CSR_MASK) >> INSN_CSR_SHIFT)
>> +
>> static inline uint64_t __kvm_reg_id(uint64_t type, uint64_t subtype,
>> uint64_t idx, uint64_t size)
>> {
>> diff --git a/tools/testing/selftests/kvm/riscv/sbi_pmu_test.c b/tools/testing/selftests/kvm/riscv/sbi_pmu_test.c
>> index 6e66833e5941..3c47268df262 100644
>> --- a/tools/testing/selftests/kvm/riscv/sbi_pmu_test.c
>> +++ b/tools/testing/selftests/kvm/riscv/sbi_pmu_test.c
>> @@ -130,9 +130,29 @@ static void stop_counter(unsigned long counter, unsigned long stop_flags)
>>
>> static void guest_illegal_exception_handler(struct pt_regs *regs)
>> {
>> + unsigned long insn;
>> + int opcode, csr_num, funct3;
>> +
>> __GUEST_ASSERT(regs->cause == EXC_INST_ILLEGAL,
>> "Unexpected exception handler %lx\n", regs->cause);
>>
>> + insn = regs->badaddr;
>> + opcode = (insn & INSN_OPCODE_MASK) >> INSN_OPCODE_SHIFT;
>> + __GUEST_ASSERT(opcode == INSN_OPCODE_SYSTEM,
>> + "Unexpected instruction with opcode 0x%x insn 0x%lx\n", opcode, insn);
>> +
>> + csr_num = GET_CSR_NUM(insn);
>> + funct3 = GET_RM(insn);
>> + /* Validate if it is a CSR read/write operation */
>> + __GUEST_ASSERT(funct3 <= 7 && (funct3 != 0 && funct3 != 4),
>> + "Unexpected system opcode with funct3 0x%x csr_num 0x%x\n",
>> + funct3, csr_num);
>> +
>> + /* Validate if it is a HPMCOUNTER CSR operation */
>> + __GUEST_ASSERT((csr_num >= CSR_CYCLE && csr_num <= CSR_HPMCOUNTER31) ||
>> + (csr_num >= CSR_CYCLEH && csr_num <= CSR_HPMCOUNTER31H),
> We should never get csr accesses to the rv32 high registers since we only
> support 64-bit.
Sure. I will remove that along with CSR_CYCLEH in pmu_csr_read_num.
>> + "Unexpected csr_num 0x%x\n", csr_num);
>> +
>> illegal_handler_invoked = true;
>> /* skip the trapping instruction */
>> regs->epc += 4;
>>
>> --
>> 2.43.0
>>
> Otherwise,
>
> Reviewed-by: Andrew Jones <ajones@ventanamicro.com>
next prev parent reply other threads:[~2025-04-30 7:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 0:18 [PATCH v2 0/3] RISC-V KVM selftests improvements Atish Patra
2025-04-30 0:18 ` [PATCH v2 1/3] KVM: riscv: selftests: Align the trap information wiht pt_regs Atish Patra
2025-04-30 7:05 ` Andrew Jones
2025-04-30 7:18 ` Atish Patra
2025-04-30 0:18 ` [PATCH v2 2/3] KVM: riscv: selftests: Decode stval to identify exact exception type Atish Patra
2025-04-30 7:09 ` Andrew Jones
2025-04-30 7:20 ` Atish Patra [this message]
2025-04-30 0:18 ` [PATCH v2 3/3] KVM: riscv: selftests: Add vector extension tests Atish Patra
2025-04-30 7:17 ` Andrew Jones
2025-04-30 7:22 ` Atish Patra
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=a6cb0396-4bc5-4215-9e2e-a68be83c1c94@linux.dev \
--to=atish.patra@linux.dev \
--cc=ajones@ventanamicro.com \
--cc=alex@ghiti.fr \
--cc=anup@brainfault.org \
--cc=atishp@atishpatra.org \
--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;
as well as URLs for NNTP newsgroup(s).