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 1/4] gdb/observer: Provide target_thread_changed observer
Date: Tue, 01 Mar 2016 16:41:00 -0000 [thread overview]
Message-ID: <86mvqi9mmv.fsf@gmail.com> (raw)
In-Reply-To: <1456427706-30077-2-git-send-email-kieran.bingham@linaro.org> (Kieran Bingham's message of "Thu, 25 Feb 2016 19:15:03 +0000")
Kieran Bingham <kieran.bingham@linaro.org> writes:
> LKD utilises an extra observer to obtain notifications whenever
> the target_thread is changed.
>
> This keeps it's internal state aware of any changes that occur
> in an event driven manner
Sorry, I don't understand why do we need this observer. What problem
are you trying to fix?
--
Yao (齐尧)
next prev parent reply other threads:[~2016-03-01 16:41 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 [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 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 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=86mvqi9mmv.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