mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Kuan-Ying Lee (李冠穎)" <Kuan-Ying.Lee@mediatek.com>
To: "matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
	"p.raghav@samsung.com" <p.raghav@samsung.com>,
	"kbingham@kernel.org" <kbingham@kernel.org>,
	"angelogioacchino.delregno@collabora.com" 
	<angelogioacchino.delregno@collabora.com>,
	"jan.kiszka@siemens.com" <jan.kiszka@siemens.com>,
	"mcgrof@kernel.org" <mcgrof@kernel.org>
Cc: "linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Qun-wei Lin (林群崴)" <Qun-wei.Lin@mediatek.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"Chinwen Chang (張錦文)" <chinwen.chang@mediatek.com>,
	"Andrew Yang (楊智強)" <Andrew.Yang@mediatek.com>
Subject: Re: [PATCH] scripts/gdb: fix 'lx-lsmod' show the wrong size
Date: Mon, 10 Jul 2023 08:51:50 +0000	[thread overview]
Message-ID: <0990cccb0d6361c2d824e4efdefa98a1980cf6b8.camel@mediatek.com> (raw)
In-Reply-To: <aad3e8fb-d16b-3fab-f17b-3e6645c946cd@samsung.com>

On Tue, 2023-07-04 at 14:11 +0200, Pankaj Raghav wrote:
>  	 
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
>  > 'lsmod' shows total core layout size, so we need to
> > sum up all the sections in core layout in gdb scripts.
> > 
> > / # lsmod
> > kasan_test 200704 0 - Live 0xffff80007f640000
> > 
> > Before patch:
> > (gdb) lx-lsmod
> > Address            Module                  Size  Used by
> > 0xffff80007f640000 kasan_test             36864  0
> > 
> > After patch:
> > (gdb) lx-lsmod
> > Address            Module                  Size  Used by
> > 0xffff80007f640000 kasan_test            200704  0
> > 
> > Fixes: b4aff7513df3 ("scripts/gdb: use mem instead of core_layout
> to get the module address")
> > Signed-off-by: Kuan-Ying Lee <Kuan-Ying.Lee@mediatek.com>
> > ---
> 
> Just one minor comment, but apart from that, feel free to add:
> 
> Reviewed-by: Pankaj Raghav <p.raghav@samsung.com>
> 
> > diff --git a/scripts/gdb/linux/modules.py
> b/scripts/gdb/linux/modules.py
> > index 261f28640f4c..84933c4c1083 100644
> > --- a/scripts/gdb/linux/modules.py
> > +++ b/scripts/gdb/linux/modules.py
> > @@ -73,11 +73,17 @@ class LxLsmod(gdb.Command):
> >                  "        " if utils.get_long_type().sizeof == 8
> else ""))
> >  
> >          for module in module_list():
> > -            layout = module['mem'][constants.LX_MOD_TEXT]
> > +            total_size = 0
> > +            for i in range(constants.LX_MOD_TEXT,
> constants.LX_MOD_RO_AFTER_INIT + 1):
> > +                layout = module['mem'][i]
> > +                if i == constants.LX_MOD_TEXT:
> > +                    text_addr = str(layout['base']).split()[0]
> > +                total_size += layout['size']
> > +
> >              gdb.write("{address} {name:<19}
> {size:>8}  {ref}".format(
> > -                address=str(layout['base']).split()[0],
> > +                address=text_addr,
> >                  name=module['name'].string(),
> > -                size=str(layout['size']),
> > +                size=str(total_size),
> >                  ref=str(module['refcnt']['counter'] - 1)))
> >  
> >              t = self._module_use_type.get_type().pointer()
> 
> We could slightly modify the code to remove the special condition
> with `i == constants.LX_MOD_TEXT`:
> 
> (I made changes on top of your patch)

Thanks for your suggestion.
I will upload v2.

> 
> diff --git a/scripts/gdb/linux/modules.py
> b/scripts/gdb/linux/modules.py
> index 84933c4c1083..f76a43bfa15f 100644
> --- a/scripts/gdb/linux/modules.py
> +++ b/scripts/gdb/linux/modules.py
> @@ -73,12 +73,12 @@ class LxLsmod(gdb.Command):
>                  "        " if utils.get_long_type().sizeof == 8 else
> ""))
> 
>          for module in module_list():
> +            text = module['mem'][constants.LX_MOD_TEXT]
> +            text_addr = str(text['base']).split()[0]
>              total_size = 0
> +
>              for i in range(constants.LX_MOD_TEXT,
> constants.LX_MOD_RO_AFTER_INIT + 1):
> -                layout = module['mem'][i]
> -                if i == constants.LX_MOD_TEXT:
> -                    text_addr = str(layout['base']).split()[0]
> -                total_size += layout['size']
> +                total_size += module['mem'][i]['size']
> 
>              gdb.write("{address} {name:<19}
> {size:>8}  {ref}".format(
>                  address=text_addr,

      reply	other threads:[~2023-07-10  8:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20230620094846eucas1p21dfc03b10384449dee5e67837ba3e72d@eucas1p2.samsung.com>
2023-06-20  9:48 ` Kuan-Ying Lee
2023-06-30  1:01   ` Kuan-Ying Lee (李冠穎)
2023-07-04 12:11   ` Pankaj Raghav
2023-07-10  8:51     ` 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=0990cccb0d6361c2d824e4efdefa98a1980cf6b8.camel@mediatek.com \
    --to=kuan-ying.lee@mediatek.com \
    --cc=Andrew.Yang@mediatek.com \
    --cc=Qun-wei.Lin@mediatek.com \
    --cc=angelogioacchino.delregno@collabora.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=mcgrof@kernel.org \
    --cc=p.raghav@samsung.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

all inboxes | Powered by JetHome®