From: "Kuan-Ying Lee (李冠穎)" <Kuan-Ying.Lee@mediatek.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"Qun-wei Lin (林群崴)" <Qun-wei.Lin@mediatek.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"Chinwen Chang (張錦文)" <chinwen.chang@mediatek.com>,
"Casper Li (李中榮)" <casper.li@mediatek.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"kbingham@kernel.org" <kbingham@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"urezki@gmail.com" <urezki@gmail.com>,
"angelogioacchino.delregno@collabora.com"
<angelogioacchino.delregno@collabora.com>,
"jan.kiszka@siemens.com" <jan.kiszka@siemens.com>
Subject: Re: [PATCH] scripts/gdb/vmalloc: fix vmallocinfo error
Date: Thu, 15 Feb 2024 03:02:01 +0000 [thread overview]
Message-ID: <8e2fbab4c611cc1bbf45f58e88736a0bd0bd6fa2.camel@mediatek.com> (raw)
In-Reply-To: <20240207155929.cc107bcc14b982789bdc9fab@linux-foundation.org>
On Wed, 2024-02-07 at 15:59 -0800, Andrew Morton wrote:
>
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
> On Wed, 7 Feb 2024 15:56:23 -0800 Andrew Morton <
> akpm@linux-foundation.org> wrote:
>
> > > [1]
> https://lore.kernel.org/linux-mm/20240102184633.748113-1-urezki@gmail.com/
> >
> > vmap_area_list was removed by
> https://lkml.kernel.org/r/20240102184633.748113-6-urezki@gmail.com
> >
> > So I think this patch is actually a fix against mm.git:mm-
> unstable's
> > mm-vmalloc-remove-vmap_area_list.patch?
> >
Yes, you are right.
Thanks for helping to fix the commit message.
> > However this gdb function was probably probably broken earlier in
> that
> > series, so perhaps this patch would be best staged as a predecessor
> to
> > Ulad's vmalloc series.
>
> ie, this:
>
>
> From: Kuan-Ying Lee <Kuan-Ying.Lee@mediatek.com>
> Subject: scripts/gdb/vmalloc: fix vmallocinfo error
> Date: Wed, 7 Feb 2024 16:58:51 +0800
>
> The patch series "Mitigate a vmap lock contention" removes
> vmap_area_list,
> which will break the gdb vmallocinfo command:
>
> (gdb) lx-vmallocinfo
> Python Exception <class 'gdb.error'>: No symbol "vmap_area_list" in
> current context.
> Error occurred in Python: No symbol "vmap_area_list" in current
> context.
>
> So we can instead use vmap_nodes to iterate all vmallocinfo.
>
> Link:
> https://lkml.kernel.org/r/20240207085856.11190-1-Kuan-Ying.Lee@mediatek.com
> Signed-off-by: Kuan-Ying Lee <Kuan-Ying.Lee@mediatek.com>
> Cc: Casper Li <casper.li@mediatek.com>
> Cc: AngeloGioacchino Del Regno <
> angelogioacchino.delregno@collabora.com>
> Cc: Chinwen Chang <chinwen.chang@mediatek.com>
> Cc: Jan Kiszka <jan.kiszka@siemens.com>
> Cc: Kieran Bingham <kbingham@kernel.org>
> Cc: Matthias Brugger <matthias.bgg@gmail.com>
> Cc: Qun-Wei Lin <qun-wei.lin@mediatek.com>
> Cc: Uladzislau Rezki (Sony) <urezki@gmail.com>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>
> scripts/gdb/linux/vmalloc.py | 56 +++++++++++++++++---------------
> -
> 1 file changed, 29 insertions(+), 27 deletions(-)
>
> --- a/scripts/gdb/linux/vmalloc.py~scripts-gdb-vmalloc-fix-
> vmallocinfo-error
> +++ a/scripts/gdb/linux/vmalloc.py
> @@ -29,32 +29,34 @@ class LxVmallocInfo(gdb.Command):
> if not constants.LX_CONFIG_MMU:
> raise gdb.GdbError("Requires MMU support")
>
> - vmap_area_list = gdb.parse_and_eval('vmap_area_list')
> - for vmap_area in lists.list_for_each_entry(vmap_area_list,
> vmap_area_ptr_type, "list"):
> - if not vmap_area['vm']:
> - gdb.write("0x%x-0x%x %10d vm_map_ram\n" %
> (vmap_area['va_start'], vmap_area['va_end'],
> - vmap_area['va_end'] - vmap_area['va_start']))
> - continue
> - v = vmap_area['vm']
> - gdb.write("0x%x-0x%x %10d" % (v['addr'], v['addr'] +
> v['size'], v['size']))
> - if v['caller']:
> - gdb.write(" %s" % str(v['caller']).split(' ')[-1])
> - if v['nr_pages']:
> - gdb.write(" pages=%d" % v['nr_pages'])
> - if v['phys_addr']:
> - gdb.write(" phys=0x%x" % v['phys_addr'])
> - if v['flags'] & constants.LX_VM_IOREMAP:
> - gdb.write(" ioremap")
> - if v['flags'] & constants.LX_VM_ALLOC:
> - gdb.write(" vmalloc")
> - if v['flags'] & constants.LX_VM_MAP:
> - gdb.write(" vmap")
> - if v['flags'] & constants.LX_VM_USERMAP:
> - gdb.write(" user")
> - if v['flags'] & constants.LX_VM_DMA_COHERENT:
> - gdb.write(" dma-coherent")
> - if is_vmalloc_addr(v['pages']):
> - gdb.write(" vpages")
> - gdb.write("\n")
> + nr_vmap_nodes = gdb.parse_and_eval('nr_vmap_nodes')
> + for i in range(0, nr_vmap_nodes):
> + vn = gdb.parse_and_eval('&vmap_nodes[%d]' % i)
> + for vmap_area in
> lists.list_for_each_entry(vn['busy']['head'], vmap_area_ptr_type,
> "list"):
> + if not vmap_area['vm']:
> + gdb.write("0x%x-0x%x %10d vm_map_ram\n" %
> (vmap_area['va_start'], vmap_area['va_end'],
> + vmap_area['va_end'] -
> vmap_area['va_start']))
> + continue
> + v = vmap_area['vm']
> + gdb.write("0x%x-0x%x %10d" % (v['addr'], v['addr'] +
> v['size'], v['size']))
> + if v['caller']:
> + gdb.write(" %s" % str(v['caller']).split(' ')[-
> 1])
> + if v['nr_pages']:
> + gdb.write(" pages=%d" % v['nr_pages'])
> + if v['phys_addr']:
> + gdb.write(" phys=0x%x" % v['phys_addr'])
> + if v['flags'] & constants.LX_VM_IOREMAP:
> + gdb.write(" ioremap")
> + if v['flags'] & constants.LX_VM_ALLOC:
> + gdb.write(" vmalloc")
> + if v['flags'] & constants.LX_VM_MAP:
> + gdb.write(" vmap")
> + if v['flags'] & constants.LX_VM_USERMAP:
> + gdb.write(" user")
> + if v['flags'] & constants.LX_VM_DMA_COHERENT:
> + gdb.write(" dma-coherent")
> + if is_vmalloc_addr(v['pages']):
> + gdb.write(" vpages")
> + gdb.write("\n")
>
> LxVmallocInfo()
> _
>
prev parent reply other threads:[~2024-02-15 3:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 8:58 Kuan-Ying Lee
2024-02-07 23:56 ` Andrew Morton
2024-02-07 23:59 ` Andrew Morton
2024-02-08 18:27 ` Uladzislau Rezki
2024-02-15 3:02 ` Kuan-Ying Lee (李冠穎) [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8e2fbab4c611cc1bbf45f58e88736a0bd0bd6fa2.camel@mediatek.com \
--to=kuan-ying.lee@mediatek.com \
--cc=Qun-wei.Lin@mediatek.com \
--cc=akpm@linux-foundation.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=casper.li@mediatek.com \
--cc=chinwen.chang@mediatek.com \
--cc=jan.kiszka@siemens.com \
--cc=kbingham@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=matthias.bgg@gmail.com \
--cc=urezki@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox