From: Andrew Jones <ajones@ventanamicro.com>
To: kvm-riscv@lists.infradead.org
Subject: [PATCH v5 20/22] KVM: riscv: selftests: Add SBI PMU selftest
Date: Tue, 9 Apr 2024 10:01:48 +0200 [thread overview]
Message-ID: <20240409-dd055c3d08e027cf2a5cb4dc@orel> (raw)
In-Reply-To: <976411ab-6ddf-4b10-8e13-1575928415ce@rivosinc.com>
On Mon, Apr 08, 2024 at 05:37:19PM -0700, Atish Patra wrote:
> On 4/5/24 05:50, Andrew Jones wrote:
> > On Wed, Apr 03, 2024 at 01:04:49AM -0700, Atish Patra wrote:
> > ...
> > > +static void test_pmu_basic_sanity(void)
> > > +{
> > > + long out_val = 0;
> > > + bool probe;
> > > + struct sbiret ret;
> > > + int num_counters = 0, i;
> > > + union sbi_pmu_ctr_info ctrinfo;
> > > +
> > > + probe = guest_sbi_probe_extension(SBI_EXT_PMU, &out_val);
> > > + GUEST_ASSERT(probe && out_val == 1);
> > > +
> > > + num_counters = get_num_counters();
> > > +
> > > + for (i = 0; i < num_counters; i++) {
> > > + ret = sbi_ecall(SBI_EXT_PMU, SBI_EXT_PMU_COUNTER_GET_INFO, i,
> > > + 0, 0, 0, 0, 0);
> > > +
> > > + /* There can be gaps in logical counter indicies*/
> > > + if (ret.error)
> > > + continue;
> > > + GUEST_ASSERT_NE(ret.value, 0);
> > > +
> > > + ctrinfo.value = ret.value;
> > > +
> > > + /**
> > > + * Accesibillity check of hardware and read capability of firmware counters.
> >
> > Accessibility
> >
>
> Fixed it.
>
> > > + * The spec doesn't mandate any initial value. No need to check any value.
> > > + */
> > > + read_counter(i, ctrinfo);
> > > + }
> > > +
> > > + GUEST_DONE();
> > > +}
> > > +
> > > +static void run_vcpu(struct kvm_vcpu *vcpu)
> > > +{
> > > + struct ucall uc;
> > > +
> > > + vcpu_run(vcpu);
> > > + switch (get_ucall(vcpu, &uc)) {
> > > + case UCALL_ABORT:
> > > + REPORT_GUEST_ASSERT(uc);
> > > + break;
> > > + case UCALL_DONE:
> > > + case UCALL_SYNC:
> > > + break;
> > > + default:
> > > + TEST_FAIL("Unknown ucall %lu", uc.cmd);
> > > + break;
> > > + }
> > > +}
> > > +
> > > +void test_vm_destroy(struct kvm_vm *vm)
> > > +{
> > > + memset(ctrinfo_arr, 0, sizeof(union sbi_pmu_ctr_info) * RISCV_MAX_PMU_COUNTERS);
> > > + counter_mask_available = 0;
> > > + kvm_vm_free(vm);
> > > +}
> > > +
> > > +static void test_vm_basic_test(void *guest_code)
> > > +{
> > > + struct kvm_vm *vm;
> > > + struct kvm_vcpu *vcpu;
> > > +
> > > + vm = vm_create_with_one_vcpu(&vcpu, guest_code);
> > > + __TEST_REQUIRE(__vcpu_has_sbi_ext(vcpu, KVM_RISCV_SBI_EXT_PMU),
> > > + "SBI PMU not available, skipping test");
> > > + vm_init_vector_tables(vm);
> > > + /* Illegal instruction handler is required to verify read access without configuration */
> > > + vm_install_exception_handler(vm, EXC_INST_ILLEGAL, guest_illegal_exception_handler);
> >
> > I still don't see where the "verify" part is. The handler doesn't record
> > that it had to handle anything.
> >
>
> The objective of the test is to ensure that we get an illegal instruction
> without configuration.
This part I guessed.
> The presence of the registered exception handler is
> sufficient for that.
This part I disagree with. The handler may not be necessary and not run if
we don't get the ILL. Usually when I write tests like these I set a
boolean in the handler and check it after the instruction which should
have sent us there to make sure we did indeed go there.
>
> The verify part is that the test doesn't end up in a illegal instruction
> exception when you try to access a counter without configuring.
>
> Let me know if you think we should more verbose comment to explain the
> scenario.
>
With a boolean the test code will be mostly self documenting, but a short
comment saying why we expect the boolean to be set would be good too.
Thanks,
drew
>
> > > +
> > > + vcpu_init_vector_tables(vcpu);
> > > + run_vcpu(vcpu);
> > > +
> > > + test_vm_destroy(vm);
> > > +}
> > > +
> > > +static void test_vm_events_test(void *guest_code)
> > > +{
> > > + struct kvm_vm *vm = NULL;
> > > + struct kvm_vcpu *vcpu = NULL;
> > > +
> > > + vm = vm_create_with_one_vcpu(&vcpu, guest_code);
> > > + __TEST_REQUIRE(__vcpu_has_sbi_ext(vcpu, KVM_RISCV_SBI_EXT_PMU),
> > > + "SBI PMU not available, skipping test");
> > > + run_vcpu(vcpu);
> > > +
> > > + test_vm_destroy(vm);
> > > +}
> > > +
> > > +int main(void)
> > > +{
> > > + test_vm_basic_test(test_pmu_basic_sanity);
> > > + pr_info("SBI PMU basic test : PASS\n");
> > > +
> > > + test_vm_events_test(test_pmu_events);
> > > + pr_info("SBI PMU event verification test : PASS\n");
> > > +
> > > + return 0;
> > > +}
> > > --
> > > 2.34.1
> > >
> >
> > Thanks,
> > drew
>
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Jones <ajones@ventanamicro.com>
To: Atish Patra <atishp@rivosinc.com>
Cc: linux-kernel@vger.kernel.org, Anup Patel <anup@brainfault.org>,
Ajay Kaher <akaher@vmware.com>,
Alexandre Ghiti <alexghiti@rivosinc.com>,
Alexey Makhalov <amakhalov@vmware.com>,
Conor Dooley <conor.dooley@microchip.com>,
Juergen Gross <jgross@suse.com>,
kvm-riscv@lists.infradead.org, kvm@vger.kernel.org,
linux-kselftest@vger.kernel.org,
linux-riscv@lists.infradead.org,
Mark Rutland <mark.rutland@arm.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Shuah Khan <shuah@kernel.org>,
virtualization@lists.linux.dev,
VMware PV-Drivers Reviewers <pv-drivers@vmware.com>,
Will Deacon <will@kernel.org>,
x86@kernel.org
Subject: Re: [PATCH v5 20/22] KVM: riscv: selftests: Add SBI PMU selftest
Date: Tue, 9 Apr 2024 10:01:48 +0200 [thread overview]
Message-ID: <20240409-dd055c3d08e027cf2a5cb4dc@orel> (raw)
In-Reply-To: <976411ab-6ddf-4b10-8e13-1575928415ce@rivosinc.com>
On Mon, Apr 08, 2024 at 05:37:19PM -0700, Atish Patra wrote:
> On 4/5/24 05:50, Andrew Jones wrote:
> > On Wed, Apr 03, 2024 at 01:04:49AM -0700, Atish Patra wrote:
> > ...
> > > +static void test_pmu_basic_sanity(void)
> > > +{
> > > + long out_val = 0;
> > > + bool probe;
> > > + struct sbiret ret;
> > > + int num_counters = 0, i;
> > > + union sbi_pmu_ctr_info ctrinfo;
> > > +
> > > + probe = guest_sbi_probe_extension(SBI_EXT_PMU, &out_val);
> > > + GUEST_ASSERT(probe && out_val == 1);
> > > +
> > > + num_counters = get_num_counters();
> > > +
> > > + for (i = 0; i < num_counters; i++) {
> > > + ret = sbi_ecall(SBI_EXT_PMU, SBI_EXT_PMU_COUNTER_GET_INFO, i,
> > > + 0, 0, 0, 0, 0);
> > > +
> > > + /* There can be gaps in logical counter indicies*/
> > > + if (ret.error)
> > > + continue;
> > > + GUEST_ASSERT_NE(ret.value, 0);
> > > +
> > > + ctrinfo.value = ret.value;
> > > +
> > > + /**
> > > + * Accesibillity check of hardware and read capability of firmware counters.
> >
> > Accessibility
> >
>
> Fixed it.
>
> > > + * The spec doesn't mandate any initial value. No need to check any value.
> > > + */
> > > + read_counter(i, ctrinfo);
> > > + }
> > > +
> > > + GUEST_DONE();
> > > +}
> > > +
> > > +static void run_vcpu(struct kvm_vcpu *vcpu)
> > > +{
> > > + struct ucall uc;
> > > +
> > > + vcpu_run(vcpu);
> > > + switch (get_ucall(vcpu, &uc)) {
> > > + case UCALL_ABORT:
> > > + REPORT_GUEST_ASSERT(uc);
> > > + break;
> > > + case UCALL_DONE:
> > > + case UCALL_SYNC:
> > > + break;
> > > + default:
> > > + TEST_FAIL("Unknown ucall %lu", uc.cmd);
> > > + break;
> > > + }
> > > +}
> > > +
> > > +void test_vm_destroy(struct kvm_vm *vm)
> > > +{
> > > + memset(ctrinfo_arr, 0, sizeof(union sbi_pmu_ctr_info) * RISCV_MAX_PMU_COUNTERS);
> > > + counter_mask_available = 0;
> > > + kvm_vm_free(vm);
> > > +}
> > > +
> > > +static void test_vm_basic_test(void *guest_code)
> > > +{
> > > + struct kvm_vm *vm;
> > > + struct kvm_vcpu *vcpu;
> > > +
> > > + vm = vm_create_with_one_vcpu(&vcpu, guest_code);
> > > + __TEST_REQUIRE(__vcpu_has_sbi_ext(vcpu, KVM_RISCV_SBI_EXT_PMU),
> > > + "SBI PMU not available, skipping test");
> > > + vm_init_vector_tables(vm);
> > > + /* Illegal instruction handler is required to verify read access without configuration */
> > > + vm_install_exception_handler(vm, EXC_INST_ILLEGAL, guest_illegal_exception_handler);
> >
> > I still don't see where the "verify" part is. The handler doesn't record
> > that it had to handle anything.
> >
>
> The objective of the test is to ensure that we get an illegal instruction
> without configuration.
This part I guessed.
> The presence of the registered exception handler is
> sufficient for that.
This part I disagree with. The handler may not be necessary and not run if
we don't get the ILL. Usually when I write tests like these I set a
boolean in the handler and check it after the instruction which should
have sent us there to make sure we did indeed go there.
>
> The verify part is that the test doesn't end up in a illegal instruction
> exception when you try to access a counter without configuring.
>
> Let me know if you think we should more verbose comment to explain the
> scenario.
>
With a boolean the test code will be mostly self documenting, but a short
comment saying why we expect the boolean to be set would be good too.
Thanks,
drew
>
> > > +
> > > + vcpu_init_vector_tables(vcpu);
> > > + run_vcpu(vcpu);
> > > +
> > > + test_vm_destroy(vm);
> > > +}
> > > +
> > > +static void test_vm_events_test(void *guest_code)
> > > +{
> > > + struct kvm_vm *vm = NULL;
> > > + struct kvm_vcpu *vcpu = NULL;
> > > +
> > > + vm = vm_create_with_one_vcpu(&vcpu, guest_code);
> > > + __TEST_REQUIRE(__vcpu_has_sbi_ext(vcpu, KVM_RISCV_SBI_EXT_PMU),
> > > + "SBI PMU not available, skipping test");
> > > + run_vcpu(vcpu);
> > > +
> > > + test_vm_destroy(vm);
> > > +}
> > > +
> > > +int main(void)
> > > +{
> > > + test_vm_basic_test(test_pmu_basic_sanity);
> > > + pr_info("SBI PMU basic test : PASS\n");
> > > +
> > > + test_vm_events_test(test_pmu_events);
> > > + pr_info("SBI PMU event verification test : PASS\n");
> > > +
> > > + return 0;
> > > +}
> > > --
> > > 2.34.1
> > >
> >
> > Thanks,
> > drew
>
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Jones <ajones@ventanamicro.com>
To: Atish Patra <atishp@rivosinc.com>
Cc: linux-kernel@vger.kernel.org, Anup Patel <anup@brainfault.org>,
Ajay Kaher <akaher@vmware.com>,
Alexandre Ghiti <alexghiti@rivosinc.com>,
Alexey Makhalov <amakhalov@vmware.com>,
Conor Dooley <conor.dooley@microchip.com>,
Juergen Gross <jgross@suse.com>,
kvm-riscv@lists.infradead.org, kvm@vger.kernel.org,
linux-kselftest@vger.kernel.org,
linux-riscv@lists.infradead.org,
Mark Rutland <mark.rutland@arm.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Shuah Khan <shuah@kernel.org>,
virtualization@lists.linux.dev,
VMware PV-Drivers Reviewers <pv-drivers@vmware.com>,
Will Deacon <will@kernel.org>,
x86@kernel.org
Subject: Re: [PATCH v5 20/22] KVM: riscv: selftests: Add SBI PMU selftest
Date: Tue, 9 Apr 2024 10:01:48 +0200 [thread overview]
Message-ID: <20240409-dd055c3d08e027cf2a5cb4dc@orel> (raw)
In-Reply-To: <976411ab-6ddf-4b10-8e13-1575928415ce@rivosinc.com>
On Mon, Apr 08, 2024 at 05:37:19PM -0700, Atish Patra wrote:
> On 4/5/24 05:50, Andrew Jones wrote:
> > On Wed, Apr 03, 2024 at 01:04:49AM -0700, Atish Patra wrote:
> > ...
> > > +static void test_pmu_basic_sanity(void)
> > > +{
> > > + long out_val = 0;
> > > + bool probe;
> > > + struct sbiret ret;
> > > + int num_counters = 0, i;
> > > + union sbi_pmu_ctr_info ctrinfo;
> > > +
> > > + probe = guest_sbi_probe_extension(SBI_EXT_PMU, &out_val);
> > > + GUEST_ASSERT(probe && out_val == 1);
> > > +
> > > + num_counters = get_num_counters();
> > > +
> > > + for (i = 0; i < num_counters; i++) {
> > > + ret = sbi_ecall(SBI_EXT_PMU, SBI_EXT_PMU_COUNTER_GET_INFO, i,
> > > + 0, 0, 0, 0, 0);
> > > +
> > > + /* There can be gaps in logical counter indicies*/
> > > + if (ret.error)
> > > + continue;
> > > + GUEST_ASSERT_NE(ret.value, 0);
> > > +
> > > + ctrinfo.value = ret.value;
> > > +
> > > + /**
> > > + * Accesibillity check of hardware and read capability of firmware counters.
> >
> > Accessibility
> >
>
> Fixed it.
>
> > > + * The spec doesn't mandate any initial value. No need to check any value.
> > > + */
> > > + read_counter(i, ctrinfo);
> > > + }
> > > +
> > > + GUEST_DONE();
> > > +}
> > > +
> > > +static void run_vcpu(struct kvm_vcpu *vcpu)
> > > +{
> > > + struct ucall uc;
> > > +
> > > + vcpu_run(vcpu);
> > > + switch (get_ucall(vcpu, &uc)) {
> > > + case UCALL_ABORT:
> > > + REPORT_GUEST_ASSERT(uc);
> > > + break;
> > > + case UCALL_DONE:
> > > + case UCALL_SYNC:
> > > + break;
> > > + default:
> > > + TEST_FAIL("Unknown ucall %lu", uc.cmd);
> > > + break;
> > > + }
> > > +}
> > > +
> > > +void test_vm_destroy(struct kvm_vm *vm)
> > > +{
> > > + memset(ctrinfo_arr, 0, sizeof(union sbi_pmu_ctr_info) * RISCV_MAX_PMU_COUNTERS);
> > > + counter_mask_available = 0;
> > > + kvm_vm_free(vm);
> > > +}
> > > +
> > > +static void test_vm_basic_test(void *guest_code)
> > > +{
> > > + struct kvm_vm *vm;
> > > + struct kvm_vcpu *vcpu;
> > > +
> > > + vm = vm_create_with_one_vcpu(&vcpu, guest_code);
> > > + __TEST_REQUIRE(__vcpu_has_sbi_ext(vcpu, KVM_RISCV_SBI_EXT_PMU),
> > > + "SBI PMU not available, skipping test");
> > > + vm_init_vector_tables(vm);
> > > + /* Illegal instruction handler is required to verify read access without configuration */
> > > + vm_install_exception_handler(vm, EXC_INST_ILLEGAL, guest_illegal_exception_handler);
> >
> > I still don't see where the "verify" part is. The handler doesn't record
> > that it had to handle anything.
> >
>
> The objective of the test is to ensure that we get an illegal instruction
> without configuration.
This part I guessed.
> The presence of the registered exception handler is
> sufficient for that.
This part I disagree with. The handler may not be necessary and not run if
we don't get the ILL. Usually when I write tests like these I set a
boolean in the handler and check it after the instruction which should
have sent us there to make sure we did indeed go there.
>
> The verify part is that the test doesn't end up in a illegal instruction
> exception when you try to access a counter without configuring.
>
> Let me know if you think we should more verbose comment to explain the
> scenario.
>
With a boolean the test code will be mostly self documenting, but a short
comment saying why we expect the boolean to be set would be good too.
Thanks,
drew
>
> > > +
> > > + vcpu_init_vector_tables(vcpu);
> > > + run_vcpu(vcpu);
> > > +
> > > + test_vm_destroy(vm);
> > > +}
> > > +
> > > +static void test_vm_events_test(void *guest_code)
> > > +{
> > > + struct kvm_vm *vm = NULL;
> > > + struct kvm_vcpu *vcpu = NULL;
> > > +
> > > + vm = vm_create_with_one_vcpu(&vcpu, guest_code);
> > > + __TEST_REQUIRE(__vcpu_has_sbi_ext(vcpu, KVM_RISCV_SBI_EXT_PMU),
> > > + "SBI PMU not available, skipping test");
> > > + run_vcpu(vcpu);
> > > +
> > > + test_vm_destroy(vm);
> > > +}
> > > +
> > > +int main(void)
> > > +{
> > > + test_vm_basic_test(test_pmu_basic_sanity);
> > > + pr_info("SBI PMU basic test : PASS\n");
> > > +
> > > + test_vm_events_test(test_pmu_events);
> > > + pr_info("SBI PMU event verification test : PASS\n");
> > > +
> > > + return 0;
> > > +}
> > > --
> > > 2.34.1
> > >
> >
> > Thanks,
> > drew
>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2024-04-09 8:01 UTC|newest]
Thread overview: 175+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 8:04 [PATCH v5 00/22] RISC-V SBI v2.0 PMU improvements and Perf sampling in KVM guest Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-03 8:04 ` [PATCH v5 01/22] RISC-V: Fix the typo in Scountovf CSR name Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-04 10:56 ` Andrew Jones
2024-04-04 10:56 ` Andrew Jones
2024-04-04 10:56 ` Andrew Jones
2024-04-03 8:04 ` [PATCH v5 02/22] RISC-V: Add FIRMWARE_READ_HI definition Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-04 10:57 ` Andrew Jones
2024-04-04 10:57 ` Andrew Jones
2024-04-04 10:57 ` Andrew Jones
2024-04-03 8:04 ` [PATCH v5 03/22] drivers/perf: riscv: Read upper bits of a firmware counter Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-04 11:02 ` Andrew Jones
2024-04-04 11:02 ` Andrew Jones
2024-04-04 11:02 ` Andrew Jones
2024-04-09 0:04 ` Atish Patra
2024-04-09 0:04 ` Atish Patra
2024-04-09 0:04 ` Atish Patra
2024-04-03 8:04 ` [PATCH v5 04/22] drivers/perf: riscv: Use BIT macro for shifting operations Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-03 15:57 ` unsubscribe jonathan.oleson
2024-04-04 11:08 ` [PATCH v5 04/22] drivers/perf: riscv: Use BIT macro for shifting operations Andrew Jones
2024-04-04 11:08 ` Andrew Jones
2024-04-04 11:08 ` Andrew Jones
2024-04-09 0:20 ` Atish Patra
2024-04-09 0:20 ` Atish Patra
2024-04-09 0:20 ` Atish Patra
2024-04-03 8:04 ` [PATCH v5 05/22] RISC-V: Add SBI PMU snapshot definitions Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-04 11:14 ` Andrew Jones
2024-04-04 11:14 ` Andrew Jones
2024-04-04 11:14 ` Andrew Jones
2024-04-03 8:04 ` [PATCH v5 06/22] drivers/perf: riscv: Implement SBI PMU snapshot function Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-04 11:52 ` Andrew Jones
2024-04-04 11:52 ` Andrew Jones
2024-04-04 11:52 ` Andrew Jones
2024-04-10 22:29 ` Atish Patra
2024-04-10 22:29 ` Atish Patra
2024-04-10 22:29 ` Atish Patra
2024-04-11 7:45 ` Andrew Jones
2024-04-11 7:45 ` Andrew Jones
2024-04-11 7:45 ` Andrew Jones
2024-04-04 12:01 ` Andrew Jones
2024-04-04 12:01 ` Andrew Jones
2024-04-04 12:01 ` Andrew Jones
2024-04-09 0:21 ` Atish Patra
2024-04-09 0:21 ` Atish Patra
2024-04-09 0:21 ` Atish Patra
2024-04-03 8:04 ` [PATCH v5 07/22] drivers/perf: riscv: Fix counter mask iteration for RV32 Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-04 11:55 ` Andrew Jones
2024-04-04 11:55 ` Andrew Jones
2024-04-04 11:55 ` Andrew Jones
2024-04-03 8:04 ` [PATCH v5 08/22] RISC-V: KVM: Fix the initial sample period value Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-04 11:57 ` Andrew Jones
2024-04-04 11:57 ` Andrew Jones
2024-04-04 11:57 ` Andrew Jones
2024-04-03 8:04 ` [PATCH v5 09/22] RISC-V: KVM: Rename the SBI_STA_SHMEM_DISABLE to a generic name Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-04 11:59 ` Andrew Jones
2024-04-04 11:59 ` Andrew Jones
2024-04-04 11:59 ` Andrew Jones
2024-04-03 8:04 ` [PATCH v5 10/22] RISC-V: KVM: No need to update the counter value during reset Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-03 8:04 ` [PATCH v5 11/22] RISC-V: KVM: No need to exit to the user space if perf event failed Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-04 12:19 ` Andrew Jones
2024-04-04 12:19 ` Andrew Jones
2024-04-04 12:19 ` Andrew Jones
2024-04-03 8:04 ` [PATCH v5 12/22] RISC-V: KVM: Implement SBI PMU Snapshot feature Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-05 11:23 ` Andrew Jones
2024-04-05 11:23 ` Andrew Jones
2024-04-05 11:23 ` Andrew Jones
2024-04-09 0:33 ` Atish Patra
2024-04-09 0:33 ` Atish Patra
2024-04-09 0:33 ` Atish Patra
2024-04-03 8:04 ` [PATCH v5 13/22] RISC-V: KVM: Add perf sampling support for guests Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-05 11:36 ` Andrew Jones
2024-04-05 11:36 ` Andrew Jones
2024-04-05 11:36 ` Andrew Jones
2024-04-03 8:04 ` [PATCH v5 14/22] RISC-V: KVM: Support 64 bit firmware counters on RV32 Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-05 12:10 ` Andrew Jones
2024-04-05 12:10 ` Andrew Jones
2024-04-05 12:10 ` Andrew Jones
2024-04-03 8:04 ` [PATCH v5 15/22] RISC-V: KVM: Improve firmware counter read function Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-05 12:12 ` Andrew Jones
2024-04-05 12:12 ` Andrew Jones
2024-04-05 12:12 ` Andrew Jones
2024-04-03 8:04 ` [PATCH v5 16/22] KVM: riscv: selftests: Move sbi definitions to its own header file Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-05 12:16 ` Andrew Jones
2024-04-05 12:16 ` Andrew Jones
2024-04-05 12:16 ` Andrew Jones
2024-04-03 8:04 ` [PATCH v5 17/22] KVM: riscv: selftests: Add helper functions for extension checks Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-05 12:17 ` Andrew Jones
2024-04-05 12:17 ` Andrew Jones
2024-04-05 12:17 ` Andrew Jones
2024-04-03 8:04 ` [PATCH v5 18/22] KVM: riscv: selftests: Add Sscofpmf to get-reg-list test Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-03 8:04 ` [PATCH v5 19/22] KVM: riscv: selftests: Add SBI PMU extension definitions Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-05 12:20 ` Andrew Jones
2024-04-05 12:20 ` Andrew Jones
2024-04-05 12:20 ` Andrew Jones
2024-04-03 8:04 ` [PATCH v5 20/22] KVM: riscv: selftests: Add SBI PMU selftest Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-05 12:50 ` Andrew Jones
2024-04-05 12:50 ` Andrew Jones
2024-04-05 12:50 ` Andrew Jones
2024-04-09 0:37 ` Atish Patra
2024-04-09 0:37 ` Atish Patra
2024-04-09 0:37 ` Atish Patra
2024-04-09 8:01 ` Andrew Jones [this message]
2024-04-09 8:01 ` Andrew Jones
2024-04-09 8:01 ` Andrew Jones
2024-04-09 22:11 ` Atish Kumar Patra
2024-04-09 22:11 ` Atish Kumar Patra
2024-04-09 22:11 ` Atish Kumar Patra
2024-04-03 8:04 ` [PATCH v5 21/22] KVM: riscv: selftests: Add a test for PMU snapshot functionality Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-05 13:11 ` Andrew Jones
2024-04-05 13:11 ` Andrew Jones
2024-04-05 13:11 ` Andrew Jones
2024-04-09 22:52 ` Atish Patra
2024-04-09 22:52 ` Atish Patra
2024-04-09 22:52 ` Atish Patra
2024-04-10 7:10 ` Andrew Jones
2024-04-10 7:10 ` Andrew Jones
2024-04-10 7:10 ` Andrew Jones
2024-04-10 7:28 ` Atish Patra
2024-04-10 7:28 ` Atish Patra
2024-04-10 7:28 ` Atish Patra
2024-04-10 7:54 ` Andrew Jones
2024-04-10 7:54 ` Andrew Jones
2024-04-10 7:54 ` Andrew Jones
2024-04-03 8:04 ` [PATCH v5 22/22] KVM: riscv: selftests: Add a test for counter overflow Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-03 8:04 ` Atish Patra
2024-04-05 13:23 ` Andrew Jones
2024-04-05 13:23 ` Andrew Jones
2024-04-05 13:23 ` Andrew Jones
2024-04-09 23:47 ` Atish Patra
2024-04-09 23:47 ` Atish Patra
2024-04-09 23:47 ` 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=20240409-dd055c3d08e027cf2a5cb4dc@orel \
--to=ajones@ventanamicro.com \
--cc=kvm-riscv@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.