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 5CDD6C433EF for ; Thu, 16 Dec 2021 14:25:54 +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=jaMDbtZD2JwMLuTJAxF/vJY+W9R0WLnUAofzZhhCp9c=; b=WRhG4nTMMHZ5ok Fxb7iSwjDmhKOHPAIk1tZJY2Hkb4AgB6CmJlM5OEZIsbRmGyQzPPCWgBQfuPG4IXiFCRRt126qSgy NWBJdeDvcGcIYxxl3V6txqY9RuOIX54UeWUQ9eAXDMaq8aqNlKVCqmA7x4SA+jm9B5fhvim5rYTB4 MmnU+xIBg9PzvlIUe4QyTukXcmAbcLkHCvbXH7ubEUFqU4QGSzmUK+i/D1MhZNIHeILIacrd1JDk+ aUs525+mD1Cww6gWT3EBblaXDD18h+bVJ4QZd4kq/qZS1yMQ76LGHMjXjT2BYN+vk9SkaPosAk8mP mhv6DckvKPEA9yxtBzew==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1mxrfw-0067rz-1X; Thu, 16 Dec 2021 14:24:05 +0000 Received: from dfw.source.kernel.org ([2604:1380:4641:c500::1]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1mxrbR-0066MZ-J0 for linux-arm-kernel@lists.infradead.org; Thu, 16 Dec 2021 14:19:26 +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 8FEBD61E26; Thu, 16 Dec 2021 14:19:24 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 3A34CC36AE4; Thu, 16 Dec 2021 14:19:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1639664364; bh=wKHsqz91WCddzKrP46ncvvbVZX+nCSFm/h2HBLrwUxI=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=j1mjwXSuOTfiCe0sanzpt8wtyyZlzNwxQl0xPqCCVQrDHlYdMWO3BJ0EyaE+B0Njs Vgf1aaYu0ByoflhWmw0DYj2gW9NAxePFd3S2biP/3us1F/a2cLvakHl+owj8HPwP+P iSnE8JfY2JZnllg4jHztoGMi6Zn75JiIMrU885gUn7N4PvpQzSfQouUuGeKz3XmxLS ip/HZHdprQBbLa+/wymjI5fDpfhnlpRFA6Zk3HZHHDGo8eq6xM8U7m41pm0muD4oKo nhiRsf41Ki4ZIgynVaCRByIqJVx/i8SKPQRYbvVn9JN6/7492tqc+Z/IwWDYcL1hR5 aqw9iXiiKiPKA== Date: Thu, 16 Dec 2021 16:19:15 +0200 From: Mike Rapoport To: Peng Fan Cc: Jan Kiszka , Ard Biesheuvel , "Peng Fan (OSS)" , Catalin Marinas , Will Deacon , Andrew Morton , David Hildenbrand , Anshuman Khandual , Geert Uytterhoeven , Linux ARM , Linux Kernel Mailing List , dl-linux-imx Subject: Re: [PATCH 2/2] arm64: mm: support bootparam max_addr Message-ID: References: <20211215064559.2843555-1-peng.fan@oss.nxp.com> <20211215064559.2843555-2-peng.fan@oss.nxp.com> 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-20211216_061925_726177_08B534F3 X-CRM114-Status: GOOD ( 14.96 ) 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 Wed, Dec 15, 2021 at 12:05:36PM +0000, Peng Fan wrote: > > Subject: Re: [PATCH 2/2] arm64: mm: support bootparam max_addr > > > > > > > > > If pass "mem=1024MB", the actually max addr will be > > > > > > > 0x81000000. However if need the max addr be 0x80000000, > > > > > > > mem=1008MB should be used. > > > > > > > > > BTW, do you think max_addr would be an option be added to memblock > common code mm/memblock.c? You have a working solution with mem=1008MB, I don't see a need for additional kernel parameter. -- Sincerely yours, Mike. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel 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 B8A92C433F5 for ; Thu, 16 Dec 2021 14:19:26 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237876AbhLPOT0 (ORCPT ); Thu, 16 Dec 2021 09:19:26 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41184 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229583AbhLPOTZ (ORCPT ); Thu, 16 Dec 2021 09:19:25 -0500 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0041AC061574 for ; Thu, 16 Dec 2021 06:19:24 -0800 (PST) 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 9300B61E29 for ; Thu, 16 Dec 2021 14:19:24 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 3A34CC36AE4; Thu, 16 Dec 2021 14:19:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1639664364; bh=wKHsqz91WCddzKrP46ncvvbVZX+nCSFm/h2HBLrwUxI=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=j1mjwXSuOTfiCe0sanzpt8wtyyZlzNwxQl0xPqCCVQrDHlYdMWO3BJ0EyaE+B0Njs Vgf1aaYu0ByoflhWmw0DYj2gW9NAxePFd3S2biP/3us1F/a2cLvakHl+owj8HPwP+P iSnE8JfY2JZnllg4jHztoGMi6Zn75JiIMrU885gUn7N4PvpQzSfQouUuGeKz3XmxLS ip/HZHdprQBbLa+/wymjI5fDpfhnlpRFA6Zk3HZHHDGo8eq6xM8U7m41pm0muD4oKo nhiRsf41Ki4ZIgynVaCRByIqJVx/i8SKPQRYbvVn9JN6/7492tqc+Z/IwWDYcL1hR5 aqw9iXiiKiPKA== Date: Thu, 16 Dec 2021 16:19:15 +0200 From: Mike Rapoport To: Peng Fan Cc: Jan Kiszka , Ard Biesheuvel , "Peng Fan (OSS)" , Catalin Marinas , Will Deacon , Andrew Morton , David Hildenbrand , Anshuman Khandual , Geert Uytterhoeven , Linux ARM , Linux Kernel Mailing List , dl-linux-imx Subject: Re: [PATCH 2/2] arm64: mm: support bootparam max_addr Message-ID: References: <20211215064559.2843555-1-peng.fan@oss.nxp.com> <20211215064559.2843555-2-peng.fan@oss.nxp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Dec 15, 2021 at 12:05:36PM +0000, Peng Fan wrote: > > Subject: Re: [PATCH 2/2] arm64: mm: support bootparam max_addr > > > > > > > > > If pass "mem=1024MB", the actually max addr will be > > > > > > > 0x81000000. However if need the max addr be 0x80000000, > > > > > > > mem=1008MB should be used. > > > > > > > > > BTW, do you think max_addr would be an option be added to memblock > common code mm/memblock.c? You have a working solution with mem=1008MB, I don't see a need for additional kernel parameter. -- Sincerely yours, Mike.