From: Andrew Jones <andrew.jones@linux.dev>
To: kvm-riscv@lists.infradead.org, kvm@vger.kernel.org
Cc: cleger@rivosinc.com, atishp@rivosinc.com, akshaybehl231@gmail.com
Subject: Re: [kvm-unit-tests PATCH 0/3] riscv: sbi: Ensure we can pass with any opensbi
Date: Sat, 22 Mar 2025 11:47:14 +0100 [thread overview]
Message-ID: <20250322-58f9c16024c28e345fd7ed02@orel> (raw)
In-Reply-To: <20250321165403.57859-5-andrew.jones@linux.dev>
On Fri, Mar 21, 2025 at 05:54:04PM +0100, Andrew Jones wrote:
> At some point CI will update the version of QEMU it uses. If the version
> selected includes an opensbi that doesn't have all the fixes for current
> tests, then CI will start failing for riscv. Guard against that by using
> kfail for known opensbi failures. We only kfail for opensbi and for its
> versions less than 1.7, though, as we expect everything to be fixed then.
>
> Andrew Jones (3):
> lib/riscv: Also provide sbiret impl functions
> riscv: sbi: Add kfail versions of sbiret_report functions
> riscv: sbi: Use kfail for known opensbi failures
>
> lib/riscv/asm/sbi.h | 6 ++++--
> lib/riscv/sbi.c | 18 ++++++++++++++----
> riscv/sbi-fwft.c | 20 +++++++++++++-------
> riscv/sbi-sse.c | 4 ++--
> riscv/sbi-tests.h | 20 +++++++++++++++-----
> riscv/sbi.c | 6 ++++--
> 6 files changed, 52 insertions(+), 22 deletions(-)
>
> --
> 2.48.1
>
Merged.
Thanks,
drew
prev parent reply other threads:[~2025-03-22 10:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 16:54 [kvm-unit-tests PATCH 0/3] riscv: sbi: Ensure we can pass with any opensbi Andrew Jones
2025-03-21 16:54 ` [kvm-unit-tests PATCH 1/3] lib/riscv: Also provide sbiret impl functions Andrew Jones
2025-03-21 20:15 ` Clément Léger
2025-03-21 16:54 ` [kvm-unit-tests PATCH 2/3] riscv: sbi: Add kfail versions of sbiret_report functions Andrew Jones
2025-03-21 20:17 ` Clément Léger
2025-03-21 16:54 ` [kvm-unit-tests PATCH 3/3] riscv: sbi: Use kfail for known opensbi failures Andrew Jones
2025-03-21 20:22 ` Clément Léger
2025-03-22 7:38 ` Andrew Jones
2025-03-22 10:47 ` 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=20250322-58f9c16024c28e345fd7ed02@orel \
--to=andrew.jones@linux.dev \
--cc=akshaybehl231@gmail.com \
--cc=atishp@rivosinc.com \
--cc=cleger@rivosinc.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