Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp622019yba; Wed, 24 Apr 2019 07:03:03 -0700 (PDT) X-Google-Smtp-Source: APXvYqyPCaUnLxwUNGTPI8ccjymyAkf2/7Ng/XkxTETUd6IUXhd8w3o7r/9wxQImPh0yFKGU7/2g X-Received: by 2002:a63:6804:: with SMTP id d4mr30970323pgc.240.1556114583549; Wed, 24 Apr 2019 07:03:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556114583; cv=none; d=google.com; s=arc-20160816; b=hlQfMBwVMxvlDwf1SozoZCWi7FG3+Rrb7PecxQ1YAyR2cbiqWipwUase3GklequXhK f16J0esky5koJtJeVvG5KsHYIKjrjebcjezl0OIe8C/Xy5SGx0foppFpa2xW9Nakap5D pwmLwSLV2ZlkFisddiB4lPz2gw6cKevTmpC63mcqD3I3THxM0aNmrW/rBAA/V1/qJ7oI zgcSXrzTNxdvtiE6gAyo4fwNDDhlAyRqzIQSuzvKo2U4aOHWYoqNt4bB+Z9coMURSMWq 7MTQIhX8QPYCyTsjxnS27Kgil+nDv/2i1+VFtJAns111+4wjRLgYwhVDWNE9LxbFshqg Av9A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:user-agent:in-reply-to :content-disposition:mime-version:references:subject:cc:to:from:date; bh=nPuGF6IrrgNqdktrRh9QcnT2X2Ets7LSb7Z2zPH7lkU=; b=gVjtvOEfLXH6EM36tnKIMXz3TUxIF8fgHyZfRvW3SOGXyVp3knOm8N92ozYCq0YY/5 z9HIy7kkoeeDXSqTxphMZ3WBKfd3IcBqRahKZ2wUO68TLLW3+O0X4Ypgv4x3VxFD77C1 w6tMVfmAvLJQB7jI5e9QIIULFqm/j0tykiw+7zYccocLwkoB4iS9yJm7ewLkrnXr6f0X qm/D6BonPoMZqZB3xJrXTpwuysLD7xEqpPbEutLoI1e/35YLjKctv2G2UlMgoibU924d j9xxo0cBdeKZH0EWPfw+MwJJ7pcK9eK70ir6neuWsHx1WBaILY2tJMpJ7wh7jxlAPdvb b77w== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 31si19657613plk.42.2019.04.24.07.02.46; Wed, 24 Apr 2019 07:03:03 -0700 (PDT) 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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730630AbfDXNqB (ORCPT + 99 others); Wed, 24 Apr 2019 09:46:01 -0400 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:48596 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727331AbfDXNqA (ORCPT ); Wed, 24 Apr 2019 09:46:00 -0400 Received: from pps.filterd (m0098396.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x3ODeFeZ006538 for ; Wed, 24 Apr 2019 09:45:59 -0400 Received: from e06smtp03.uk.ibm.com (e06smtp03.uk.ibm.com [195.75.94.99]) by mx0a-001b2d01.pphosted.com with ESMTP id 2s2rc7j1s4-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Wed, 24 Apr 2019 09:45:59 -0400 Received: from localhost by e06smtp03.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Wed, 24 Apr 2019 14:45:57 +0100 Received: from b06cxnps3074.portsmouth.uk.ibm.com (9.149.109.194) by e06smtp03.uk.ibm.com (192.168.101.133) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Wed, 24 Apr 2019 14:45:51 +0100 Received: from b06wcsmtp001.portsmouth.uk.ibm.com (b06wcsmtp001.portsmouth.uk.ibm.com [9.149.105.160]) by b06cxnps3074.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id x3ODjo6f58064976 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 24 Apr 2019 13:45:50 GMT Received: from b06wcsmtp001.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 939FEA4060; Wed, 24 Apr 2019 13:45:50 +0000 (GMT) Received: from b06wcsmtp001.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 6E0E5A405C; Wed, 24 Apr 2019 13:45:49 +0000 (GMT) Received: from rapoport-lnx (unknown [9.148.8.112]) by b06wcsmtp001.portsmouth.uk.ibm.com (Postfix) with ESMTPS; Wed, 24 Apr 2019 13:45:49 +0000 (GMT) Date: Wed, 24 Apr 2019 16:45:47 +0300 From: Mike Rapoport To: Serge Semin Cc: Ralf Baechle , Paul Burton , James Hogan , Matt Redfearn , Andrew Morton , Michal Hocko , Greg Kroah-Hartman , Thomas Bogendoerfer , Huacai Chen , Stefan Agner , Stephen Rothwell , Alexandre Belloni , Juergen Gross , linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 08/12] mips: Dump memblock regions for debugging References: <20190423224748.3765-1-fancer.lancer@gmail.com> <20190423224748.3765-9-fancer.lancer@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190423224748.3765-9-fancer.lancer@gmail.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-TM-AS-GCONF: 00 x-cbid: 19042413-0012-0000-0000-000003131744 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 19042413-0013-0000-0000-0000214B6CE9 Message-Id: <20190424134547.GD6278@rapoport-lnx> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-04-24_09:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=938 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1904240109 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Apr 24, 2019 at 01:47:44AM +0300, Serge Semin wrote: > It is useful to have the whole memblock memory space printed to console > when basic memlock initializations are done. It can be performed by > ready-to-use method memblock_dump_all(), which prints the available > and reserved memory spaces if MEMBLOCK_DEBUG config is enabled. Nit: there's no MEMBLOCK_DEBUG config option but rather memblock=debug command line parameter ;-) > Lets call it at the very end of arch_mem_init() function, when > all memblock memory and reserved regions are defined, but before > any serious allocation is performed. > > Signed-off-by: Serge Semin > --- > arch/mips/kernel/setup.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/arch/mips/kernel/setup.c b/arch/mips/kernel/setup.c > index 2a1b2e7a1bc9..ca493fdf69b0 100644 > --- a/arch/mips/kernel/setup.c > +++ b/arch/mips/kernel/setup.c > @@ -824,6 +824,8 @@ static void __init arch_mem_init(char **cmdline_p) > /* Reserve for hibernation. */ > memblock_reserve(__pa_symbol(&__nosave_begin), > __pa_symbol(&__nosave_end) - __pa_symbol(&__nosave_begin)); > + > + memblock_dump_all(); > } > > static void __init resource_init(void) > -- > 2.21.0 > -- Sincerely yours, Mike.