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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id B6C8DC761A6 for ; Tue, 4 Apr 2023 07:22:26 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233664AbjDDHW0 (ORCPT ); Tue, 4 Apr 2023 03:22:26 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50796 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233851AbjDDHWY (ORCPT ); Tue, 4 Apr 2023 03:22:24 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B63A3268B; Tue, 4 Apr 2023 00:22:20 -0700 (PDT) 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 2588A62F5C; Tue, 4 Apr 2023 07:22:20 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 18439C433D2; Tue, 4 Apr 2023 07:22:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1680592939; bh=zNbuc2c7Q9IWg5uy9hdmHULoUQBr2Hs/BAYhilZF5F4=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=CqHblzUj1z5GNNRhlVv5PjhJZbkNnPlRJpd8BNP9SFM3LozxkSRnpQ6pJHq1734IE nD0HzFbv58nu6J/EDvb0/r/dPnGTG4/RX9IFH1dtOkbIUrpX4gBAxv+iMBA5DHcRED emlRqtXMUO+8S4B3gXHGAfaZat5oK//B6B2YKi3S5Gq0z1OVXNwTRQKMwaAeo6YUWs fVidc4rMbc4aUoxxzgWhlqdgki6r0Y6O3oX30JhcakMQVSnJAF09H5rT22qPoqcLsD 1rUCPCKRgr6yla1vp2aXejTBBX5r0wagFlZzYRUY3h9pSLxjoBb/Ad/MMOzP9CoNyA E21K1u28YAOpQ== Date: Tue, 4 Apr 2023 10:22:00 +0300 From: Mike Rapoport To: Justin Forbes Cc: Andrew Morton , Arnd Bergmann , Catalin Marinas , Christophe Leroy , "David S. Miller" , Dinh Nguyen , Geert Uytterhoeven , Guo Ren , John Paul Adrian Glaubitz , "Kirill A. Shutemov" , Max Filippov , Michael Ellerman , Rich Felker , Russell King , Will Deacon , Yoshinori Sato , Zi Yan , linux-arm-kernel@lists.infradead.org, linux-csky@vger.kernel.org, linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org, linux-m68k@lists.linux-m68k.org, linux-mm@kvack.org, linux-sh@vger.kernel.org, linux-xtensa@linux-xtensa.org, linuxppc-dev@lists.ozlabs.org, sparclinux@vger.kernel.org Subject: Re: [PATCH v3 02/14] arm64: drop ranges in definition of ARCH_FORCE_MAX_ORDER Message-ID: References: <20230325060828.2662773-1-rppt@kernel.org> <20230325060828.2662773-3-rppt@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-csky@vger.kernel.org On Wed, Mar 29, 2023 at 10:55:37AM -0500, Justin Forbes wrote: > On Sat, Mar 25, 2023 at 1:09 AM Mike Rapoport wrote: > > > > From: "Mike Rapoport (IBM)" > > > > It is not a good idea to change fundamental parameters of core memory > > management. Having predefined ranges suggests that the values within > > those ranges are sensible, but one has to *really* understand > > implications of changing MAX_ORDER before actually amending it and > > ranges don't help here. > > > > Drop ranges in definition of ARCH_FORCE_MAX_ORDER and make its prompt > > visible only if EXPERT=y > > I do not like suddenly hiding this behind EXPERT for a couple of > reasons. Most importantly, it will silently change the config for > users building with an old kernel config. If a user has for instance > "13" set and building with 4K pages, as is the current configuration > for Fedora and RHEL aarch64 builds, an oldconfig build will now set it > to 10 with no indication that it is doing so. And while I think that > 10 is a fine default for many aarch64 users, there are valid reasons > for choosing other values. Putting this behind expert makes it much > less obvious that this is an option. That's the idea of EXPERT, no? This option was intended to allow allocation of huge pages for architectures that had PMD_ORDER > MAX_ORDER and not to allow user to select size of maximal physically contiguous allocation. Changes to MAX_ORDER fundamentally change the behaviour of core mm and unless users *really* know what they are doing there is no reason to choose non-default values so hiding this option behind EXPERT seems totally appropriate to me. > Justin > > > Acked-by: Kirill A. Shutemov > > Reviewed-by: Zi Yan > > Signed-off-by: Mike Rapoport (IBM) > > --- > > arch/arm64/Kconfig | 4 +--- > > 1 file changed, 1 insertion(+), 3 deletions(-) > > > > diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig > > index e60baf7859d1..7324032af859 100644 > > --- a/arch/arm64/Kconfig > > +++ b/arch/arm64/Kconfig > > @@ -1487,11 +1487,9 @@ config XEN > > # 16K | 27 | 14 | 13 | 11 | > > # 64K | 29 | 16 | 13 | 13 | > > config ARCH_FORCE_MAX_ORDER > > - int "Maximum zone order" if ARM64_4K_PAGES || ARM64_16K_PAGES > > + int "Maximum zone order" if EXPERT && (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 memory allocator divides physically contiguous memory > > -- > > 2.35.1 > > > > -- Sincerely yours, Mike. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Rapoport Date: Tue, 04 Apr 2023 07:22:00 +0000 Subject: Re: [PATCH v3 02/14] arm64: drop ranges in definition of ARCH_FORCE_MAX_ORDER Message-Id: List-Id: References: <20230325060828.2662773-1-rppt@kernel.org> <20230325060828.2662773-3-rppt@kernel.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable To: Justin Forbes Cc: Andrew Morton , Arnd Bergmann , Catalin Marinas , Christophe Leroy , "David S. Miller" , Dinh Nguyen , Geert Uytterhoeven , Guo Ren , John Paul Adrian Glaubitz , "Kirill A. Shutemov" , Max Filippov , Michael Ellerman , Rich Felker , Russell King , Will Deacon , Yoshinori Sato , Zi Yan , linux-arm-kernel@lists.infradead.org, linux-csky@vger.kernel.org, linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org, linux-m68k@lists.linux-m68k.org, linux-mm@kvack.org, linux-sh@vger.kernel.org, linux-xtensa@linux-xtensa.org, linuxppc-dev@lists.ozlabs.org, sparclinux@vger.kernel.org On Wed, Mar 29, 2023 at 10:55:37AM -0500, Justin Forbes wrote: > On Sat, Mar 25, 2023 at 1:09=E2=80=AFAM Mike Rapoport w= rote: > > > > From: "Mike Rapoport (IBM)" > > > > It is not a good idea to change fundamental parameters of core memory > > management. Having predefined ranges suggests that the values within > > those ranges are sensible, but one has to *really* understand > > implications of changing MAX_ORDER before actually amending it and > > ranges don't help here. > > > > Drop ranges in definition of ARCH_FORCE_MAX_ORDER and make its prompt > > visible only if EXPERT=3Dy >=20 > I do not like suddenly hiding this behind EXPERT for a couple of > reasons. Most importantly, it will silently change the config for > users building with an old kernel config. If a user has for instance > "13" set and building with 4K pages, as is the current configuration > for Fedora and RHEL aarch64 builds, an oldconfig build will now set it > to 10 with no indication that it is doing so. And while I think that > 10 is a fine default for many aarch64 users, there are valid reasons > for choosing other values. Putting this behind expert makes it much > less obvious that this is an option. That's the idea of EXPERT, no? This option was intended to allow allocation of huge pages for architectures that had PMD_ORDER > MAX_ORDER and not to allow user to select size of maximal physically contiguous allocation. Changes to MAX_ORDER fundamentally change the behaviour of core mm and unless users *really* know what they are doing there is no reason to choose non-default values so hiding this option behind EXPERT seems totally appropriate to me. =20 > Justin >=20 > > Acked-by: Kirill A. Shutemov > > Reviewed-by: Zi Yan > > Signed-off-by: Mike Rapoport (IBM) > > --- > > arch/arm64/Kconfig | 4 +--- > > 1 file changed, 1 insertion(+), 3 deletions(-) > > > > diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig > > index e60baf7859d1..7324032af859 100644 > > --- a/arch/arm64/Kconfig > > +++ b/arch/arm64/Kconfig > > @@ -1487,11 +1487,9 @@ config XEN > > # 16K | 27 | 14 | 13 | 1= 1 | > > # 64K | 29 | 16 | 13 | 1= 3 | > > config ARCH_FORCE_MAX_ORDER > > - int "Maximum zone order" if ARM64_4K_PAGES || ARM64_16K_PAGES > > + int "Maximum zone order" if EXPERT && (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 memory allocator divides physically contiguous mem= ory > > -- > > 2.35.1 > > > > --=20 Sincerely yours, Mike. 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 lists.ozlabs.org (lists.ozlabs.org [112.213.38.117]) (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 00AB0C77B60 for ; Tue, 4 Apr 2023 07:23:15 +0000 (UTC) Received: from boromir.ozlabs.org (localhost [IPv6:::1]) by lists.ozlabs.org (Postfix) with ESMTP id 4PrK423zlNz3chb for ; Tue, 4 Apr 2023 17:23:14 +1000 (AEST) Authentication-Results: lists.ozlabs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20201202 header.b=CqHblzUj; dkim-atps=neutral Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=kernel.org (client-ip=139.178.84.217; helo=dfw.source.kernel.org; envelope-from=rppt@kernel.org; receiver=) Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20201202 header.b=CqHblzUj; dkim-atps=neutral Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4PrK3361cKz3bXQ for ; Tue, 4 Apr 2023 17:22:23 +1000 (AEST) 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 187FE61248; Tue, 4 Apr 2023 07:22:20 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 18439C433D2; Tue, 4 Apr 2023 07:22:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1680592939; bh=zNbuc2c7Q9IWg5uy9hdmHULoUQBr2Hs/BAYhilZF5F4=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=CqHblzUj1z5GNNRhlVv5PjhJZbkNnPlRJpd8BNP9SFM3LozxkSRnpQ6pJHq1734IE nD0HzFbv58nu6J/EDvb0/r/dPnGTG4/RX9IFH1dtOkbIUrpX4gBAxv+iMBA5DHcRED emlRqtXMUO+8S4B3gXHGAfaZat5oK//B6B2YKi3S5Gq0z1OVXNwTRQKMwaAeo6YUWs fVidc4rMbc4aUoxxzgWhlqdgki6r0Y6O3oX30JhcakMQVSnJAF09H5rT22qPoqcLsD 1rUCPCKRgr6yla1vp2aXejTBBX5r0wagFlZzYRUY3h9pSLxjoBb/Ad/MMOzP9CoNyA E21K1u28YAOpQ== Date: Tue, 4 Apr 2023 10:22:00 +0300 From: Mike Rapoport To: Justin Forbes Subject: Re: [PATCH v3 02/14] arm64: drop ranges in definition of ARCH_FORCE_MAX_ORDER Message-ID: References: <20230325060828.2662773-1-rppt@kernel.org> <20230325060828.2662773-3-rppt@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Rich Felker , linux-ia64@vger.kernel.org, linux-sh@vger.kernel.org, Catalin Marinas , Max Filippov , Guo Ren , linux-csky@vger.kernel.org, sparclinux@vger.kernel.org, Will Deacon , Yoshinori Sato , Russell King , Geert Uytterhoeven , Zi Yan , linux-xtensa@linux-xtensa.org, Arnd Bergmann , linux-m68k@lists.linux-m68k.org, John Paul Adrian Glaubitz , linux-arm-kernel@lists.infradead.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, Dinh Nguyen , Andrew Morton , linuxppc-dev@lists.ozlabs.org, "David S. Miller" , "Kirill A. Shutemov" Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" On Wed, Mar 29, 2023 at 10:55:37AM -0500, Justin Forbes wrote: > On Sat, Mar 25, 2023 at 1:09 AM Mike Rapoport wrote: > > > > From: "Mike Rapoport (IBM)" > > > > It is not a good idea to change fundamental parameters of core memory > > management. Having predefined ranges suggests that the values within > > those ranges are sensible, but one has to *really* understand > > implications of changing MAX_ORDER before actually amending it and > > ranges don't help here. > > > > Drop ranges in definition of ARCH_FORCE_MAX_ORDER and make its prompt > > visible only if EXPERT=y > > I do not like suddenly hiding this behind EXPERT for a couple of > reasons. Most importantly, it will silently change the config for > users building with an old kernel config. If a user has for instance > "13" set and building with 4K pages, as is the current configuration > for Fedora and RHEL aarch64 builds, an oldconfig build will now set it > to 10 with no indication that it is doing so. And while I think that > 10 is a fine default for many aarch64 users, there are valid reasons > for choosing other values. Putting this behind expert makes it much > less obvious that this is an option. That's the idea of EXPERT, no? This option was intended to allow allocation of huge pages for architectures that had PMD_ORDER > MAX_ORDER and not to allow user to select size of maximal physically contiguous allocation. Changes to MAX_ORDER fundamentally change the behaviour of core mm and unless users *really* know what they are doing there is no reason to choose non-default values so hiding this option behind EXPERT seems totally appropriate to me. > Justin > > > Acked-by: Kirill A. Shutemov > > Reviewed-by: Zi Yan > > Signed-off-by: Mike Rapoport (IBM) > > --- > > arch/arm64/Kconfig | 4 +--- > > 1 file changed, 1 insertion(+), 3 deletions(-) > > > > diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig > > index e60baf7859d1..7324032af859 100644 > > --- a/arch/arm64/Kconfig > > +++ b/arch/arm64/Kconfig > > @@ -1487,11 +1487,9 @@ config XEN > > # 16K | 27 | 14 | 13 | 11 | > > # 64K | 29 | 16 | 13 | 13 | > > config ARCH_FORCE_MAX_ORDER > > - int "Maximum zone order" if ARM64_4K_PAGES || ARM64_16K_PAGES > > + int "Maximum zone order" if EXPERT && (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 memory allocator divides physically contiguous memory > > -- > > 2.35.1 > > > > -- Sincerely yours, Mike. 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 6221CC7618D for ; Tue, 4 Apr 2023 07:23:23 +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=YLiizLnoGsIpzNE3A9w/FwaRE/ECjiRmRZtiqYV8ia8=; b=ZEQdUgEg7mwDAT H+2rTg+MKixovJ5JhM85DwKYhQ7FVO3ii39qy8+7VOZzIkTPmQ2jQc010UZLMSTDFCV1plUgMVCuw g5DmZT3lVltOjp1/uqlDcqXcKdb8CNkbtvcEFPAgQC2jBVkR96eQb+WdOBbPykI7vCYPzLxKALd1Z 5ySVl9Mtvl3TELLPAdM4a7NA3U4VzEtnO35OeQp7UCpsdS7G+OHF6U7gZNcUuUlLbDQk9r1sL2FWb IEGLrkuTKHDK6UppFn9FQGD5u9J0KyX2maEabzr2VqCsQCGtV39T1yNMsRBgdbeQ6Vkfaz32WjHUR vwgl+xnK3Y4Ir8mhUldA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1pjazp-000IN8-0P; Tue, 04 Apr 2023 07:22:25 +0000 Received: from dfw.source.kernel.org ([139.178.84.217]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1pjazm-000IJH-1t for linux-arm-kernel@lists.infradead.org; Tue, 04 Apr 2023 07:22:23 +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 187FE61248; Tue, 4 Apr 2023 07:22:20 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 18439C433D2; Tue, 4 Apr 2023 07:22:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1680592939; bh=zNbuc2c7Q9IWg5uy9hdmHULoUQBr2Hs/BAYhilZF5F4=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=CqHblzUj1z5GNNRhlVv5PjhJZbkNnPlRJpd8BNP9SFM3LozxkSRnpQ6pJHq1734IE nD0HzFbv58nu6J/EDvb0/r/dPnGTG4/RX9IFH1dtOkbIUrpX4gBAxv+iMBA5DHcRED emlRqtXMUO+8S4B3gXHGAfaZat5oK//B6B2YKi3S5Gq0z1OVXNwTRQKMwaAeo6YUWs fVidc4rMbc4aUoxxzgWhlqdgki6r0Y6O3oX30JhcakMQVSnJAF09H5rT22qPoqcLsD 1rUCPCKRgr6yla1vp2aXejTBBX5r0wagFlZzYRUY3h9pSLxjoBb/Ad/MMOzP9CoNyA E21K1u28YAOpQ== Date: Tue, 4 Apr 2023 10:22:00 +0300 From: Mike Rapoport To: Justin Forbes Cc: Andrew Morton , Arnd Bergmann , Catalin Marinas , Christophe Leroy , "David S. Miller" , Dinh Nguyen , Geert Uytterhoeven , Guo Ren , John Paul Adrian Glaubitz , "Kirill A. Shutemov" , Max Filippov , Michael Ellerman , Rich Felker , Russell King , Will Deacon , Yoshinori Sato , Zi Yan , linux-arm-kernel@lists.infradead.org, linux-csky@vger.kernel.org, linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org, linux-m68k@lists.linux-m68k.org, linux-mm@kvack.org, linux-sh@vger.kernel.org, linux-xtensa@linux-xtensa.org, linuxppc-dev@lists.ozlabs.org, sparclinux@vger.kernel.org Subject: Re: [PATCH v3 02/14] arm64: drop ranges in definition of ARCH_FORCE_MAX_ORDER Message-ID: References: <20230325060828.2662773-1-rppt@kernel.org> <20230325060828.2662773-3-rppt@kernel.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230404_002222_722960_F63E85B7 X-CRM114-Status: GOOD ( 33.01 ) 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="utf-8" Content-Transfer-Encoding: base64 Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org T24gV2VkLCBNYXIgMjksIDIwMjMgYXQgMTA6NTU6MzdBTSAtMDUwMCwgSnVzdGluIEZvcmJlcyB3 cm90ZToKPiBPbiBTYXQsIE1hciAyNSwgMjAyMyBhdCAxOjA54oCvQU0gTWlrZSBSYXBvcG9ydCA8 cnBwdEBrZXJuZWwub3JnPiB3cm90ZToKPiA+Cj4gPiBGcm9tOiAiTWlrZSBSYXBvcG9ydCAoSUJN KSIgPHJwcHRAa2VybmVsLm9yZz4KPiA+Cj4gPiBJdCBpcyBub3QgYSBnb29kIGlkZWEgdG8gY2hh bmdlIGZ1bmRhbWVudGFsIHBhcmFtZXRlcnMgb2YgY29yZSBtZW1vcnkKPiA+IG1hbmFnZW1lbnQu IEhhdmluZyBwcmVkZWZpbmVkIHJhbmdlcyBzdWdnZXN0cyB0aGF0IHRoZSB2YWx1ZXMgd2l0aGlu Cj4gPiB0aG9zZSByYW5nZXMgYXJlIHNlbnNpYmxlLCBidXQgb25lIGhhcyB0byAqcmVhbGx5KiB1 bmRlcnN0YW5kCj4gPiBpbXBsaWNhdGlvbnMgb2YgY2hhbmdpbmcgTUFYX09SREVSIGJlZm9yZSBh Y3R1YWxseSBhbWVuZGluZyBpdCBhbmQKPiA+IHJhbmdlcyBkb24ndCBoZWxwIGhlcmUuCj4gPgo+ ID4gRHJvcCByYW5nZXMgaW4gZGVmaW5pdGlvbiBvZiBBUkNIX0ZPUkNFX01BWF9PUkRFUiBhbmQg bWFrZSBpdHMgcHJvbXB0Cj4gPiB2aXNpYmxlIG9ubHkgaWYgRVhQRVJUPXkKPiAKPiBJIGRvIG5v dCBsaWtlIHN1ZGRlbmx5IGhpZGluZyB0aGlzIGJlaGluZCBFWFBFUlQgZm9yIGEgY291cGxlIG9m Cj4gcmVhc29ucy4gIE1vc3QgaW1wb3J0YW50bHksIGl0IHdpbGwgc2lsZW50bHkgY2hhbmdlIHRo ZSBjb25maWcgZm9yCj4gdXNlcnMgYnVpbGRpbmcgd2l0aCBhbiBvbGQga2VybmVsIGNvbmZpZy4g IElmIGEgdXNlciBoYXMgZm9yIGluc3RhbmNlCj4gIjEzIiBzZXQgYW5kIGJ1aWxkaW5nIHdpdGgg NEsgcGFnZXMsIGFzIGlzIHRoZSBjdXJyZW50IGNvbmZpZ3VyYXRpb24KPiBmb3IgRmVkb3JhIGFu ZCBSSEVMIGFhcmNoNjQgYnVpbGRzLCBhbiBvbGRjb25maWcgYnVpbGQgd2lsbCBub3cgc2V0IGl0 Cj4gdG8gMTAgd2l0aCBubyBpbmRpY2F0aW9uIHRoYXQgaXQgaXMgZG9pbmcgc28uICBBbmQgd2hp bGUgSSB0aGluayB0aGF0Cj4gMTAgaXMgYSBmaW5lIGRlZmF1bHQgZm9yIG1hbnkgYWFyY2g2NCB1 c2VycywgdGhlcmUgYXJlIHZhbGlkIHJlYXNvbnMKPiBmb3IgY2hvb3Npbmcgb3RoZXIgdmFsdWVz LiBQdXR0aW5nIHRoaXMgYmVoaW5kIGV4cGVydCBtYWtlcyBpdCBtdWNoCj4gbGVzcyBvYnZpb3Vz IHRoYXQgdGhpcyBpcyBhbiBvcHRpb24uCgpUaGF0J3MgdGhlIGlkZWEgb2YgRVhQRVJULCBubz8K ClRoaXMgb3B0aW9uIHdhcyBpbnRlbmRlZCB0byBhbGxvdyBhbGxvY2F0aW9uIG9mIGh1Z2UgcGFn ZXMgZm9yCmFyY2hpdGVjdHVyZXMgdGhhdCBoYWQgUE1EX09SREVSID4gTUFYX09SREVSIGFuZCBu b3QgdG8gYWxsb3cgdXNlciB0bwpzZWxlY3Qgc2l6ZSBvZiBtYXhpbWFsIHBoeXNpY2FsbHkgY29u dGlndW91cyBhbGxvY2F0aW9uLgoKQ2hhbmdlcyB0byBNQVhfT1JERVIgZnVuZGFtZW50YWxseSBj aGFuZ2UgdGhlIGJlaGF2aW91ciBvZiBjb3JlIG1tIGFuZAp1bmxlc3MgdXNlcnMgKnJlYWxseSog a25vdyB3aGF0IHRoZXkgYXJlIGRvaW5nIHRoZXJlIGlzIG5vIHJlYXNvbiB0byBjaG9vc2UKbm9u LWRlZmF1bHQgdmFsdWVzIHNvIGhpZGluZyB0aGlzIG9wdGlvbiBiZWhpbmQgRVhQRVJUIHNlZW1z IHRvdGFsbHkKYXBwcm9wcmlhdGUgdG8gbWUuCiAKPiBKdXN0aW4KPiAKPiA+IEFja2VkLWJ5OiBL aXJpbGwgQS4gU2h1dGVtb3YgPGtpcmlsbC5zaHV0ZW1vdkBsaW51eC5pbnRlbC5jb20+Cj4gPiBS ZXZpZXdlZC1ieTogWmkgWWFuIDx6aXlAbnZpZGlhLmNvbT4KPiA+IFNpZ25lZC1vZmYtYnk6IE1p a2UgUmFwb3BvcnQgKElCTSkgPHJwcHRAa2VybmVsLm9yZz4KPiA+IC0tLQo+ID4gIGFyY2gvYXJt NjQvS2NvbmZpZyB8IDQgKy0tLQo+ID4gIDEgZmlsZSBjaGFuZ2VkLCAxIGluc2VydGlvbigrKSwg MyBkZWxldGlvbnMoLSkKPiA+Cj4gPiBkaWZmIC0tZ2l0IGEvYXJjaC9hcm02NC9LY29uZmlnIGIv YXJjaC9hcm02NC9LY29uZmlnCj4gPiBpbmRleCBlNjBiYWY3ODU5ZDEuLjczMjQwMzJhZjg1OSAx MDA2NDQKPiA+IC0tLSBhL2FyY2gvYXJtNjQvS2NvbmZpZwo+ID4gKysrIGIvYXJjaC9hcm02NC9L Y29uZmlnCj4gPiBAQCAtMTQ4NywxMSArMTQ4Nyw5IEBAIGNvbmZpZyBYRU4KPiA+ICAjIDE2SyB8 ICAgICAgIDI3ICAgICAgICAgIHwgICAgICAxNCAgICAgIHwgICAgICAgMTMgICAgICAgIHwgICAg ICAgICAxMSAgICAgICAgIHwKPiA+ICAjIDY0SyB8ICAgICAgIDI5ICAgICAgICAgIHwgICAgICAx NiAgICAgIHwgICAgICAgMTMgICAgICAgIHwgICAgICAgICAxMyAgICAgICAgIHwKPiA+ICBjb25m aWcgQVJDSF9GT1JDRV9NQVhfT1JERVIKPiA+IC0gICAgICAgaW50ICJNYXhpbXVtIHpvbmUgb3Jk ZXIiIGlmIEFSTTY0XzRLX1BBR0VTIHx8IEFSTTY0XzE2S19QQUdFUwo+ID4gKyAgICAgICBpbnQg Ik1heGltdW0gem9uZSBvcmRlciIgaWYgRVhQRVJUICYmIChBUk02NF80S19QQUdFUyB8fCBBUk02 NF8xNktfUEFHRVMpCj4gPiAgICAgICAgIGRlZmF1bHQgIjEzIiBpZiBBUk02NF82NEtfUEFHRVMK PiA+IC0gICAgICAgcmFuZ2UgMTEgMTMgaWYgQVJNNjRfMTZLX1BBR0VTCj4gPiAgICAgICAgIGRl ZmF1bHQgIjExIiBpZiBBUk02NF8xNktfUEFHRVMKPiA+IC0gICAgICAgcmFuZ2UgMTAgMTUgaWYg QVJNNjRfNEtfUEFHRVMKPiA+ICAgICAgICAgZGVmYXVsdCAiMTAiCj4gPiAgICAgICAgIGhlbHAK PiA+ICAgICAgICAgICBUaGUga2VybmVsIG1lbW9yeSBhbGxvY2F0b3IgZGl2aWRlcyBwaHlzaWNh bGx5IGNvbnRpZ3VvdXMgbWVtb3J5Cj4gPiAtLQo+ID4gMi4zNS4xCj4gPgo+ID4KCi0tIApTaW5j ZXJlbHkgeW91cnMsCk1pa2UuCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fXwpsaW51eC1hcm0ta2VybmVsIG1haWxpbmcgbGlzdApsaW51eC1hcm0ta2VybmVs QGxpc3RzLmluZnJhZGVhZC5vcmcKaHR0cDovL2xpc3RzLmluZnJhZGVhZC5vcmcvbWFpbG1hbi9s aXN0aW5mby9saW51eC1hcm0ta2VybmVsCg==