From: Kieran Bingham <kieran.bingham@linaro.org>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: gdb-patches@sourceware.org, arnez@linux.vnet.ibm.com,
jeffm@suse.com, peter.griffin@linaro.org, lee.jones@linaro.org,
russell.wayman@linaro.org, kernel@stlinux.com
Subject: Re: [PATCH 3/4] gdb/lkd: Add Linux Kernel Awareness target
Date: Tue, 01 Mar 2016 17:37:00 -0000 [thread overview]
Message-ID: <56D5D335.7040700@linaro.org> (raw)
In-Reply-To: <86io169kho.fsf@gmail.com>
On 01/03/16 17:27, Yao Qi wrote:
> Kieran Bingham <kieran.bingham@linaro.org> writes:
>
>> Provide infrastructure and thread awareness for the Linux Kernel
>> This functionality is heavily derived from the functionality created
>> by ST Microelectronics which provides a greater feature set.
>
> In some file headers, there is such claimer
>
> Copyright 2011-2013 STMicroelectronics.
>
> the copyright should be associated to the FSF. See other GDB source
> file headers.
Yes, of course - Sorry - I'll update these. My aim was to get the code
out to review the overall implementation.
>
> Looks ST Microelectronics has already had signed copyright paper
>
> GDB/INSIGHT STMicroelectronics 2004-12-09
> Assigns past and future changes.
Excellent - I was worried about this :)
>
>>
>> This specific implementation is stripped down to provide thread
>> awareness only. Other functionality that can already be provided by python
>> infrastructure such as information gathering tools specific to linux
>> have been submitted to the linux kernel project separately.
>
> This patch includes too many things... could you split it so that the
> patch only include the very basic and simple kernel awareness feature.
> It may have bugs or may not handle some cases very well, but GDB can
> show the kernel threads. The following patches can fix these bugs and
> do improvements. For example, some commands added by this patch isn't
> necessary, nor the code for logging levels. They can be split to
> separated patches.
Ok, I can go further in the chop.
At this level, I was hoping for a review of the method of implementation
through a target layer.
>>
>> Kernel module support is also already working and available through the
>> python extensions provided by the linux kernel and has been removed from
>> this submission.
>
> I don't know how kernel module support is done through python
> extensions. I thought linux kernel module can be handled as shared
> library under the solib infrastructure. See files solib*.c.
The module list is parsed through a python command, which then searches
for the ko objects, and adds them to GDB as symbol files.
See:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/scripts/gdb/linux/modules.py
and in particular:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/scripts/gdb/linux/symbols.py
Regards
Kieran
next prev parent reply other threads:[~2016-03-01 17:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 19:15 [RFC PATCH 0/4] GDB Linux Kernel Thread Awareness Kieran Bingham
2016-02-25 19:15 ` [PATCH 2/4] gdb/command: Add LKD Command class Kieran Bingham
2016-02-25 19:15 ` [PATCH 3/4] gdb/lkd: Add Linux Kernel Awareness target Kieran Bingham
2016-02-26 11:02 ` [PATCH] squash! " Kieran Bingham
2016-03-01 17:27 ` [PATCH 3/4] " Yao Qi
2016-03-01 17:37 ` Kieran Bingham [this message]
2016-02-25 19:15 ` [PATCH 4/4] lkd: Add an Architecture Layer for ARMv7 targets Kieran Bingham
2016-02-25 19:15 ` [PATCH 1/4] gdb/observer: Provide target_thread_changed observer Kieran Bingham
2016-03-01 16:41 ` Yao Qi
2016-02-25 20:04 ` [RFC PATCH 0/4] GDB Linux Kernel Thread Awareness Jeff Mahoney
2016-02-29 9:42 ` Kieran Bingham
2016-03-01 16:33 ` Yao Qi
2016-03-02 15:38 ` 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=56D5D335.7040700@linaro.org \
--to=kieran.bingham@linaro.org \
--cc=arnez@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=jeffm@suse.com \
--cc=kernel@stlinux.com \
--cc=lee.jones@linaro.org \
--cc=peter.griffin@linaro.org \
--cc=qiyaoltc@gmail.com \
--cc=russell.wayman@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