All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Clément Léger" <cleger@rivosinc.com>
To: Andrew Jones <andrew.jones@linux.dev>
Cc: kvm@vger.kernel.org, kvm-riscv@lists.infradead.org,
	Andrew Jones <ajones@ventanamicro.com>,
	Ved Shanbhogue <ved@rivosinc.com>
Subject: Re: [PATCH 0/3] riscv: Add double trap testing
Date: Tue, 3 Jun 2025 09:52:52 +0200	[thread overview]
Message-ID: <9fbee56b-988d-4557-a8c5-e0c85d146a39@rivosinc.com> (raw)
In-Reply-To: <20250603-ae5b10c63b6ac83d206343fa@orel>



On 03/06/2025 09:10, Andrew Jones wrote:
> 
> Hi Clement,
> 
> You may want to add format.subjectprefix = kvm-unit-tests to your git
> config, since it's missing from this series.

Hi Drew,

Yeah sorry forgot the prefix !

> 
> On Fri, May 23, 2025 at 09:53:07AM +0200, Clément Léger wrote:
>> Add a test that triggers double trap and verify that it's behavior
>> conforms to the spec. Also use SSE to verify that an SSE event is
>> correctly sent upon double trap.
>>
>> In order to run this test, one can use the following command using an
>> upstream version of OpenSBI:
>>
>> $ qemu-system-riscv64 \
>> 	-M virt \
>> 	-cpu max \
>> 	-nographic -serial mon:stdio \
>> 	-bios <opensbi>/fw_dynamic.bin \
>> 	-kernel riscv/isa-dbltrp.flat
> 
> You can also do
> 
> $ QEMU=qemu-system-riscv64 FIRMWARE_OVERRIDE=<opensbi>/fw_dynamic.bin ./riscv-run riscv/isa-dbltrp.flat

Oh yeah I even used that as well...

Thanks,

Clément

> 
> Thanks,
> drew
> 
>>
>> Clément Léger (3):
>>   lib/riscv: export FWFT functions
>>   lib/riscv: clear SDT when entering exception handling
>>   riscv: Add ISA double trap extension testing
>>
>>  riscv/Makefile      |   1 +
>>  lib/riscv/asm/csr.h |   1 +
>>  lib/riscv/asm/sbi.h |   5 ++
>>  lib/riscv/sbi.c     |  20 +++++
>>  riscv/cstart.S      |   9 ++-
>>  riscv/isa-dbltrp.c  | 189 ++++++++++++++++++++++++++++++++++++++++++++
>>  riscv/sbi-fwft.c    |  49 ++++--------
>>  riscv/unittests.cfg |   5 ++
>>  8 files changed, 240 insertions(+), 39 deletions(-)
>>  create mode 100644 riscv/isa-dbltrp.c
>>
>> -- 
>> 2.49.0
>>


-- 
kvm-riscv mailing list
kvm-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kvm-riscv

WARNING: multiple messages have this Message-ID (diff)
From: "Clément Léger" <cleger@rivosinc.com>
To: Andrew Jones <andrew.jones@linux.dev>
Cc: kvm@vger.kernel.org, kvm-riscv@lists.infradead.org,
	Andrew Jones <ajones@ventanamicro.com>,
	Ved Shanbhogue <ved@rivosinc.com>
Subject: Re: [PATCH 0/3] riscv: Add double trap testing
Date: Tue, 3 Jun 2025 09:52:52 +0200	[thread overview]
Message-ID: <9fbee56b-988d-4557-a8c5-e0c85d146a39@rivosinc.com> (raw)
In-Reply-To: <20250603-ae5b10c63b6ac83d206343fa@orel>



On 03/06/2025 09:10, Andrew Jones wrote:
> 
> Hi Clement,
> 
> You may want to add format.subjectprefix = kvm-unit-tests to your git
> config, since it's missing from this series.

Hi Drew,

Yeah sorry forgot the prefix !

> 
> On Fri, May 23, 2025 at 09:53:07AM +0200, Clément Léger wrote:
>> Add a test that triggers double trap and verify that it's behavior
>> conforms to the spec. Also use SSE to verify that an SSE event is
>> correctly sent upon double trap.
>>
>> In order to run this test, one can use the following command using an
>> upstream version of OpenSBI:
>>
>> $ qemu-system-riscv64 \
>> 	-M virt \
>> 	-cpu max \
>> 	-nographic -serial mon:stdio \
>> 	-bios <opensbi>/fw_dynamic.bin \
>> 	-kernel riscv/isa-dbltrp.flat
> 
> You can also do
> 
> $ QEMU=qemu-system-riscv64 FIRMWARE_OVERRIDE=<opensbi>/fw_dynamic.bin ./riscv-run riscv/isa-dbltrp.flat

Oh yeah I even used that as well...

Thanks,

Clément

> 
> Thanks,
> drew
> 
>>
>> Clément Léger (3):
>>   lib/riscv: export FWFT functions
>>   lib/riscv: clear SDT when entering exception handling
>>   riscv: Add ISA double trap extension testing
>>
>>  riscv/Makefile      |   1 +
>>  lib/riscv/asm/csr.h |   1 +
>>  lib/riscv/asm/sbi.h |   5 ++
>>  lib/riscv/sbi.c     |  20 +++++
>>  riscv/cstart.S      |   9 ++-
>>  riscv/isa-dbltrp.c  | 189 ++++++++++++++++++++++++++++++++++++++++++++
>>  riscv/sbi-fwft.c    |  49 ++++--------
>>  riscv/unittests.cfg |   5 ++
>>  8 files changed, 240 insertions(+), 39 deletions(-)
>>  create mode 100644 riscv/isa-dbltrp.c
>>
>> -- 
>> 2.49.0
>>


  reply	other threads:[~2025-06-03  7:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-23  7:53 [PATCH 0/3] riscv: Add double trap testing Clément Léger
2025-05-23  7:53 ` Clément Léger
2025-05-23  7:53 ` [PATCH 1/3] lib/riscv: export FWFT functions Clément Léger
2025-05-23  7:53   ` Clément Léger
2025-06-03  7:14   ` Andrew Jones
2025-06-03  7:14     ` Andrew Jones
2025-05-23  7:53 ` [PATCH 2/3] lib/riscv: clear SDT when entering exception handling Clément Léger
2025-05-23  7:53   ` Clément Léger
2025-06-03  8:16   ` Andrew Jones
2025-06-03  8:16     ` Andrew Jones
2025-06-03  8:22     ` Clément Léger
2025-06-03  8:22       ` Clément Léger
2025-05-23  7:53 ` [PATCH 3/3] riscv: Add ISA double trap extension testing Clément Léger
2025-05-23  7:53   ` Clément Léger
2025-06-03  9:09   ` Andrew Jones
2025-06-03  9:09     ` Andrew Jones
2025-06-03  9:39     ` Clément Léger
2025-06-03  9:39       ` Clément Léger
2025-06-03  7:10 ` [PATCH 0/3] riscv: Add double trap testing Andrew Jones
2025-06-03  7:10   ` Andrew Jones
2025-06-03  7:52   ` Clément Léger [this message]
2025-06-03  7:52     ` Clément Léger

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=9fbee56b-988d-4557-a8c5-e0c85d146a39@rivosinc.com \
    --to=cleger@rivosinc.com \
    --cc=ajones@ventanamicro.com \
    --cc=andrew.jones@linux.dev \
    --cc=kvm-riscv@lists.infradead.org \
    --cc=kvm@vger.kernel.org \
    --cc=ved@rivosinc.com \
    /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.