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=-7.0 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED 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 BD7CDC4363A for ; Wed, 28 Oct 2020 18:59:15 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (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 3BDAC24811 for ; Wed, 28 Oct 2020 18:59:15 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="XbrdNWGl"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="0wRwxQSg" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 3BDAC24811 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+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=merlin.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=nW7k5dFoaVl1Gg4qW9CjoQoQ9yPtdeG5/oR0sb6M5No=; b=XbrdNWGlMpNVIzAqo88imvc0j YGihg+7aKW+vf5TiTmFosPzhHZzHEGfVgk4pR0VCBPyzdFkiFThNHZ1X4nvd8BtUVyr+t+RRNDBJ1 5nsFmBGew8TAQ/vo636Nc9OzZqmqkX4epF7pfzLzDkCRYddVrS+ObRimFFztin2ItO3a7syJ4XA6b beoa4pLjxsljzTcY1wiVPhFo06HJrWpUU7wYSmyF38rJHTRX5edenv8T3gmvGsbbpGYLK9Gj1qaTy hgsu6cmMvR/AoZUPYVH+bHatHBKRD8uyvJf6KvUcTZDaHRtU56Ew9/et+NLzuSXy8ocRwS9i12oaD cS4AKovBg==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1kXqdv-0006V1-FB; Wed, 28 Oct 2020 18:57:55 +0000 Received: from mail.kernel.org ([198.145.29.99]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1kXqdt-0006UG-2y; Wed, 28 Oct 2020 18:57:54 +0000 Received: from kernel.org (unknown [87.70.96.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 1B5552473E; Wed, 28 Oct 2020 18:57:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1603911472; bh=zK9DfVuZHDzMdXj+yhDB8KulDOu8wW0+2VHqzzJ4VCs=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=0wRwxQSg4yE6tWskIfT82ofwXzSEJ/5NZugomFl0MhuujRXgT16OkYNSNiruGCQgb 4FmuFCHOOX4U7+tixFCp9eSridGpAq2f1ngfZ2ujosWNGX6mwHBQzCWsAku7+1/9jF 4Ekc11AXMUb29fsDTzF2sQtG1jcmaJnC2BBUIYCs= Date: Wed, 28 Oct 2020 20:57:41 +0200 From: Mike Rapoport To: Michael Schmitz Subject: Re: [PATCH 11/13] m68k/mm: make node data and node setup depend on CONFIG_DISCONTIGMEM Message-ID: <20201028185741.GI1428094@kernel.org> References: <20201027112955.14157-1-rppt@kernel.org> <20201027112955.14157-12-rppt@kernel.org> <20201028111631.GF1428094@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-20201028_145753_382404_2BA816DA X-CRM114-Status: GOOD ( 39.36 ) 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: "linux-ia64@vger.kernel.org" , "open list:DOCUMENTATION" , Catalin Marinas , Linux MM , Will Deacon , Greg Ungerer , Jonathan Corbet , Meelis Roos , Russell King , Mike Rapoport , Geert Uytterhoeven , Matt Turner , arcml , Alexey Dobriyan , linux-m68k , John Paul Adrian Glaubitz , Linux ARM , Tony Luck , Vineet Gupta , Linux Kernel Mailing List , alpha , Linux FS Devel , Andrew Morton Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, Oct 29, 2020 at 07:14:38AM +1300, Michael Schmitz wrote: > Hi Mike, > = > On 29/10/20 12:16 AM, Mike Rapoport wrote: > > Hi Geert, > > = > > On Wed, Oct 28, 2020 at 10:25:49AM +0100, Geert Uytterhoeven wrote: > > > Hi Mike, > > > = > > > On Tue, Oct 27, 2020 at 12:31 PM Mike Rapoport wrot= e: > > > > From: Mike Rapoport > > > > = > > > > The pg_data_t node structures and their initialization currently de= pends on > > > > !CONFIG_SINGLE_MEMORY_CHUNK. Since they are required only for DISCO= NTIGMEM > > > > make this dependency explicit and replace usage of > > > > CONFIG_SINGLE_MEMORY_CHUNK with CONFIG_DISCONTIGMEM where appropria= te. > > > > = > > > > The CONFIG_SINGLE_MEMORY_CHUNK was implicitly disabled on the ColdF= ire MMU > > > > variant, although it always presumed a single memory bank. As there= is no > > > > actual need for DISCONTIGMEM in this case, make sure that ColdFire = MMU > > > > systems set CONFIG_SINGLE_MEMORY_CHUNK to 'y'. > > > > = > > > > Signed-off-by: Mike Rapoport > > > Thanks for your patch! > > > = > > > > --- > > > > arch/m68k/Kconfig.cpu | 6 +++--- > > > > arch/m68k/include/asm/page_mm.h | 2 +- > > > > arch/m68k/mm/init.c | 4 ++-- > > > > 3 files changed, 6 insertions(+), 6 deletions(-) > > > Is there any specific reason you didn't convert the checks for > > > CONFIG_SINGLE_MEMORY_CHUNK in arch/m68k/kernel/setup_mm.c > > In arch/m68k/kernel/setup_mm.c the CONFIG_SINGLE_MEMORY_CHUNK is needed > > for the case when a system has two banks, the kernel is loaded into the > > second bank and so the first bank cannot be used as normal memory. It > > does not matter what memory model will be used in this case. > = > = > That case used to be detected just fine at run time (by dint of the second > memory chunk having an address below the first; the chunk the kernel resi= des > in is always listed first), even without using CONFIG_SINGLE_MEMORY_CHUNK. = Right, CONFIG_SINGLE_MEMORY_CHUNK in arch/m68k/kernel/setup_mm.c is used to force using a single bank of memory regardless of run time detection. = > Unless you changed that behaviour (and I see nothing in your patch that > would indicate that), this is still true. > = > Converting the check as Geert suggested, without also adding a test for > out-of-order memory bank addresses, would implicitly treat DISCONTIGMEM a= s=A0 > SINGLE_MEMORY_CHUNK, regardless of bank ordering. I don't think that is w= hat > we really want? It is in a way the case now when !SINGLE_MEMORY_CHUNK =3D=3D DISCONTIGMEM. So forcing SIGNLE_MEMORY_CHUNK at compile time would also mean forcing FLATMEM. After these changes I think SINGLE_MEMORY_CHUNK is not needed at all. > Cheers, > = > =A0=A0=A0 Michael > = > = > > = > > > and arch/m68k/include/asm/virtconvert.h? > > I remember I had build errors and troubles with include file > > dependencies if I changed it there, but I might be mistaken. I'll > > recheck again. > > = > > > Gr{oetje,eeting}s, > > > = > > > Geert > > > = > > > -- = > > > Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linu= x-m68k.org > > > = > > > In personal conversations with technical people, I call myself a hack= er. But > > > when I'm talking to journalists I just say "programmer" or something = like that. > > > -- Linus Torvalds -- = Sincerely yours, Mike. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel