From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 295B1C43334 for ; Fri, 1 Jul 2022 15:42:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Message-Id:Date:Subject:Cc:To:From:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=Jsl0HFolC/t5R5wu7igrMSPwifuS23J1/4iSuAvY2UQ=; b=Ku/rI1I6C2xEnT TgbZ1WXd1dFahqrvRP+gOWkPWCtn1KTXYuF5mnfactvBtgEbUXzyK35LdNsY+QjC/1wAjXD6Rgrk7 qAd08rAiiomj/muPm0nxoo8+kgMhf9X4pjV4Dy5ng4WojBqhodW3+kzNsLLRqSybRg97FPCCFKZGf qgJPapRAlxV4y8ZQr8GzOapI39B6bS2xRWzAAbE8mi69WBTLoPhC1PuL6etKJT6vu6KObNXm+0kRs CVuQdfspGJ2A+G9jjTBc51ILdZVe7jlLka+J7AqSTUeXOms1rdDnmt/bZVKiR/YJTpWFYERVJ+Bv+ 3F8KJy429bBrS9abVo2g==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1o7ImE-005ksX-Pr; Fri, 01 Jul 2022 15:41:50 +0000 Received: from ams.source.kernel.org ([145.40.68.75]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1o7Im7-005krD-Mz for linux-arm-kernel@lists.infradead.org; Fri, 01 Jul 2022 15:41:45 +0000 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 27115B830A0; Fri, 1 Jul 2022 15:41:42 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 8701BC341CA; Fri, 1 Jul 2022 15:41:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1656690100; bh=3T9BR9wQoQq/4l/cuzDtrWY3lzmwZg8afajWV734Dec=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=Lug4DmtrmpSw5neujBjnRi7fGP89gVgZ24QOAJOyACkezuGNUVLaJ45hbqfbgRfsD +Y2RfNiYBnmkZQBbKfUseS5mdedNWJDdkLAWnbTlfXT5zzw/yx96SrWb8olyojH4Jy hLwZW4qLtv0lWSDl/I0E9K03jsspravTdz0lUIh1Z65DxSKckcegX+12wPX1HDAufS 6DLaNXEmK+6SUYnJSCid6X/e/or0HUJ0k3AtiyBYw5uI9mGn/JcS4tImhjh4kciJNH X/Wf+NZMWaw0Zgs+WhyjE7LIwhX63wb3G55gQ4Ojami2HU4r7mcvderuLVncCAjVbL asBcBC2NDJc9g== From: Will Deacon To: kvmarm@lists.cs.columbia.edu, linux-arm-kernel@lists.infradead.org, maz@kernel.org, Alexandru Elisei , 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 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 Message-Id: <165668808723.3745248.3708834385367183136.b4-ty@kernel.org> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20220616134828.129006-1-alexandru.elisei@arm.com> References: <20220616134828.129006-1-alexandru.elisei@arm.com> MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220701_084143_934365_50DDA96C X-CRM114-Status: GOOD ( 13.54 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org 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