Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jeff Mahoney <jeffm@suse.com>
To: Kieran Bingham <kieran.bingham@linaro.org>, gdb-patches@sourceware.org
Cc: arnez@linux.vnet.ibm.com, peter.griffin@linaro.org,
	lee.jones@linaro.org, yao.qi@linaro.org,
	russell.wayman@linaro.org, kernel@stlinux.com
Subject: Re: [RFC PATCH 0/4] GDB Linux Kernel Thread Awareness
Date: Thu, 25 Feb 2016 20:04:00 -0000	[thread overview]
Message-ID: <56CF5E2A.9030905@suse.com> (raw)
In-Reply-To: <1456427706-30077-1-git-send-email-kieran.bingham@linaro.org>


[-- Attachment #1.1: Type: text/plain, Size: 1918 bytes --]

On 2/25/16 2:15 PM, Kieran Bingham wrote:
> I've wanted to get some actual code out for a while and as such I have
> tried to strip down the implementation of LKD to the bare essentials for
> implementing thread awareness. I hope to get some feedback on the best ways of
> upstreaming this functionality.
> 
> This functionality implements the 'possible improvements' Related to Execution
> Contexts as mentioned in Andreas' slides on slide 18 [1] and allows a user
> to perform 'info threads' and see the currently running and sleeping tasks.
> Switching to a specific task, then functions as expected with 'thread NN', and
> 'bt' to produce a back trace of that thread.
> 
> Indeed this patch set hopes to satisfy Andreas' request in [2] to submit a
> small patchset of the initial features. In this case, the thread awareness.
> 
> Now that I have separated out the LKD code from the ST's internal STMC code,
> it could also be possible to publish the larger project if it is of relevance,
> though that will be heavier reading than this reduced patch.
> 
> This implementation is in C and heavily derived from the implementation
> created by ST, as the aim of the upstreaming project is to reuse as much
> of the ST implementation as is reasonable.
> 
> The python-ic version of this that I've been working on (gdb.Target) hits a
> few problems, in guarding against infinite recursion as many of the python
> API's end up calling back into the target layer, and exceptions in that layer
> tend to make GDB crash in very un-user-friendly ways.

FWIW, I've continued to use your Python implementation and have extended
it to meet our needs.  I haven't encountered the recursion you describe,
but it may be that I haven't pushed it hard enough yet.  I think you're
probably more focused on active targets while we're mostly working on dumps.

-Jeff

-- 
Jeff Mahoney
SUSE Labs


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 881 bytes --]

  parent reply	other threads:[~2016-02-25 20:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-25 19:15 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   ` [PATCH 3/4] " Yao Qi
2016-03-01 17:37     ` 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 ` Jeff Mahoney [this message]
2016-02-29  9:42   ` [RFC PATCH 0/4] GDB Linux Kernel Thread Awareness 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=56CF5E2A.9030905@suse.com \
    --to=jeffm@suse.com \
    --cc=arnez@linux.vnet.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=kernel@stlinux.com \
    --cc=kieran.bingham@linaro.org \
    --cc=lee.jones@linaro.org \
    --cc=peter.griffin@linaro.org \
    --cc=russell.wayman@linaro.org \
    --cc=yao.qi@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