Received: by 10.223.176.46 with SMTP id f43csp3397688wra; Mon, 22 Jan 2018 13:33:38 -0800 (PST) X-Google-Smtp-Source: AH8x227AKqtFFfjOC3Do5gH13ydJo0hLu2oXnGE8Ge9NBNTcgtWHHPKoG1si6J21eiPHxWm542Sv X-Received: by 10.36.1.66 with SMTP id 63mr387846itk.104.1516656818539; Mon, 22 Jan 2018 13:33:38 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516656818; cv=none; d=google.com; s=arc-20160816; b=ECkY1IabZR83aUlXia5XlRYUvj89LYgyaeb1jsyTCPFx4fcLnEXd/Z5/4KX2/E4Tke R50hcLVJSoaB5tvqTtNj6G4kAghX0pE41wQaIdjjTAuddGy0vbqplI+goWpwA1ruoFzr eYrpKgbKNInOOpRsnZIrL0mlACmkNVcdlM0buPT0UwxovnAChxDfq45RtYiSmfKsdQiz TpABXBI3J1R0+GBAPIvcMbB/XYga/jI7Ck3dLQYeQ1E6DCjyM0eUVpY1hShTo5qkh+0L 02uoV3bhWYXjVpKSuD/Me6Ig/hCBqvgvOzg8XG7vIUM9vkBmwr7X8gBfdHHfuVj2ziLC x+jQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature:arc-authentication-results; bh=2bG6tCJ+CnkwphOTScIGw700edX4MUGmZ16SHmn4pYM=; b=lQ4osYgTm5Ja0SDDlxqbxY34VW6poexg0j3H+uyvtz9aXEKS2bVscA/n9PSqyBSNZ0 0p1R1GojAbWEu7oJLmiCmkObZCRIW0wXi2GHKe+LCyIHcowBa3Pppgl22MHJ8lvFKNON 5fGnZ77tvVmPmgsHCi1r66aK6pHk3q5YTLqvbCgdJvenUVCPlAKpJeu3xlu3Vjf2hL7P wpd1FI9B+Ah2WJBu9n48ey0u1vc4U3VJStce4GiqSM+2QNNMZCBeKpSQ8NbugGfcKztB 1xdp6ZFVgnuuQI1LgOz6EEspYU/nGSTTNCKIhwQfzyvAXn9uU1/erI4KRia65ux/cD79 mXpQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=XR8lVy0g; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d65si5913862iod.233.2018.01.22.13.33.24; Mon, 22 Jan 2018 13:33:38 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=XR8lVy0g; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751206AbeAVVdE (ORCPT + 99 others); Mon, 22 Jan 2018 16:33:04 -0500 Received: from mail-lf0-f67.google.com ([209.85.215.67]:34592 "EHLO mail-lf0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750996AbeAVVdC (ORCPT ); Mon, 22 Jan 2018 16:33:02 -0500 Received: by mail-lf0-f67.google.com with SMTP id k19so12443615lfj.1 for ; Mon, 22 Jan 2018 13:33:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=2bG6tCJ+CnkwphOTScIGw700edX4MUGmZ16SHmn4pYM=; b=XR8lVy0g6V8dhW1ct2MnyDFCbg9qz17l7rr2cO+6paGX6CRKI31ZAPr8WvLIdH7HSP f0OGdMxlv/MV0wjNrcZ++5j/OnxZ+a4gYhl+kMcJODlxYj/8QoSrw3FH2jQt7uxEZrOx zdFirzD6oipvY43grimhPwnTJKnNxDuuhCQ7FEXRKtScGAKSX/zoE4I9VWo1eP3u+Qyy ruJ6psrUJKejq0svqU6FEUXKLxjpYlip70D+079Tq1zkNo2eeps27bafll3y1BdB18yy BC0o26ufuZ2rXvCfnqTwdFNcjdqIGtdPh8oNpX/jSiAfvEVlU+YTyEm0ao4CDODjY3sX C+oQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=2bG6tCJ+CnkwphOTScIGw700edX4MUGmZ16SHmn4pYM=; b=Kgd4DqAgJod8ecufoeIpcklawqIAmQih3yrsDFpuuz6koZoePNjESoujPN53hZG+vY Km1iEfY4ASlZ03qvOqnr3JHZcQ7TejKmEWhN07q1Q3sH5dZjv3l8kaj0OluJ5T1gPZyG ubUXI6N+7TqOgoerM7mm66p/KbkoaZGfD0f6euMWMNNHmCh9OKxF0y5p+HhGMxXtneio wwbxciv/rnLup+H46dXYX4gC3brpqWtVz32yz2WpT6KBkdlEHCCF/srXYp+oc8pXry+W baiNp2neYY/zw3NsN+Oc3cam05xy4pm/fyNar5Uaym682mO/uTecYnRqGbHgsXS+NCpd 2EAg== X-Gm-Message-State: AKwxyte26vf6KWbEyE5byo0VWio9M3r4xJiij/qDwkgZKrjMSzBJRNr5 NGx6CLMXQS/+CSE8Cw/8jqk= X-Received: by 10.46.23.141 with SMTP id 13mr132652ljx.29.1516656781178; Mon, 22 Jan 2018 13:33:01 -0800 (PST) Received: from mobilestation ([95.79.164.146]) by smtp.gmail.com with ESMTPSA id p83sm2731102lfg.41.2018.01.22.13.32.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 22 Jan 2018 13:33:00 -0800 (PST) Date: Tue, 23 Jan 2018 00:33:12 +0300 From: Serge Semin To: Matt Redfearn Cc: ralf@linux-mips.org, miodrag.dinic@mips.com, jhogan@kernel.org, goran.ferenc@mips.com, david.daney@cavium.com, paul.gortmaker@windriver.com, paul.burton@mips.com, alex.belits@cavium.com, Steven.Hill@cavium.com, alexander.sverdlin@nokia.com, kumba@gentoo.org, marcin.nowakowski@mips.com, James.hogan@mips.com, Peter.Wotton@mips.com, Sergey.Semin@t-platforms.ru, linux-mips@linux-mips.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 00/14] MIPS: memblock: Switch arch code to NO_BOOTMEM Message-ID: <20180122213312.GB32024@mobilestation> References: <20180117222312.14763-1-fancer.lancer@gmail.com> <2fd1f530-e6c6-a528-5827-c3ecc8b4a81c@mips.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2fd1f530-e6c6-a528-5827-c3ecc8b4a81c@mips.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jan 22, 2018 at 04:36:40PM +0000, Matt Redfearn wrote: Hello Matt, > Hi Serge, > > On 17/01/18 22:22, Serge Semin wrote: > >Even though it's common to see the architecture code using both > >bootmem and memblock early memory allocators, it's not good for > >multiple reasons. First of all, it's redundant to have two > >early memory allocator while one would be more than enough from > >functionality and stability points of view. Secondly, some new > >features introduced in the kernel utilize the methods of the most > >modern allocator ignoring the older one. It means the architecture > >code must keep the both subsystems up synchronized with information > >about memory regions and reservations, which leads to the code > >complexity increase, that obviously increases bugs probability. > >Finally it's better to keep all the architectures code unified for > >better readability and code simplification. All these reasons lead > >to one conclusion - arch code should use just one memory allocator, > >which is supposed to be memblock as the most modern and already > >utilized by the most of the kernel platforms. This patchset is > >mostly about it. > > > >One more reason why the MIPS arch code should finally move to > >memblock is a BUG somewhere in the initialization process, when > >CMA is activated: > > > >[ 0.248762] BUG: Bad page state in process swapper/0 pfn:01f93 > >[ 0.255415] page:8205b0ac count:0 mapcount:-127 mapping: (null) index:0x1 > >[ 0.263172] flags: 0x40000000() > >[ 0.266723] page dumped because: nonzero mapcount > >[ 0.272049] Modules linked in: > >[ 0.275511] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.4.88-module #5 > >[ 0.282900] Stack : 00000000 00000000 80b6dd6a 0000003a 00000000 00000000 80930000 8092bff4 > > 86073a14 80ac88c7 809f21ac 00000000 00000001 80b6998c 00000400 00000000 > > 80a00000 801822e8 80b6dd68 00000000 00000002 00000000 809f8024 86077ccc > > 80b80000 801e9328 809fcbc0 00000000 00000400 00010000 86077ccc 86073a14 > > 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > > ... > >[ 0.323148] Call Trace: > >[ 0.325935] [<8010e7c4>] show_stack+0x8c/0xa8 > >[ 0.330859] [<80404814>] dump_stack+0xd4/0x110 > >[ 0.335879] [<801f0bc0>] bad_page+0xfc/0x14c > >[ 0.340710] [<801f0e04>] free_pages_prepare+0x1f4/0x330 > >[ 0.346632] [<801f36c4>] __free_pages_ok+0x2c/0x104 > >[ 0.352154] [<80b23a40>] init_cma_reserved_pageblock+0x5c/0x74 > >[ 0.358761] [<80b29390>] cma_init_reserved_areas+0x1b4/0x240 > >[ 0.365170] [<8010058c>] do_one_initcall+0xe8/0x27c > >[ 0.370697] [<80b14e60>] kernel_init_freeable+0x200/0x2c4 > >[ 0.376828] [<808faca4>] kernel_init+0x14/0x104 > >[ 0.381939] [<80107598>] ret_from_kernel_thread+0x14/0x1c > > > >The bugus pfn seems to be the one allocated for bootmem allocator > >pages and hasn't been freed before letting the CMA working with its > >areas. Anyway the bug is solved by this patchset. > > > >Another reason why this patchset is useful is that it fixes the fdt > >reserved-memory nodes functionality for MIPS. Really it's bug to have > >the fdt reserved nodes scanning before the memblock is > >fully initialized (calling early_init_fdt_scan_reserved_mem before > >bootmem_init is called). Additionally no-map flag of the > >reserved-memory node hasn't been taking into account. This patchset > >fixes all of these. > > > >As you probably remember I already did another attempt to merge a > >similar functionality into the kernel. This time the patchset got > >to be less complex (14 patches vs 21 last time) and fixes the > >platform code like SGI IP27 and Loongson3, which due to being > >NUMA introduce its own memory initialization process. Although > >I have much doubt in SGI IP27 code operability in the first place, > >since it got prom_meminit() method of early memory initialization, > >which hasn't been called at any other place in the kernel. It must > >have been left there unrenamed after arch/mips/mips-boards/generic > >code had been discarded. > > > >Here are the list of folks, who agreed to perform some tests of > >the patchset: > >Alexander Sverdlin - Octeon2 > >Matt Redfearn - Loongson3, etc > > > I have applied and tested these patches on various platforms that we have > available here, and the kernel appears to boot and get to userspace as > normal on the following platforms: > > UTM8 (Cavium Octeon III) > Creator CI20 > Creator CI40 > Loongson3a > MIPS Boston > MIPS Malta > MIPS SEAD3 > > Aside from the CONFIG_RELOCATABLE stuff, this looks pretty tidy to me. Thank you very much for the tests. It is great to see interest from the community. From my side I've tested the patchset on: Baikal-T (MIPS Warrior p5600) Regards, -Sergey > > Thanks, > Matt > > > >Joshua Kinard - IP27 > >Marcin Nowakowski > >Thanks to you all in regards and for everybody, who will be involved > >in reviewing and testing. > > > >The patchset is applied on top of kernel 4.15-rc8 and can be found > >submitted at my repo: > >https://github.com/fancer/Linux-kernel-MIPS-memblock-project > > > >Signed-off-by: Serge Semin > > > >Serge Semin (14): > > MIPS: memblock: Add RESERVED_NOMAP memory flag > > MIPS: memblock: Surely map BSS kernel memory section > > MIPS: memblock: Reserve initrd memory in memblock > > MIPS: memblock: Discard bootmem initialization > > MIPS: memblock: Add reserved memory regions to memblock > > MIPS: memblock: Reserve kdump/crash regions in memblock > > MIPS: memblock: Mark present sparsemem sections > > MIPS: memblock: Simplify DMA contiguous reservation > > MIPS: memblock: Allow memblock regions resize > > MIPS: memblock: Perform early low memory test > > MIPS: memblock: Print out kernel virtual mem layout > > MIPS: memblock: Discard bootmem from Loongson3 code > > MIPS: memblock: Discard bootmem from SGI IP27 code > > MIPS: memblock: Deactivate bootmem allocator > > > > arch/mips/Kconfig | 2 +- > > arch/mips/include/asm/bootinfo.h | 1 + > > arch/mips/kernel/prom.c | 8 +- > > arch/mips/kernel/setup.c | 218 +++++++++------------ > > arch/mips/loongson64/loongson-3/numa.c | 16 +- > > arch/mips/mm/init.c | 47 +++++ > > arch/mips/sgi-ip27/ip27-memory.c | 9 +- > > 7 files changed, 153 insertions(+), 148 deletions(-) > >