linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kieran Bingham <kieran.bingham@linaro.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: linux-kernel@vger.kernel.org, maxime.coquelin@st.com,
	peter.griffin@linaro.org, lee.jones@linaro.org
Subject: Re: [PATCH 3/5] scripts/gdb: Add io resource readers
Date: Sun, 24 Jan 2016 00:17:06 +0000	[thread overview]
Message-ID: <56A41802.8070908@linaro.org> (raw)
In-Reply-To: <56A39841.4040901@siemens.com>



On 23/01/16 15:12, Jan Kiszka wrote:
> On 2016-01-20 12:15, Kieran Bingham wrote:
>> Provide iomem_resource and ioports_resource printers and command hooks
>>
>> Signed-off-by: Kieran Bingham <kieran.bingham@linaro.org>
>>
>> ---
>>
>> These two readers are a useful extract of kernel information.
>> This shows the power of having these commands in gdb/scripts as you can
>> halt a kernel as it's booting and read these as the structures grow.
>>
>> It should be useful in the event that a kernel is not booting, you
>> can identify what memory resources have been registered
>>
> 
> Ack. Maybe provide this reasoning in the commit log? I explains why we
> want this which is too often lacking in the persistent logs...
> 

Perfect,
I'll update the commit for v2.

--
Kieran


>>
>>
>>  scripts/gdb/linux/proc.py | 57 +++++++++++++++++++++++++++++++++++++++++++++++
>>  1 file changed, 57 insertions(+)
>>
>> diff --git a/scripts/gdb/linux/proc.py b/scripts/gdb/linux/proc.py
>> index 6e6709c1830c..d855b2fd9a06 100644
>> --- a/scripts/gdb/linux/proc.py
>> +++ b/scripts/gdb/linux/proc.py
>> @@ -39,3 +39,60 @@ class LxVersion(gdb.Command):
>>          gdb.write(gdb.parse_and_eval("linux_banner").string())
>>  
>>  LxVersion()
>> +
>> +
>> +# Resource Structure Printers
>> +#  /proc/iomem
>> +#  /proc/ioports
>> +
>> +def get_resources(resource, depth):
>> +    while resource:
>> +        yield resource, depth
>> +
>> +        child = resource['child']
>> +        if child:
>> +            for res, deep in get_resources(child, depth + 1):
>> +                yield res, deep
>> +
>> +        resource = resource['sibling']
>> +
>> +
>> +def show_lx_resources(resource_str):
>> +        resource = gdb.parse_and_eval(resource_str)
>> +        width = 4 if resource['end'] < 0x10000 else 8
>> +        # Iterate straight to the first child
>> +        for res, depth in get_resources(resource['child'], 0):
>> +            start = int(res['start'])
>> +            end = int(res['end'])
>> +            gdb.write(" " * depth * 2 +
>> +                      "{0:0{1}x}-".format(start, width) +
>> +                      "{0:0{1}x} : ".format(end, width) +
>> +                      res['name'].string() + "\n")
>> +
>> +
>> +class LxIOMem(gdb.Command):
>> +    """Identify the IO memory resource locations defined by the kernel
>> +
>> +Equivalent to cat /proc/iomem on a running target"""
>> +
>> +    def __init__(self):
>> +        super(LxIOMem, self).__init__("lx-iomem", gdb.COMMAND_DATA)
>> +
>> +    def invoke(self, arg, from_tty):
>> +        return show_lx_resources("iomem_resource")
>> +
>> +LxIOMem()
>> +
>> +
>> +class LxIOPorts(gdb.Command):
>> +    """Identify the IO port resource locations defined by the kernel
>> +
>> +Equivalent to cat /proc/ioports on a running target"""
>> +
>> +    def __init__(self):
>> +        super(LxIOPorts, self).__init__("lx-ioports", gdb.COMMAND_DATA)
>> +
>> +    def invoke(self, arg, from_tty):
>> +        return show_lx_resources("ioport_resource")
>> +
>> +LxIOPorts()
>>
> 
> Looks good to me.
> 
> Jan
> 

  reply	other threads:[~2016-01-24  0:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-20 11:15 [RFC PATCH 0/5] scripts/gdb: Linux awareness debug commands Kieran Bingham
2016-01-20 11:15 ` [PATCH 1/5] scripts/gdb: Provide linux constants Kieran Bingham
2016-01-23 15:05   ` Jan Kiszka
2016-01-24  0:11     ` Kieran Bingham
2016-01-20 11:15 ` [PATCH 2/5] scripts/gdb: Provide a kernel list item generator Kieran Bingham
2016-01-23 15:08   ` Jan Kiszka
2016-01-24  0:15     ` Kieran Bingham
2016-01-20 11:15 ` [PATCH 3/5] scripts/gdb: Add io resource readers Kieran Bingham
2016-01-23 15:12   ` Jan Kiszka
2016-01-24  0:17     ` Kieran Bingham [this message]
2016-01-20 11:15 ` [PATCH 4/5] scripts/gdb: Add mount point list command Kieran Bingham
2016-01-20 11:42   ` Jan Kiszka
2016-01-20 11:51     ` Kieran Bingham
2016-01-20 12:08       ` Jan Kiszka
2016-01-23 12:34   ` Jan Kiszka
2016-01-23 15:27   ` Jan Kiszka
2016-01-24  0:24     ` Kieran Bingham
2016-01-20 11:15 ` [PATCH 5/5] scripts/gdb: Add meminfo command Kieran Bingham
2016-01-23 15:21   ` Jan Kiszka
2016-01-24  0:30     ` Kieran Bingham

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=56A41802.8070908@linaro.org \
    --to=kieran.bingham@linaro.org \
    --cc=jan.kiszka@siemens.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxime.coquelin@st.com \
    --cc=peter.griffin@linaro.org \
    /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;
as well as URLs for NNTP newsgroup(s).