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>
Subject: [PATCH 0/3] riscv: KVM: Expose Zicbom to the guest
Date: Tue, 6 Sep 2022 10:35:52 +0200 [thread overview]
Message-ID: <20220906083555.931806-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 were 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
Thanks,
drew
Andrew Jones (3):
RISC-V: Output cbom-block-size
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 | 11 +++++++++++
arch/riscv/mm/cacheflush.c | 5 ++++-
3 files changed, 17 insertions(+), 1 deletion(-)
--
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-06 8:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 8:35 Andrew Jones [this message]
2022-09-06 8:35 ` [PATCH 1/3] RISC-V: Output cbom-block-size Andrew Jones
2022-09-06 8:40 ` Conor.Dooley
2022-09-06 8:55 ` Andrew Jones
2022-09-06 9:00 ` Conor.Dooley
2022-09-06 9:29 ` Andrew Jones
2022-09-06 9:42 ` Conor.Dooley
2022-09-06 14:34 ` Heiko Stübner
2022-09-06 14:51 ` Andrew Jones
2022-09-06 9:01 ` Andrew Jones
2022-09-06 8:35 ` [PATCH 2/3] RISC-V: KVM: Provide UAPI for Zicbom block size Andrew Jones
2022-09-06 8:35 ` [PATCH 3/3] RISC-V: KVM: Expose Zicbom to the guest Andrew Jones
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=20220906083555.931806-1-ajones@ventanamicro.com \
--to=ajones@ventanamicro.com \
--cc=anup@brainfault.org \
--cc=atishp@atishpatra.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox