From: Stan Sieler <sieler@allegro.com>
To: alan@linuxcare.com.au (Alan Modra)
Cc: jsm@udlkern.fc.hp.com (John Marvin),
parisc-linux@puffin.external.hp.com,
parisc-linux@thepuffingroup.com
Subject: Re: Single-stepping
Date: Sun, 19 Nov 2000 23:24:00 -0800 (PST) [thread overview]
Message-ID: <200011200724.XAA07561@opus.allegro.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0011201703290.15391-100000@front.linuxcare.com.au> from "Alan Modra" at Nov 20, 2000 05:53:18 PM
Re:
> handlers you mention below. Maybe using the recovery counter isn't such a
quite true.
> bad idea after all, especially since the added syscall and task switch
> overhead can be quite small if the kernel only supports single-step by
> one instruction.
why the limit? We've used multi-instruction "single step" (oxymoron :)
for about 15 years on PA-RISC...no problems, efficient, and *very*
useful!
--
Stan Sieler sieler@allegro.com
www.allegro.com/sieler/wanted/index.html www.sieler.com
next prev parent reply other threads:[~2000-11-20 7:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-20 5:43 Single-stepping John Marvin
2000-11-20 6:53 ` Single-stepping Alan Modra
2000-11-20 7:24 ` Stan Sieler [this message]
2000-11-20 9:05 ` Single-stepping Alan Modra
2000-11-20 18:47 ` Single-stepping Stan Sieler
-- strict thread matches above, loose matches on Subject: below --
2000-11-16 12:44 Single-stepping John Marvin
2000-11-16 13:20 ` Single-stepping Richard Hirst
2000-11-16 19:00 ` Single-stepping Frank Rowand
2000-11-16 20:28 ` Single-stepping Richard Hirst
2000-11-16 9:01 Single-stepping John Marvin
2000-11-16 12:00 ` Single-stepping Richard Hirst
2000-11-20 3:03 ` Single-stepping Alan Modra
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=200011200724.XAA07561@opus.allegro.com \
--to=sieler@allegro.com \
--cc=alan@linuxcare.com.au \
--cc=jsm@udlkern.fc.hp.com \
--cc=parisc-linux@puffin.external.hp.com \
--cc=parisc-linux@thepuffingroup.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.