From: Daniel Jacobowitz <drow@false.org>
To: Robert Picco <Robert.Picco@hp.com>
Cc: Andrew Cagney <cagney@gnu.org>, gdb-patches@sources.redhat.com
Subject: Re: new gdb remote packet type
Date: Wed, 12 May 2004 20:55:00 -0000 [thread overview]
Message-ID: <20040512205512.GB3728@nevyn.them.org> (raw)
In-Reply-To: <40A27584.7090200@hp.com>
On Wed, May 12, 2004 at 03:05:40PM -0400, Robert Picco wrote:
> On IA64 the g-packet is too large for kernel debugging. How would you
> suggest identifying registers that are in g-packet. Use another
> protocol extension to see whether target wants to exclude registers from
> g-packet? Another way would be to optionally enable the p-packet with a
> "set-command". This p-packet causes very little latency on IA64 because
> most register values retrieved come from RSE (register stack engine)
> backing store memory.
The latency I was worried about was round trip time - if we have to
request a half-dozen out of a hundred registers, then this will
probably take longer than a whole g packet would, because of waiting
for each side to process the conversation. I guess we'll ignore it for
now and investigate smaller regsets later with qPart.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-05-12 20:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-16 0:45 Robert Picco
2004-04-16 18:33 ` Andrew Cagney
2004-04-22 15:45 ` Robert Picco
2004-04-22 16:09 ` Andrew Cagney
2004-04-29 15:31 ` Robert Picco
2004-04-30 17:31 ` Andrew Cagney
2004-05-04 17:56 ` Robert Picco
2004-05-05 19:10 ` Andrew Cagney
2004-05-06 19:41 ` Robert Picco
2004-05-11 17:31 ` Robert Picco
2004-05-12 18:20 ` Andrew Cagney
2004-05-12 18:31 ` Daniel Jacobowitz
2004-05-12 18:59 ` Robert Picco
2004-05-12 20:55 ` Daniel Jacobowitz [this message]
2004-05-12 22:16 ` Robert Picco
[not found] ` <40A279AF.30603@gnu.org>
2004-05-12 20:53 ` Daniel Jacobowitz
2004-08-02 15:51 ` Robert Picco
2004-09-24 20:07 ` Andrew Cagney
2004-09-25 16:33 ` Eli Zaretskii
2004-09-27 19:21 ` Andrew Cagney
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=20040512205512.GB3728@nevyn.them.org \
--to=drow@false.org \
--cc=Robert.Picco@hp.com \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.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