From: Andrew Jones <ajones@ventanamicro.com>
To: kvm-riscv@lists.infradead.org, linux-riscv@lists.infradead.org
Cc: Anup Patel <anup@brainfault.org>,
Atish Patra <atishp@atishpatra.org>,
Conor Dooley <conor.dooley@microchip.com>
Subject: [PATCH v3 0/2] riscv: KVM: Expose Zicbom to the guest
Date: Fri, 9 Sep 2022 16:43:58 +0200 [thread overview]
Message-ID: <20220909144400.1114485-1-ajones@ventanamicro.com> (raw)
Add support for exposing the Zicbom extension to guests. This has been
tested over a QEMU including the Zicbom support [1] ([1] was rebased and
the Zicboz support from it was dropped.) QEMU was further modified to
ensure the cache block size was provided in the DT. kvmtool was also
modified [2] to test the new KVM API and provide the guest the cache
block size in its DT (The kvmtool patches are based on Anup's Svpbmt/Sstc
series [3]). These KVM patches are based on the riscv_init_cbom_blocksize()
cleanup patch from Palmer and the move and expose riscv_cbom_block_size
patch from Anup which was reposted [4]. This series is also available here
[5].
[1] https://gitlab.com/jones-drew/qemu/-/commits/riscv/zicbom
[2] https://github.com/jones-drew/kvmtool/commits/riscv/zicbom
[3] https://github.com/avpatel/kvmtool/commits/riscv_svpbmt_sstc_v1
[4] https://lore.kernel.org/linux-riscv/20220906074509.928865-1-ajones@ventanamicro.com/T/#u
[5] https://github.com/jones-drew/linux/commits/riscv/kvm/zicbom-v3
Thanks,
drew
v3:
- Added check to ensure the extension is enabled for
config.get(blocksz) [Atish and Anup]
- Opportunistically switched all extension checks in
kvm_riscv_vcpu_update_config() to riscv_isa_extension_available()
from its __ counterpart
- Picked up some r-b's
v2:
- Dropped a patch that output the cache block size to dmesg
Andrew Jones (2):
RISC-V: KVM: Provide UAPI for Zicbom block size
RISC-V: KVM: Expose Zicbom to the guest
arch/riscv/include/uapi/asm/kvm.h | 2 ++
arch/riscv/kvm/vcpu.c | 17 +++++++++++++++--
arch/riscv/mm/cacheflush.c | 1 +
3 files changed, 18 insertions(+), 2 deletions(-)
--
2.37.2
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2022-09-09 14:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 14:43 Andrew Jones [this message]
2022-09-09 14:43 ` [PATCH v3 1/2] RISC-V: KVM: Provide UAPI for Zicbom block size Andrew Jones
2022-09-09 18:41 ` Atish Patra
2022-09-26 10:03 ` Anup Patel
2022-09-09 14:44 ` [PATCH v3 2/2] RISC-V: KVM: Expose Zicbom to the guest Andrew Jones
2022-09-09 18:37 ` Atish Patra
2022-09-26 10:05 ` Anup Patel
2022-09-15 16:57 ` [PATCH v3 0/2] riscv: " Conor.Dooley
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=20220909144400.1114485-1-ajones@ventanamicro.com \
--to=ajones@ventanamicro.com \
--cc=anup@brainfault.org \
--cc=atishp@atishpatra.org \
--cc=conor.dooley@microchip.com \
--cc=kvm-riscv@lists.infradead.org \
--cc=linux-riscv@lists.infradead.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 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.