From: Alistair Francis <alistair23@gmail.com>
To: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
Cc: qemu-devel@nongnu.org, qemu-riscv@nongnu.org,
alistair.francis@wdc.com, bmeng@tinylab.org,
liweiwei@iscas.ac.cn, zhiwei_liu@linux.alibaba.com,
palmer@rivosinc.com, ajones@ventanamicro.com
Subject: Re: [PATCH 0/2] riscv, kvm: support KVM_GET_REG_LIST
Date: Mon, 9 Oct 2023 11:14:48 +1000 [thread overview]
Message-ID: <CAKmqyKOBYNp2d7+4qQCojuDMmERTYgYkcacJ+V0sUNrzOMjUPQ@mail.gmail.com> (raw)
In-Reply-To: <20231003113259.771539-1-dbarboza@ventanamicro.com>
On Tue, Oct 3, 2023 at 9:34 PM Daniel Henrique Barboza
<dbarboza@ventanamicro.com> wrote:
>
> Hi,
>
> Starting on Linux 6.6 the QEMU RISC-V KVM driver now supports
> KMV_GET_REG_LIST. This API will make it simpler for the QEMU KVM driver
> to determine whether a KVM reg is present or not.
>
> We'll use this API to fetch ISA_EXT regs during init(). The current
> logic will be put in a legacy() helper and will still be used in case
> the host KVM module does not support get-reg-list.
>
> Patch 1 contains error handling changes in kvm_riscv_init_multiext_cfg()
> where we're using &error_fatal and errno.
>
>
> Daniel Henrique Barboza (2):
> target/riscv/kvm: improve 'init_multiext_cfg' error msg
> target/riscv/kvm: support KVM_GET_REG_LIST
Thanks!
Applied to riscv-to-apply.next
Alistair
>
> target/riscv/kvm/kvm-cpu.c | 100 +++++++++++++++++++++++++++++++++++--
> 1 file changed, 95 insertions(+), 5 deletions(-)
>
> --
> 2.41.0
>
>
prev parent reply other threads:[~2023-10-09 1:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 11:32 [PATCH 0/2] riscv, kvm: support KVM_GET_REG_LIST Daniel Henrique Barboza
2023-10-03 11:32 ` [PATCH 1/2] target/riscv/kvm: improve 'init_multiext_cfg' error msg Daniel Henrique Barboza
2023-10-03 11:53 ` Philippe Mathieu-Daudé
2023-10-03 11:32 ` [PATCH 2/2] target/riscv/kvm: support KVM_GET_REG_LIST Daniel Henrique Barboza
2023-10-09 1:14 ` Alistair Francis [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=CAKmqyKOBYNp2d7+4qQCojuDMmERTYgYkcacJ+V0sUNrzOMjUPQ@mail.gmail.com \
--to=alistair23@gmail.com \
--cc=ajones@ventanamicro.com \
--cc=alistair.francis@wdc.com \
--cc=bmeng@tinylab.org \
--cc=dbarboza@ventanamicro.com \
--cc=liweiwei@iscas.ac.cn \
--cc=palmer@rivosinc.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=zhiwei_liu@linux.alibaba.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).