Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Metzger, Markus T" <markus.t.metzger@intel.com>
To: Pedro Alves <palves@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	"markus.t.metzger@gmail.com" <markus.t.metzger@gmail.com>,
	Jan Kratochvil	<jan.kratochvil@redhat.com>
Subject: FW: [rfc] remote, btrace: add branch tracing protocol to Qbtrace packet
Date: Fri, 01 Mar 2013 15:32:00 -0000	[thread overview]
Message-ID: <A78C989F6D9628469189715575E55B2307B8759C@IRSMSX102.ger.corp.intel.com> (raw)

Hi Pedro,

I would appreciate your feedback to the below discussion.

> -----Original Message-----
> From: gdb-patches-owner@sourceware.org [mailto:gdb-patches-owner@sourceware.org] On Behalf Of Jan Kratochvil
> Sent: Thursday, February 28, 2013 11:03 AM
[...]
> > > 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+;QStart
> NoAckMode+;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,
Markus.
Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen, Deutschland
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas Lusk
Registergericht: Muenchen HRB 47456
Ust.-IdNr./VAT Registration No.: DE129385895
Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052


             reply	other threads:[~2013-03-01 15:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-01 15:32 Metzger, Markus T [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-02-22 15:23 markus.t.metzger
2013-02-25  9:13 ` FW: " Metzger, Markus T

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=A78C989F6D9628469189715575E55B2307B8759C@IRSMSX102.ger.corp.intel.com \
    --to=markus.t.metzger@intel.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=markus.t.metzger@gmail.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