[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <AM0PR04MB64346AE2641AACD732C2EF9EEE230@AM0PR04MB6434.eurprd04.prod.outlook.com>
Date: Tue, 23 Apr 2019 09:20:47 +0000
From: Leonard Crestez <leonard.crestez@....com>
To: Stephen Boyd <sboyd@...nel.org>,
Jan Kiszka <jan.kiszka@...mens.com>,
Kieran Bingham <kbingham@...nel.org>
CC: Andrew Morton <akpm@...ux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/3] scripts/gdb: Add hlist utilities
On 4/22/2019 11:41 PM, Stephen Boyd wrote:
> Quoting Leonard Crestez (2019-04-22 01:26:56)
>> This allows easily examining kernel hlists in python.
>>
>> Signed-off-by: Leonard Crestez <leonard.crestez@....com>
>
>> +def hlist_for_each_entry(head, gdbtype, member):
>> + for node in hlist_for_each(head):
>> + if node.type != hlist_node.get_type().pointer():
>> + raise TypeError("Type {} found. Expected struct hlist_head *."
>
> Maybe drop the full-stop? It looks weird to see struct list_head *.
Makes sense, it was copy/pasted from list_for_each_entry. Since this
iterates over items from hlist_for_each the check is only useful as an
assertion anyway so I'll just drop it.
The hlist_for_each/list_for_each raise gdb.GdbError on type mismatch; as
far as I understand the difference is that GdbError won't print a python
backtrace. However these are internal helpers so TypeError makes more sense.
Powered by blists - more mailing lists