Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Kieran Bingham <kieran.bingham@linaro.org>
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:27:00 -0000	[thread overview]
Message-ID: <86io169kho.fsf@gmail.com> (raw)
In-Reply-To: <1456427706-30077-4-git-send-email-kieran.bingham@linaro.org>	(Kieran Bingham's message of "Thu, 25 Feb 2016 19:15:05 +0000")

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.

Looks ST Microelectronics has already had signed copyright paper

GDB/INSIGHT	STMicroelectronics	2004-12-09
Assigns past and future changes.

>
> 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.

>
> 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.

-- 
Yao (齐尧)


  parent reply	other threads:[~2016-03-01 17:27 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 1/4] gdb/observer: Provide target_thread_changed observer Kieran Bingham
2016-03-01 16:41   ` Yao Qi
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   ` Yao Qi [this message]
2016-03-01 17:37     ` [PATCH 3/4] " Kieran Bingham
2016-02-25 19:15 ` [PATCH 2/4] gdb/command: Add LKD Command class Kieran Bingham
2016-02-25 19:15 ` [PATCH 4/4] lkd: Add an Architecture Layer for ARMv7 targets Kieran Bingham
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=86io169kho.fsf@gmail.com \
    --to=qiyaoltc@gmail.com \
    --cc=arnez@linux.vnet.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jeffm@suse.com \
    --cc=kernel@stlinux.com \
    --cc=kieran.bingham@linaro.org \
    --cc=lee.jones@linaro.org \
    --cc=peter.griffin@linaro.org \
    --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