From: Michael Snyder <msnyder@redhat.com>
To: Jim Blandy <jimb@red-bean.com>
Cc: gdb@sourceware.org
Subject: Re: Packing "R" actions in a QTDP packet
Date: Mon, 21 Nov 2005 20:19:00 -0000 [thread overview]
Message-ID: <43822BC0.6010101@redhat.com> (raw)
In-Reply-To: <8f2776cb0511182148u78181643o940ebd454d0e3901@mail.gmail.com>
Jim Blandy wrote:
> The code in stringify_collection_list will concatenate as many 'M' and
> 'X' actions as it can in a packet, but it leaves 'R' actions in a
> packet by themselves.
Are you sure? That's not my recollection, though admittedly
it's been 5 years or so... In my mental picture, the R bitmask
goes somewhere in the QTDP message, just *before* the memranges.
There is of course only one 'R' <thing> per tracepoint,
because it's a bitmask...
> Is there any technical reason for this? Should
> I simply document the protocol as allowing actions to be packed
> together as much as you like as long as the overall packet size
> doesn't get too big, or should I say that 'R' actions require a packet
> unto themselves?
next prev parent reply other threads:[~2005-11-21 20:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-19 5:48 Jim Blandy
2005-11-21 20:19 ` Michael Snyder [this message]
2005-11-22 4:48 ` Jim Blandy
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=43822BC0.6010101@redhat.com \
--to=msnyder@redhat.com \
--cc=gdb@sourceware.org \
--cc=jimb@red-bean.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