From: Kuan-Ying Lee <Kuan-Ying.Lee@mediatek.com>
To: Jan Kiszka <jan.kiszka@siemens.com>,
Kieran Bingham <kbingham@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Cc: <chinwen.chang@mediatek.com>, <qun-wei.lin@mediatek.com>,
<linux-mm@kvack.org>, <linux-modules@vger.kernel.org>,
<casper.li@mediatek.com>, <akpm@linux-foundation.org>,
<linux-arm-kernel@lists.infradead.org>,
Kuan-Ying Lee <Kuan-Ying.Lee@mediatek.com>,
<linux-kernel@vger.kernel.org>,
<linux-mediatek@lists.infradead.org>
Subject: [PATCH 3/8] scripts/gdb/utils: add common type usage
Date: Tue, 25 Jul 2023 17:34:53 +0800 [thread overview]
Message-ID: <20230725093458.30064-4-Kuan-Ying.Lee@mediatek.com> (raw)
In-Reply-To: <20230725093458.30064-1-Kuan-Ying.Lee@mediatek.com>
Since we often use 'unsigned long', 'size_t', 'usigned int'
and 'struct page', we add these common types to utils.
Signed-off-by: Kuan-Ying Lee <Kuan-Ying.Lee@mediatek.com>
---
scripts/gdb/linux/utils.py | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
diff --git a/scripts/gdb/linux/utils.py b/scripts/gdb/linux/utils.py
index 9f44df13761e..7d5278d815fa 100644
--- a/scripts/gdb/linux/utils.py
+++ b/scripts/gdb/linux/utils.py
@@ -35,12 +35,32 @@ class CachedType:
long_type = CachedType("long")
+ulong_type = CachedType("unsigned long")
+uint_type = CachedType("unsigned int")
atomic_long_type = CachedType("atomic_long_t")
+size_t_type = CachedType("size_t")
+struct_page_type = CachedType("struct page")
+
+def get_uint_type():
+ global uint_type
+ return uint_type.get_type()
+
+def get_page_type():
+ global struct_page_type
+ return struct_page_type.get_type()
def get_long_type():
global long_type
return long_type.get_type()
+def get_ulong_type():
+ global ulong_type
+ return ulong_type.get_type()
+
+def get_size_t_type():
+ global size_t_type
+ return size_t_type.get_type()
+
def offset_of(typeobj, field):
element = gdb.Value(0).cast(typeobj)
return int(str(element[field].address).split()[0], 16)
--
2.18.0
next prev parent reply other threads:[~2023-07-25 9:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 9:34 [PATCH 0/8] Add GDB memory helper commands Kuan-Ying Lee
2023-07-25 9:34 ` [PATCH 1/8] scripts/gdb/symbols: add specific ko module load command Kuan-Ying Lee
2023-07-25 9:34 ` [PATCH 2/8] scripts/gdb/modules: add get module text support Kuan-Ying Lee
2023-07-25 9:34 ` Kuan-Ying Lee [this message]
2023-07-25 9:34 ` [PATCH 4/8] scripts/gdb/aarch64: add aarch64 page operation helper commands and configs Kuan-Ying Lee
2023-07-25 9:34 ` [PATCH 5/8] scripts/gdb/stackdepot: Add stackdepot support Kuan-Ying Lee
2023-07-25 9:34 ` [PATCH 6/8] scripts/gdb/page_owner: add page owner support Kuan-Ying Lee
2023-07-25 9:34 ` [PATCH 7/8] scripts/gdb/slab: Add slab support Kuan-Ying Lee
2023-07-25 9:34 ` [PATCH 8/8] scripts/gdb/vmalloc: add vmallocinfo support Kuan-Ying Lee
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=20230725093458.30064-4-Kuan-Ying.Lee@mediatek.com \
--to=kuan-ying.lee@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=linux-modules@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=qun-wei.lin@mediatek.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