From: PAUL GILLIAM <pgilliam@us.ibm.com>
To: Paul Koning <pkoning@equallogic.com>
Cc: drow@false.org, mark.kettenis@xs4all.nl, gdb@sources.redhat.com,
drow@false.org
Subject: Re: Instrcutions that must not be stepped.
Date: Tue, 20 Jun 2006 23:34:00 -0000 [thread overview]
Message-ID: <1150842231.7608.8.camel@dufur.beaverton.ibm.com> (raw)
In-Reply-To: <17560.22490.629655.738203@gargle.gargle.HOWL>
On Tue, 2006-06-20 at 16:17 -0400, Paul Koning wrote:
> >>>>> "PAUL" == PAUL GILLIAM <pgilliam@us.ibm.com> writes:
>
> >> By the way, if stepping these atomic sequences proves to be a
> >> performance problem, you might want to consider implementing
> >> stepping them in the (Linux) kernel.
>
> PAUL> This would be cool. It would be nice to be able to tell if the
> PAUL> kernel has support for this and let it handle atomic sequences
> PAUL> if it does. Let GDB handle it if the kernel doesn't.
>
> Similarly, in remote debugging, there should be a way to have the stub
> handle it. That means you may need some extensions to the stub
> protocol to encode some new information...
Perhaps something in "qSupported" stuff Danial Jacobowitz is working on?
-=# Paul #=-
next prev parent reply other threads:[~2006-06-20 23:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-08 2:27 PAUL GILLIAM
2006-06-08 3:50 ` Daniel Jacobowitz
2006-06-16 4:36 ` PAUL GILLIAM
2006-06-17 12:26 ` PAUL GILLIAM
2006-06-18 4:57 ` Mark Kettenis
2006-06-20 20:13 ` PAUL GILLIAM
2006-06-20 22:53 ` Paul Koning
2006-06-20 23:34 ` PAUL GILLIAM [this message]
2006-06-21 1:17 ` Daniel Jacobowitz
2006-06-09 14:12 John Yates
2006-06-09 14:28 ` Daniel Jacobowitz
2006-06-10 0:33 ` PAUL GILLIAM
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=1150842231.7608.8.camel@dufur.beaverton.ibm.com \
--to=pgilliam@us.ibm.com \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=mark.kettenis@xs4all.nl \
--cc=pkoning@equallogic.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