Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Andrew Jones <andrew.jones@linux.dev>
To: kvm@vger.kernel.org, kvm-riscv@lists.infradead.org
Cc: atishp@rivosinc.com, cade.richard@berkeley.edu, jamestiotio@gmail.com
Subject: Re: [kvm-unit-tests PATCH 0/4] riscv: sbi: More DBCN tests
Date: Mon, 12 Aug 2024 16:18:08 +0200	[thread overview]
Message-ID: <20240812-067579d76c30484592009ced@orel> (raw)
In-Reply-To: <20240812141354.119889-6-andrew.jones@linux.dev>

On Mon, Aug 12, 2024 at 04:13:55PM GMT, Andrew Jones wrote:
> The current DBCN tests found a several bugs and with high address
> support for rv32 we were able to find even more. Add the new tests
> which checks high use page boundary crossing. The first three patches
> a various improvements to the SBI tests.
> 
> Based on riscv/queue, https://gitlab.com/jones-drew/kvm-unit-tests/-/commits/riscv%2Fqueue
> 
> Andrew Jones (4):
>   riscv: sbi: dbcn: Output return values
>   riscv: sbi: Use strtoul to avoid overflow
>   riscv: sbi: Prefix several environment variables with SBI
>   riscv: sbi: dbcn: Add high address tests
> 
>  riscv/sbi.c | 163 +++++++++++++++++++++++++++++++++++++++++-----------
>  1 file changed, 131 insertions(+), 32 deletions(-)
> 
> -- 
> 2.45.2
>

Queued on riscv/sbi, https://gitlab.com/jones-drew/kvm-unit-tests/-/commits/riscv%2Fsbi

      parent reply	other threads:[~2024-08-12 14:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-12 14:13 [kvm-unit-tests PATCH 0/4] riscv: sbi: More DBCN tests Andrew Jones
2024-08-12 14:13 ` [kvm-unit-tests PATCH 1/4] riscv: sbi: dbcn: Output return values Andrew Jones
2024-08-12 14:13 ` [kvm-unit-tests PATCH 2/4] riscv: sbi: Use strtoul to avoid overflow Andrew Jones
2024-08-12 14:13 ` [kvm-unit-tests PATCH 3/4] riscv: sbi: Prefix several environment variables with SBI Andrew Jones
2024-08-12 14:13 ` [kvm-unit-tests PATCH 4/4] riscv: sbi: dbcn: Add high address tests Andrew Jones
2024-08-12 14:18 ` Andrew Jones [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=20240812-067579d76c30484592009ced@orel \
    --to=andrew.jones@linux.dev \
    --cc=atishp@rivosinc.com \
    --cc=cade.richard@berkeley.edu \
    --cc=jamestiotio@gmail.com \
    --cc=kvm-riscv@lists.infradead.org \
    --cc=kvm@vger.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