From: Will Deacon <will@kernel.org>
To: kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org, maz@kernel.org,
Alexandru Elisei <alexandru.elisei@arm.com>,
andre.przywara@arm.com, suzuki.poulose@arm.com,
james.morse@arm.com, julien@xen.org,
julien.thierry.kdev@gmail.com
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>
Subject: Re: [PATCH v4 kvmtool 00/12] arm64: Allow the user to set RAM base address
Date: Fri, 1 Jul 2022 16:41:24 +0100 [thread overview]
Message-ID: <165668808723.3745248.3708834385367183136.b4-ty@kernel.org> (raw)
In-Reply-To: <20220616134828.129006-1-alexandru.elisei@arm.com>
On Thu, 16 Jun 2022 14:48:16 +0100, Alexandru Elisei wrote:
> The series can be found at [1]. It is loosely based on the patches that
> allow the user to define the VM memory layout (RAM + MMIO) [2]. I've
> cherry-picked a handful of patches from that series, the rest I wrote from
> scratch since there have been several changes to the way guest memory is
> handled. I've chosen to focus on specifying the RAM layout with only one
> RAM bank and leave the rest for a later series because this was relatively
> easy to accomplish, while still being very useful.
>
> [...]
Applied to kvmtool (master), thanks!
[01/12] Use MB for megabytes consistently
https://git.kernel.org/will/kvmtool/c/024c331b8483
[02/12] builtin-run: Always use RAM size in bytes
https://git.kernel.org/will/kvmtool/c/9d655190e466
[03/12] builtin-run: Rework RAM size validation
https://git.kernel.org/will/kvmtool/c/28b96259fbdf
[04/12] builtin-run: Add arch hook to validate VM configuration
https://git.kernel.org/will/kvmtool/c/abe3f28a9c07
[05/12] arm/arm64: Fail if RAM size is too large for 32-bit guests
https://git.kernel.org/will/kvmtool/c/cce5a4f6ae9b
[06/12] arm/arm64: Kill the ARM_MAX_MEMORY() macro
https://git.kernel.org/will/kvmtool/c/1af57dcdce51
[07/12] arm/arm64: Kill the ARM_HIMAP_MAX_MEMORY() macro
https://git.kernel.org/will/kvmtool/c/d6d4220133b7
[08/12] builtin_run: Allow standard size specifiers for memory
https://git.kernel.org/will/kvmtool/c/a9c24ec78b4f
[09/12] kvm__arch_init: Remove hugetlbfs_path and ram_size as parameters
https://git.kernel.org/will/kvmtool/c/5e9c654e60e8
[10/12] arm/arm64: Consolidate RAM initialization in kvm__init_ram()
https://git.kernel.org/will/kvmtool/c/a37dad0ea9c7
[11/12] Introduce kvm__arch_default_ram_address()
https://git.kernel.org/will/kvmtool/c/3f7e48f621bb
[12/12] arm64: Allow the user to specify the RAM base address
https://git.kernel.org/will/kvmtool/c/8b91a1828ee9
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-07-01 15:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 13:48 [PATCH v4 kvmtool 00/12] arm64: Allow the user to set RAM base address Alexandru Elisei
2022-06-16 13:48 ` [PATCH v4 kvmtool 01/12] Use MB for megabytes consistently Alexandru Elisei
2022-06-16 13:48 ` [PATCH v4 kvmtool 02/12] builtin-run: Always use RAM size in bytes Alexandru Elisei
2022-06-16 17:07 ` Andre Przywara
2022-06-16 13:48 ` [PATCH v4 kvmtool 03/12] builtin-run: Rework RAM size validation Alexandru Elisei
2022-06-16 13:48 ` [PATCH v4 kvmtool 04/12] builtin-run: Add arch hook to validate VM configuration Alexandru Elisei
2022-06-16 17:07 ` Andre Przywara
2022-06-16 13:48 ` [PATCH v4 kvmtool 05/12] arm/arm64: Fail if RAM size is too large for 32-bit guests Alexandru Elisei
2022-06-16 13:48 ` [PATCH v4 kvmtool 06/12] arm/arm64: Kill the ARM_MAX_MEMORY() macro Alexandru Elisei
2022-06-16 13:48 ` [PATCH v4 kvmtool 07/12] arm/arm64: Kill the ARM_HIMAP_MAX_MEMORY() macro Alexandru Elisei
2022-06-16 13:48 ` [PATCH v4 kvmtool 08/12] builtin_run: Allow standard size specifiers for memory Alexandru Elisei
2022-06-16 17:10 ` Andre Przywara
2022-06-16 13:48 ` [PATCH v4 kvmtool 09/12] kvm__arch_init: Remove hugetlbfs_path and ram_size as parameters Alexandru Elisei
2022-06-16 13:48 ` [PATCH v4 kvmtool 10/12] arm/arm64: Consolidate RAM initialization in kvm__init_ram() Alexandru Elisei
2022-06-16 13:48 ` [PATCH v4 kvmtool 11/12] Introduce kvm__arch_default_ram_address() Alexandru Elisei
2022-06-16 13:48 ` [PATCH v4 kvmtool 12/12] arm64: Allow the user to specify the RAM base address Alexandru Elisei
2022-06-21 17:03 ` [PATCH v4 kvmtool 00/12] arm64: Allow the user to set " Suzuki K Poulose
2022-06-22 9:27 ` Alexandru Elisei
2022-07-01 15:41 ` 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=165668808723.3745248.3708834385367183136.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=alexandru.elisei@arm.com \
--cc=andre.przywara@arm.com \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=julien.thierry.kdev@gmail.com \
--cc=julien@xen.org \
--cc=kernel-team@android.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--cc=suzuki.poulose@arm.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