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 3A7EBC4332F for ; Fri, 25 Nov 2022 13:26:01 +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=6pq9xyHkzduAx8CQmFlnkZeEcvTEBXP+RmhQ/81vzAc=; b=afSpeODlgRxoag WU+Og0+TNT/uEi7FeuM3g31noUPZyd+nQzxnjP2lLSfQLmo9Qop0a+OwRG/PhThI8R8dVL1qWHCB4 cV1npxjRBnpYQkgXBhDmf4xUnzhILPXkhS8AfIBbl145oOfpdMxqqeKLbeyFpkfnYHKFXMzt2cpc+ 3UpNk96UboMNhVL+QPg9kNQ3zSor+rDb4XqXy0EFOQ+3wo6e6IoQEeEb2re+PJOVB8YQ/ZTBI0TBV 6pBdpZxAo1bXcohGi75+f/HnVC3bSpIwHhdUUOwzW6ttJfAzqn+UEv1rtNDbJx4Tj+qRq/1iYD9Og jeOWXVIarqKjeNj3etaw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1oyYhP-00GfIr-C5; Fri, 25 Nov 2022 13:24:59 +0000 Received: from dfw.source.kernel.org ([139.178.84.217]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1oyYhM-00GfHe-Il for linux-arm-kernel@lists.infradead.org; Fri, 25 Nov 2022 13:24:58 +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 dfw.source.kernel.org (Postfix) with ESMTPS id 085B5623F3; Fri, 25 Nov 2022 13:24:56 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 2E147C433C1; Fri, 25 Nov 2022 13:24:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1669382695; bh=992p7WkT5/dSrv31fAM88AbytKlPeiJ9mN41VePGHoU=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=SteoEpJMOLA0idg2klDDsIDluiqqPKXTe2Jn2GcsKp9vnK3vaRlNrH2FBTqTEe7x5 SxuWpNaMA1jzNjYYetQSGtzqockM4zBzyM8saFTRUolMOTSYT512h74oLW/ojiDCNM fPZMsm6RbfglIETnK9ha/t6uzQ2Oix+WCyV+RRT7pGHJQNKPdgW5Ae+oYscvhLhity auU7ute36rb0SVE5VOdFS+kCyUwc7FRZwfSa0FIZ/6a5HmNbLveLc2QN4Q1YcgQxhL 5e5w68KuPGPtSJAAI/rVhvLWsai49Ir3u+2UCcj6wf/J+NkxnpeIS50bXVK1tv/Is4 /y+5UZw60+FUQ== From: Will Deacon To: Ard Biesheuvel , linux-arm-kernel@lists.infradead.org Cc: catalin.marinas@arm.com, kernel-team@android.com, Will Deacon , mark.rutland@arm.com Subject: Re: [PATCH] arm64: booting: Require placement within 48-bit addressable memory Date: Fri, 25 Nov 2022 13:24:47 +0000 Message-Id: <166937881256.3467204.8500922774094500775.b4-ty@kernel.org> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20221122170249.2453853-1-ardb@kernel.org> References: <20221122170249.2453853-1-ardb@kernel.org> MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20221125_052456_679252_3236A141 X-CRM114-Status: GOOD ( 12.29 ) 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 Tue, 22 Nov 2022 18:02:49 +0100, Ard Biesheuvel wrote: > Some configurations (i.e., 64k + LVA/LPA) can tolerate a physical > placement of the kernel image outside of the 48-bit addressable region, > but given that the loader has no way of knowing whether or not the image > in question supports LVA/LPA, it currently has no choice but to place it > below the 48-bit mark. > > Once we add support for LPA2, which allows 52-bit physical and virtual > addressing when using 4k or 16k pages, but in way that relies on > increasing the number of paging levels, there will be more variety in > the configurations that may or may not support this. > > [...] Applied to arm64 (for-next/mm), thanks! [1/1] arm64: booting: Require placement within 48-bit addressable memory https://git.kernel.org/arm64/c/453dfcee70c5 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