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 kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1BBE6C77B7F for ; Wed, 17 May 2023 13:42:32 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 8F2C4900005; Wed, 17 May 2023 09:42:31 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 8A275900004; Wed, 17 May 2023 09:42:31 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 7B928900005; Wed, 17 May 2023 09:42:31 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0015.hostedemail.com [216.40.44.15]) by kanga.kvack.org (Postfix) with ESMTP id 6D78C900004 for ; Wed, 17 May 2023 09:42:31 -0400 (EDT) Received: from smtpin08.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay06.hostedemail.com (Postfix) with ESMTP id 2B818ADE62 for ; Wed, 17 May 2023 13:42:31 +0000 (UTC) X-FDA: 80799861702.08.7DC1C53 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by imf11.hostedemail.com (Postfix) with ESMTP id 3FF604000F for ; Wed, 17 May 2023 13:42:28 +0000 (UTC) Authentication-Results: imf11.hostedemail.com; dkim=pass header.d=kernel.org header.s=k20201202 header.b=D1tQQ12g; spf=pass (imf11.hostedemail.com: domain of rppt@kernel.org designates 139.178.84.217 as permitted sender) smtp.mailfrom=rppt@kernel.org; dmarc=pass (policy=none) header.from=kernel.org ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1684330949; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=gqW+JVRVGZRzJXTObm9fctqGEmx8oekV3cjdIC3UnVg=; b=nKl3Z8cQYLK30XXJup8PwW1OBaNH2zbsjsOs6MUcqwDZSyVfXLnqEfAD/lbu/1AQhZFZnf TJc+5DJBOZ/C48ZpQov0jC5xoh2W/MRXclQF1V3m0+fGi2CDVCGpcF24KtWocGVyMn8wzj GvgquaJpkd3VxjwlCRUgvmA2S8ibxqk= ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1684330949; a=rsa-sha256; cv=none; b=Ty7+v859Abla7svF7rDDNHvNR7KwPkY6Ck80vjlPAZ7QNxEIdfYBbc9EaIDl7pLjvvCFIQ K3N0IV/QRrRUbB3LubtSS9sDdALCRg3T3gbimQed+TxjSzSjJz61whlIMv68PsHdqYLArF 94QkSeKYZgDQIxGsI5sYtrmfTRsDt6k= ARC-Authentication-Results: i=1; imf11.hostedemail.com; dkim=pass header.d=kernel.org header.s=k20201202 header.b=D1tQQ12g; spf=pass (imf11.hostedemail.com: domain of rppt@kernel.org designates 139.178.84.217 as permitted sender) smtp.mailfrom=rppt@kernel.org; dmarc=pass (policy=none) header.from=kernel.org 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 0A74363F0F; Wed, 17 May 2023 13:42:28 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id A1A48C4339B; Wed, 17 May 2023 13:42:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1684330947; bh=Vl7/xGCMjGm7dBBBvSimFFnqjAVwiGrWBbtqILvy0z0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=D1tQQ12gARaIbGtqJKLM1xh/nNHWY3En2nO5yUCtYrRpbIN479qk10Ze8qHBGqKLr 1oxkP+BzE8FloEccxCeDfIi3idbMJrqklh7LGOHV5EgKTlzWoEho0+77MliY5KxJkv p20oHaSS2mWO0F+jH8tCO7jwWZRirOE40/5rJVc23AcMdEQTj8H7iHXeHLDYThKEvi fO6SBSjFqut0TbmO6sF63UwioF8NrlMQspHtIdjgIncH/1ruypUsQM/Nwx7R1hgPAg p+tFeaWKerVJumdssw13WXYyMUtFJ61zianwjYEfIAJDOh1vwgKs+thhIYxtkgltCH E4kUq+AKDdNtw== Date: Wed, 17 May 2023 16:42:21 +0300 From: Mike Rapoport To: Anshuman Khandual Cc: Yuwei Guan , akpm@linux-foundation.org, tsahu@linux.ibm.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2] memblock: Add flags and nid info in memblock debugfs Message-ID: References: <20230517025747.230-1-ssawgyw@gmail.com> <52fa3a4f-5467-7b68-334c-4280d3925b39@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <52fa3a4f-5467-7b68-334c-4280d3925b39@arm.com> X-Stat-Signature: 5j6eyjp44wfn43dr8my575d8yfp6cbmd X-Rspamd-Server: rspam03 X-Rspam-User: X-Rspamd-Queue-Id: 3FF604000F X-HE-Tag: 1684330948-928276 X-HE-Meta: U2FsdGVkX18rpqx6YqYHI710lkXgWfS2oKixvQyzZoPytFZw594w2GD2O0b3/Oz91e4dskaO619DeQONP9A5zoFJbFcKV0Y15rK33voEYhiQy6uyOzRozVMJCqcZM8GQoWNGVdXQnF9Z1NI5Xuv3zdi9K9LbA+kiyL3F0yhx4M7su8VzHQk7A4NCqzGxauqTbRdp2ofsvvFrw0eK/KBne0gmr+jq9dytlLwj/FGxD5CSo9UxFpcYR8SJRrH6QFgbk1bCSOmLQQESSVnm2gdAYgFYFmchbJKlsN+6gM2PnZcO+2MS2T5mrw1uvE5ARA4sgzECqQCFYttIDZdBsrkclEIoVTBZ0PjK6l/RxfjrPVqtv7h9NtgSTRpsMju8G2Ojj1jiztqxVK1QOADkHYQ1j5qOWHqZGdSZ4+Mtmw4sN2nt8LTo7/DGluH6QB5UzxzMQyYlQlGm1OvVnW+EAPf63u03YTlYJwu6tv8+VioHq+wZMK0Tx8W5EHAOZgOsj9RwqAdcCcSjNfA5PrDf1DxNfLLa4EUz3fv3DOOfkOYzOuYLTbJQZhsO1uo5GOeOOj1SHrNrKlFRnd83QDM7gtgBrlYSlx4/U2/h/xmAEEGEbWfrqamI4iQ9hRuqfbenpgW5LvA7mt2iUzuNBuBma/XYGSBSzzIfPeBnUjG3/AoXv2oERzsarUINOepqsf9AB7ALOsIgCLkH66Rg0psif9vzFvi6W2LqdNzb1+lUSbTtsxv/xW2erCnFf8OholKc3SE6MJ5plOcGTtv+GNRzCM2teg7m2/JhkF6FP+QoOgAioisy4EMrNWMnaVAB1zMWhUyoEocGI470tRNXCZG/5XK7RLBxDXHjTg1UkCzg91nyTdhcEbJwOkyrgmaQe5VvMQG7BWysbj70g3Onlv5pKx1goWU1WQJwg3Uub9TKmSMgKkI38JmyemVb5MI7BK0o9F2LSrf2wAdyma736noT9Zk mKYGrtTL gp7f9GkONnSm2P7i7KC4cEdhB+NfJSzCBrylpvZhEgB1neYOpLdK5TrGBX0k/0gVz0joOSJeEirM35eHvck+/r8XlIrVM/j/AMbygyg76b/i2zMulmpVKZbkrG0GKSEAwc1CS5+l89pZmdR7g5cMWFhqijUKaSrsIi9n8G/2xYQbGcrX1eymq/5akXOINTXwfHvdAt1+BFmKA3tliiidEPH8xMGCZjnIyZK/qluJE2bj9YF/3LjCVFPaJcnCyDRSeXhb36lM5t8cNdf+/tyzxHYSPiWpnj/ytuZ0drLhbMNP+DTD7cfFpwYbyrlAcd8ScmyEC36IxV7wO5bM= X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Wed, May 17, 2023 at 11:37:25AM +0530, Anshuman Khandual wrote: > > On 5/17/23 08:27, Yuwei Guan wrote: > > Currently, the memblock debugfs can display the count of memblock_type and > > the base and end of the reg. However, when the following scenario occurs, > > scenarios where the memblock flags or nid varies inside a single PA range ? > I guess the commit message description here can be improved to accommodate > such details. > > > the information in the existing debugfs cannot make it clear why the > > address is not consecutive. > > > > For example, > > cat /sys/kernel/debug/memblock/memory > > 0: 0x0000000080000000..0x00000000901fffff > > 1: 0x0000000090200000..0x00000000905fffff > > 2: 0x0000000090600000..0x0000000092ffffff > > 3: 0x0000000093000000..0x00000000973fffff > > 4: 0x0000000097400000..0x00000000b71fffff > > 5: 0x00000000c0000000..0x00000000dfffffff > > 6: 0x00000000e2500000..0x00000000f87fffff > > 7: 0x00000000f8800000..0x00000000fa7fffff > > 8: 0x00000000fa800000..0x00000000fd3effff > > 9: 0x00000000fd3f0000..0x00000000fd3fefff > > 10: 0x00000000fd3ff000..0x00000000fd7fffff > > 11: 0x00000000fd800000..0x00000000fd901fff > > 12: 0x00000000fd902000..0x00000000fd909fff > > 13: 0x00000000fd90a000..0x00000000fd90bfff > > 14: 0x00000000fd90c000..0x00000000ffffffff > > 15: 0x0000000880000000..0x0000000affffffff > > > > So we can add flags and nid to this debugfs. > > > > For example, > > cat /sys/kernel/debug/memblock/memory > > cnt base..end flags nid > > These markers ^^^ are not aligned properly, and also might not be > required as well. > > > 0: 0x0000000080000000..0x00000000901fffff 0x0 0x0 > > 1: 0x0000000090200000..0x00000000905fffff 0x4 0x0 > > 2: 0x0000000090600000..0x0000000092ffffff 0x0 0x0 > > 3: 0x0000000093000000..0x00000000973fffff 0x4 0x0 > > 4: 0x0000000097400000..0x00000000b71fffff 0x0 0x0 > > 5: 0x00000000c0000000..0x00000000dfffffff 0x0 0x0 > > 6: 0x00000000e2500000..0x00000000f87fffff 0x0 0x0 > > 7: 0x00000000f8800000..0x00000000fa7fffff 0x4 0x0 > > 8: 0x00000000fa800000..0x00000000fd3effff 0x0 0x0 > > 9: 0x00000000fd3f0000..0x00000000fd3fefff 0x4 0x0 > > 10: 0x00000000fd3ff000..0x00000000fd7fffff 0x0 0x0 > > 11: 0x00000000fd800000..0x00000000fd901fff 0x4 0x0 > > 12: 0x00000000fd902000..0x00000000fd909fff 0x0 0x0 > > 13: 0x00000000fd90a000..0x00000000fd90bfff 0x4 0x0 > > 14: 0x00000000fd90c000..0x00000000ffffffff 0x0 0x0 > > 15: 0x0000000880000000..0x0000000affffffff 0x0 0x0 > > > > Signed-off-by: Yuwei Guan > > Reviewed-by: Tarun Sahu > > --- > > mm/memblock.c | 8 ++++++-- > > 1 file changed, 6 insertions(+), 2 deletions(-) > > > > diff --git a/mm/memblock.c b/mm/memblock.c > > index 511d4783dcf1..b36fb6b31e0f 100644 > > --- a/mm/memblock.c > > +++ b/mm/memblock.c > > @@ -2144,12 +2144,16 @@ static int memblock_debug_show(struct seq_file *m, void *private) > > int i; > > phys_addr_t end; > > > > + seq_puts(m, "cnt\tbase..end\tflags\tnid\n"); > > Please drop this. > > > + > > for (i = 0; i < type->cnt; i++) { > > reg = &type->regions[i]; > > end = reg->base + reg->size - 1; > > > > - seq_printf(m, "%4d: ", i); > > - seq_printf(m, "%pa..%pa\n", ®->base, &end); > > + seq_printf(m, "%d:\t", i); > > Why drop the existing %4d formatting qualifier ? > > > + seq_printf(m, "%pa..%pa\t", ®->base, &end); > > + seq_printf(m, "0x%x\t", reg->flags); > > Should there be ORed string values for each memblock flag ? > > enum memblock_flags { > MEMBLOCK_NONE = 0x0, /* No special request */ > MEMBLOCK_HOTPLUG = 0x1, /* hotpluggable region */ > MEMBLOCK_MIRROR = 0x2, /* mirrored region */ > MEMBLOCK_NOMAP = 0x4, /* don't add to kernel direct mapping */ > MEMBLOCK_DRIVER_MANAGED = 0x8, /* always detected via a driver */ > }; > > Something like NN | HT | MR | NM | DM ? These are not less cryptic than numbers :) Most of them are mutually exclusive, so maybe just spell them out fully, just shorten DRIVER_MANAGED to DRV_MNG? And make the flags dump the last to keep columns nicely aligned. > > + seq_printf(m, "0x%x\n", memblock_get_region_node(reg)); > > } > > return 0; > > } -- Sincerely yours, Mike.