From: Anup Patel <anup@brainfault.org>
To: Andrew Jones <ajones@ventanamicro.com>
Cc: kvm-riscv@lists.infradead.org, linux-riscv@lists.infradead.org,
atishp@atishpatra.org, palmer@dabbelt.com, haibo1.xu@intel.com
Subject: Re: [PATCH v2 0/6] RISC-V: KVM: Make SBI uapi consistent with ISA uapi
Date: Thu, 14 Dec 2023 10:49:15 +0530 [thread overview]
Message-ID: <CAAhSdy1N2BaExXsTJnxn=UJ4G5cLQv0WY8mK41miZA9WNFO26w@mail.gmail.com> (raw)
In-Reply-To: <20231213170951.93453-8-ajones@ventanamicro.com>
On Wed, Dec 13, 2023 at 10:39 PM Andrew Jones <ajones@ventanamicro.com> wrote:
>
> SBI extension UAPI is currently almost the same as the ISA extension
> UAPI. This series closes the remaining gap by ensuring when an SBI
> extension is not available that its register returns ENOENT when
> accessed by userspace. We also drop the SBI multi registers from
> get-reg-list (ISA multi registers aren't there either) and make
> several improvements to the get-reg-list kselftest.
>
> This series is based on Anup's riscv_kvm_more_exts_v1 branch.
>
> Based on kvm-riscv/riscv_kvm_queue
>
> v2:
> - Rebased on kvm-riscv/riscv_kvm_queue which is based on v6.7-rc5
>
> Thanks,
> drew
>
>
> Andrew Jones (6):
> RISC-V: KVM: Don't add SBI multi regs in get-reg-list
> KVM: riscv: selftests: Drop SBI multi registers
> RISC-V: KVM: Make SBI uapi consistent with ISA uapi
> KVM: riscv: selftests: Add RISCV_SBI_EXT_REG
> KVM: riscv: selftests: Use register subtypes
> RISC-V: KVM: selftests: Treat SBI ext regs like ISA ext regs
Queued this series for Linux-6.8
Thanks,
Anup
>
> arch/riscv/include/asm/kvm_vcpu_sbi.h | 10 +-
> arch/riscv/kvm/vcpu_onereg.c | 53 ++---
> arch/riscv/kvm/vcpu_sbi.c | 75 +++---
> arch/riscv/kvm/vcpu_sbi_replace.c | 2 +-
> .../selftests/kvm/include/kvm_util_base.h | 1 +
> .../selftests/kvm/include/riscv/processor.h | 40 ++--
> .../selftests/kvm/lib/riscv/processor.c | 4 +-
> .../selftests/kvm/riscv/get-reg-list.c | 220 +++++++++++++-----
> 8 files changed, 254 insertions(+), 151 deletions(-)
>
> --
> 2.43.0
>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2023-12-14 5:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 17:09 [PATCH v2 0/6] RISC-V: KVM: Make SBI uapi consistent with ISA uapi Andrew Jones
2023-12-13 17:09 ` [PATCH v2 1/6] RISC-V: KVM: Don't add SBI multi regs in get-reg-list Andrew Jones
2023-12-13 17:23 ` Anup Patel
2023-12-13 17:09 ` [PATCH v2 2/6] KVM: riscv: selftests: Drop SBI multi registers Andrew Jones
2023-12-13 17:24 ` Anup Patel
2023-12-13 17:09 ` [PATCH v2 3/6] RISC-V: KVM: Make SBI uapi consistent with ISA uapi Andrew Jones
2023-12-13 17:35 ` Anup Patel
2023-12-13 17:09 ` [PATCH v2 4/6] KVM: riscv: selftests: Add RISCV_SBI_EXT_REG Andrew Jones
2023-12-13 17:36 ` Anup Patel
2023-12-13 17:09 ` [PATCH v2 5/6] KVM: riscv: selftests: Use register subtypes Andrew Jones
2023-12-13 17:39 ` Anup Patel
2023-12-13 17:09 ` [PATCH v2 6/6] RISC-V: KVM: selftests: Treat SBI ext regs like ISA ext regs Andrew Jones
2023-12-13 17:42 ` Anup Patel
2023-12-14 5:19 ` Anup Patel [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='CAAhSdy1N2BaExXsTJnxn=UJ4G5cLQv0WY8mK41miZA9WNFO26w@mail.gmail.com' \
--to=anup@brainfault.org \
--cc=ajones@ventanamicro.com \
--cc=atishp@atishpatra.org \
--cc=haibo1.xu@intel.com \
--cc=kvm-riscv@lists.infradead.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.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 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).