From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: "Metzger, Markus T" <markus.t.metzger@intel.com>
Cc: Pedro Alves <palves@redhat.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
"markus.t.metzger@gmail.com" <markus.t.metzger@gmail.com>
Subject: Re: [rfc] remote, btrace: add branch tracing protocol to Qbtrace packet
Date: Thu, 28 Feb 2013 11:31:00 -0000 [thread overview]
Message-ID: <20130228100236.GA10937@host2.jankratochvil.net> (raw)
In-Reply-To: <A78C989F6D9628469189715575E55B2307B86A67@IRSMSX102.ger.corp.intel.com>
On Thu, 28 Feb 2013 09:45:23 +0100, Metzger, Markus T wrote:
> Btw, I think target sub-commands are created dynamically when you call add_target.
Yes; but add_target is called unconditionally during GDB startup so from the
user point of view the commands are not created dynamically.
> > If "lbr" exists it should be enabled by default without asking the user.
>
> We could do that until the user requests BTS tracing or full tracing. This would
> mean that there would be a record target pushed implicitly. With the current
> logic, this would prevent displaced stepping and would require an explicit
> record stop before another record target can be pushed.
>
> I think we should discuss the details once we start sending patches to enable
> LBR tracing.
Yes; I understand it may not be trivial but LBR by default would be great.
> > No preference for the qSupported details, I am OK with your proposal myself,
> > "qXfer" gdbserver->gdb feature is designed that way already.
>
> Pedro objected and rather wanted a comma-separated list, i.e.
>
> ....;Qbtrace=bts,lbr;...
>
> I'm fine either way. For the way I proposed and what seems to be your preference,
> as well, I already found code in GDB to handle it. For Pedro's preferred way, I have
> not found anything that I could reuse.
>
> I would like to get the minimal changes in with the btrace series so we don't need
> to rework the protocol later on and are forced to maintain backwards compatibility.
> I do not intend to implement full support for different branch trace recording
> methods right now, since we currently only have one. We will add that support
> when there's a need.
>
> Pedro did not respond to my reply. I don't know how to proceed, here.
OK; hopefully Pedro will. For example qXfer:* sets a precedent for it IMO
although delegating all gdbserver decisions to Pedro:
PacketSize=3fff;QPassSignals+;qXfer:libraries-svr4:read+;qXfer:auxv:read+;qXfer:spu:read+;qXfer:spu:write+;qXfer:siginfo:read+;qXfer:siginfo:write+;qXfer:features:read+;QStartNoAckMode+;qXfer:osdata:read+;multiprocess+;QNonStop+;QDisableRandomization+;qXfer:threads:read+;ConditionalTracepoints+;TraceStateVariables+;TracepointSource+;DisconnectedTracing+;FastTracepoints+;StaticTracepoints+;InstallInTrace+;qXfer:statictrace:read+;qXfer:traceframe-info:read+;EnableDisableTracepoints+;tracenz+
Thanks,
Jan
prev parent reply other threads:[~2013-02-28 10:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 15:23 markus.t.metzger
2013-02-22 15:51 ` Eli Zaretskii
2013-02-25 8:51 ` Metzger, Markus T
2013-02-25 9:08 ` Jan Kratochvil
2013-02-25 9:13 ` FW: " Metzger, Markus T
2013-02-25 20:33 ` Pedro Alves
2013-02-26 9:24 ` Metzger, Markus T
2013-02-27 16:48 ` Jan Kratochvil
2013-02-28 9:19 ` Metzger, Markus T
2013-02-28 11:31 ` Jan Kratochvil [this message]
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=20130228100236.GA10937@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@gmail.com \
--cc=markus.t.metzger@intel.com \
--cc=palves@redhat.com \
/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