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 X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id AE3A4C433E0 for ; Thu, 21 May 2020 12:03:24 +0000 (UTC) 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 mail.kernel.org (Postfix) with ESMTPS id 62DB820721 for ; Thu, 21 May 2020 12:03:24 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="mWqbhr15"; dkim=fail reason="signature verification failed" (2048-bit key) header.d=armlinux.org.uk header.i=@armlinux.org.uk header.b="wjIqw2Nw" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 62DB820721 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=armlinux.org.uk Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject: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=2WVTVYF9kXJel1yskFVSvrFSnMIhXwNiF2gCo9fVDgg=; b=mWqbhr15zgCrJ2 yjdItxZVICx/Zd9eGb/ZKsuHlSiTXniiohse4rIc9IiKmJ5jywvwKbkAHc6dAJEvjkZP8sfdLqO/Z Sc+q4RHnEGY3HN4p76ANIDJgJYYCBlqIkYmWrSwp/iOpLQ6A4kJHF64CKhALRFUbzE6/1Mx5T2Ky2 TGFtiYNwBl9+zARGf9K6e9aaDHjk9O3dRkULrDNt+sCBOaN93Brzh8neb3nwnRU7RBugeqT9ctZzO wYxLG7lilGX+Z+0TnrdBj1jZVmcaa1POCDDLYN+LxsoVLxonMq+WasSb5/dwIwv2IxyUW6LFd99B0 8zE5ZBGYLonqCJqxsWdg==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1jbjv0-0003e4-I3; Thu, 21 May 2020 12:03:22 +0000 Received: from pandora.armlinux.org.uk ([2001:4d48:ad52:3201:214:fdff:fe10:1be6]) by bombadil.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1jbjux-0003dP-RP for linux-arm-kernel@lists.infradead.org; Thu, 21 May 2020 12:03:21 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=armlinux.org.uk; s=pandora-2019; h=Sender:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=DugcN9tbDgtWy6KtRQBnM72cC+bpgx46fZD/tUG5gjo=; b=wjIqw2NwPqWPl/iYizsOTBh5I TylaQFSATiDKxa+X1/RBTAw6MqthIF6DClJTXNAeaV+B1qWCrXC5AffDlFH20OQR3gU0t3K1D4+wp CHjjP2KygVSWFfnsrno3kTOZPN+D5WyNvIwo8uHvqiRxKynf5SrYf6kGznhoKFA11znDGYTu0/alC xh9pPdR70cc88zSR6tOlbOYJmElxSpd0+7PNckslXuPADih1qxML7i5Qz6NwsFsJjQcJTz2At7QFb WqPknIA9eomKOrH6qfQ/v/Uf4VWqJQl/6QSfrFwhoiBjbjB8VqYh0Rgo62cS0WNSvbLWStXOxVNZb XMAHs86KA==; Received: from shell.armlinux.org.uk ([2001:4d48:ad52:3201:5054:ff:fe00:4ec]:43122) by pandora.armlinux.org.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jbjuo-0002NN-2P; Thu, 21 May 2020 13:03:10 +0100 Received: from linux by shell.armlinux.org.uk with local (Exim 4.92) (envelope-from ) id 1jbjum-0000BN-GM; Thu, 21 May 2020 13:03:08 +0100 Date: Thu, 21 May 2020 13:03:08 +0100 From: Russell King - ARM Linux admin To: Mike Rapoport Subject: Re: [PATCH 0/2] ARM: Allow either FLATMEM or SPARSEMEM on the multiplatform build Message-ID: <20200521120308.GR1551@shell.armlinux.org.uk> References: <20200521081825.1348844-1-rppt@linux.ibm.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20200521081825.1348844-1-rppt@linux.ibm.com> User-Agent: Mutt/1.10.1 (2018-07-13) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20200521_050319_886846_487CAB66 X-CRM114-Status: GOOD ( 16.57 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Florian Fainelli , Arnd Bergmann , Stephen Boyd , Kevin Cernekee , Doug Berger , Gregory Fong , linux-arm-kernel@lists.infradead.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, May 21, 2020 at 11:18:23AM +0300, Mike Rapoport wrote: > (resendig for the correct address and with mailing list cc'ed, sorry for > the noise) > > Hi, > > Following the discussion at [1], I'm resending the patches that enable > memory model selection in menuconfig and such. > > These patches do not change the way the configuration is generated from the > defconfigs and they do not change explicit selection of SPARSEMEM for > platforms that have "select ARCH_ENABLE_SPARSEMEM". > > The mere change is that when a user runs an interactive configuration they > will be allowed to select between FLATMEM and SPARSMEM, which is not the > case today. > > There is indeed some awkwardness in, e.g. removal of > ARCH_SPARSEMEM_DEFAULT, but this is what memory model selection logic in > mm/Kconfig imposes. > > For example, below is the diffs of the configurations generated with > 'make rpc_defconfig' and 'make defconfig': > > $ diff -s old/rpc_defconfig new/rpc_defconfig > Files old/rpc_defconfig and new/rpc_defconfig are identical > > $ diff -u old/defconfig new/defconfig > --- old/defconfig 2020-05-20 17:51:01.832649705 +0300 > +++ new/defconfig 2020-05-20 18:15:21.084385880 +0300 > @@ -674,6 +674,9 @@ > CONFIG_AEABI=y > # CONFIG_OABI_COMPAT is not set > CONFIG_ARCH_HAS_HOLES_MEMORYMODEL=y > +CONFIG_ARCH_SELECT_MEMORY_MODEL=y > +CONFIG_ARCH_FLATMEM_ENABLE=y > +CONFIG_ARCH_SPARSEMEM_ENABLE=y > CONFIG_HAVE_ARCH_PFN_VALID=y > CONFIG_HIGHMEM=y > CONFIG_HIGHPTE=y > @@ -1061,6 +1064,9 @@ > # > # Memory Management options > # > +CONFIG_SELECT_MEMORY_MODEL=y > +CONFIG_FLATMEM_MANUAL=y > +# CONFIG_SPARSEMEM_MANUAL is not set > CONFIG_FLATMEM=y > CONFIG_FLAT_NODE_MEM_MAP=y > CONFIG_ARCH_KEEP_MEMBLOCK=y Right, but the question is whether we want to offer flatmem for rpc. It isn't allowed today, and so far no one has said why it's a desirable change to make. -- RMK's Patch system: https://www.armlinux.org.uk/developer/patches/ FTTC for 0.8m (est. 1762m) line in suburbia: sync at 13.1Mbps down 424kbps up _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel