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 A926AC77B60 for ; Fri, 28 Apr 2023 17:02:34 +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:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=hGAzarXL+kpRNRuSULLHI2p88/GUJpiRZ0q3w9j1YLk=; b=ndOzE6cF2DbKft 5APOsO1Z4NEGtwZpaEuXQ0HQIa6JzGpBIFH6PiekCT+j72QrezUKWQJ973qnW54y9LgiBUpIKstGa EyOMBMcMSe4MTyGihRHI4itouMKCOGi2upo69XcfJ4wF2aote7+8AGgrqy0XukKBYfvoTwMptMgB6 rZNMmECdNta6Fmq2s1zaKrkcJoeZpMQi4WbAryQbEE39QKsJaJxV1n8HMeZNpBcV1aykQpv8cfjOf g4Wt8nVQMk+/SGgGXgWNrRPlQQEutC3t9CCbd3S6klaQdQJcd3zXnty21WFa46P/e5HfD/itJBxSK xZ+av+eshlj/pVfzl9cQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1psRTW-00BIOK-2x; Fri, 28 Apr 2023 17:01:38 +0000 Received: from dfw.source.kernel.org ([2604:1380:4641:c500::1]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1psRTU-00BINq-0H for linux-arm-kernel@lists.infradead.org; Fri, 28 Apr 2023 17:01:37 +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 A3296644B1; Fri, 28 Apr 2023 17:01:35 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id C11C3C433EF; Fri, 28 Apr 2023 17:01:33 +0000 (UTC) Date: Fri, 28 Apr 2023 18:01:30 +0100 From: Catalin Marinas To: "Justin M. Forbes" Cc: Will Deacon , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, jmforbes@linuxtx.org, Mike Rapoport , Andrew Morton Subject: Re: [PATCH] Revert arm64: drop ranges in definition of ARCH_FORCE_MAX_ORDER Message-ID: References: <20230428153646.823736-1-jforbes@fedoraproject.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20230428153646.823736-1-jforbes@fedoraproject.org> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230428_100136_159606_5CC115B5 X-CRM114-Status: GOOD ( 22.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 + Mike and Andrew On Fri, Apr 28, 2023 at 10:36:45AM -0500, Justin M. Forbes wrote: > While the ARCH_FORCE_MAX_ORDER changes clarified the descriptions quite > a bit, the aarch64 specific change moved this config to sit behind > CONFIG_EXPERT. This becomes problematic when distros are setting this to > a non default value already. Pushing it behind EXPERT where it was not > before will silently change the configuration for users building with > oldconfig. If distros patch out if EXPERT downstream, it still creates > problems for users testing out upstream patches, or trying to bisect to > find the root of problem, as the configuration will change unexpectedly, > possibly leading to different behavior and false results. > > Whem I asked about reverting the EXPERT, dependency, I was asked to add > the ranges back. > > This essentially reverts commit 34affcd7577a232803f729d1870ba475f294e4ea > > Signed-off-by: Justin M. Forbes > Cc: Catalin Marinas > --- > arch/arm64/Kconfig | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) > > diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig > index b1201d25a8a4..dae18ac01e94 100644 > --- a/arch/arm64/Kconfig > +++ b/arch/arm64/Kconfig > @@ -1516,9 +1516,11 @@ config XEN > # 16K | 27 | 14 | 13 | 11 | > # 64K | 29 | 16 | 13 | 13 | > config ARCH_FORCE_MAX_ORDER > - int "Order of maximal physically contiguous allocations" if EXPERT && (ARM64_4K_PAGES || ARM64_16K_PAGES) > + int "Order of maximal physically contiguous allocations" if ARM64_4K_PAGES || ARM64_16K_PAGES > default "13" if ARM64_64K_PAGES > + range 11 13 if ARM64_16K_PAGES > default "11" if ARM64_16K_PAGES > + range 10 15 if ARM64_4K_PAGES > default "10" > help > The kernel page allocator limits the size of maximal physically The revert looks fine to me: Acked-by: Catalin Marinas For the record, the original discussion: Link: https://lore.kernel.org/r/CAFxkdAr5C7ggZ+WdvDbsfmwuXujT_z_x3qcUnhnCn-WrAurvgA@mail.gmail.com _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel