From: Will Deacon <will@kernel.org>
To: Marc Zyngier <maz@kernel.org>, kvmarm@lists.cs.columbia.edu
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
Andre Przywara <andre.przywara@arm.com>
Subject: Re: [PATCH v2 0/3] kvmtool: Limit IPA space to what is actually required
Date: Tue, 31 Aug 2021 16:05:57 +0100 [thread overview]
Message-ID: <163042121770.1911365.5609247685320419649.b4-ty@kernel.org> (raw)
In-Reply-To: <20210822152526.1291918-1-maz@kernel.org>
On Sun, 22 Aug 2021 16:25:23 +0100, Marc Zyngier wrote:
> KVM hacking on the Apple M1 SoC has shown that kvmtool (and other
> VMMs) make pretty poor use of the IPA space parameter (read: do not
> use it and just pass 0). This results in a guest that cannot boot
> (recent kernels will just send the VMM packing), and in general means
> we don't benefit from smaller page tables at stage-2.
>
> This series does three things:
> - It switches kvmtool away from the default 40bit, allowing large VMs
> to be created (I have booted a 4TB VM)
> - It reduces the requested IPA space to be as small as possible
> - It tells the user why the VM cannot boot when the IPA space required
> exceeds that of the HW
>
> [...]
Applied to kvmtool (master), thanks!
[1/3] kvmtool: Abstract KVM_VM_TYPE into a weak function
https://git.kernel.org/will/kvmtool/c/4250819de93b
[2/3] kvmtool: arm64: Use the maximum supported IPA size when creating the VM
https://git.kernel.org/will/kvmtool/c/066b5c06c4e3
[3/3] kvmtool: arm64: Configure VM with the minimal required IPA space
https://git.kernel.org/will/kvmtool/c/bdb86d0c0c95
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
prev parent reply other threads:[~2021-08-31 15:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-22 15:25 [PATCH v2 0/3] kvmtool: Limit IPA space to what is actually required Marc Zyngier
2021-08-22 15:25 ` [PATCH v2 1/3] kvmtool: Abstract KVM_VM_TYPE into a weak function Marc Zyngier
2021-08-22 19:58 ` Oliver Upton
2021-08-22 15:25 ` [PATCH v2 2/3] kvmtool: arm64: Use the maximum supported IPA size when creating the VM Marc Zyngier
2021-08-22 20:03 ` Oliver Upton
2021-08-24 0:46 ` Andre Przywara
2021-08-22 15:25 ` [PATCH v2 3/3] kvmtool: arm64: Configure VM with the minimal required IPA space Marc Zyngier
2021-08-22 20:05 ` Oliver Upton
2021-08-23 9:36 ` Marc Zyngier
2021-08-23 9:43 ` Oliver Upton
2021-08-24 0:47 ` Andre Przywara
2021-08-26 11:11 ` Marc Zyngier
2021-08-31 15:05 ` Will Deacon [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=163042121770.1911365.5609247685320419649.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=andre.przywara@arm.com \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=maz@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 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.