public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Richard J Moore <richardj_moore@uk.ibm.com>
To: fche@redhat.com (Frank Ch. Eigler)
Cc: systemtap@sources.redhat.com
Subject: Re: Single-stepping with interrupts enabled.
Date: Mon, 27 Feb 2006 14:05:00 -0000	[thread overview]
Message-ID: <OFD1B7132F.675DDBC4-ON80257122.004C8326-80257122.004D447E@uk.ibm.com> (raw)
In-Reply-To: <y0mr75odi4l.fsf@ton.toronto.redhat.com>





You can't do without post-handlers. SystemTap might not use them explicitly
but post-handling of the single-step (in kprobes) is required whether or
not a user handler is registered. For example for correcting the outcome of
an instructions execution (certain adjustments may have to be made - E49,
etc..); for handling exceptions from the single-stepped instruction
correctly; for giving the correct 'logical' view at a higher level of a
trace event following the generation of a recoverable page-fault on
single-step; for correcting IF manipulating instructions where the state of
the interrupt flag is not actually as the probed program logically thinks
it is; for correcting the TRAP Flag for the same reasons as IF.

There must be more.

- -
Richard J Moore
IBM Advanced Linux Response Team - Linux Technology Centre
MOBEX: 264807; Mobile (+44) (0)7739-875237
Office: (+44) (0)1962-817072


                                                                           
             fche@redhat.com                                               
             (Frank Ch.                                                    
             Eigler)                                                    To 
             Sent by:                  Richard J Moore/UK/IBM@IBMGB        
             fche@redhat.com                                            cc 
                                       systemtap@sources.redhat.com        
                                                                       bcc 
             27/02/2006                                                    
             13:51                                                 Subject 
                                       Re: Single-stepping with interrupts 
                                       enabled.                            
                                                                           
                                                                           





richardj_moore wrote:

> [...]  The problem is down to the need to save state over the
> single-step, so that pre- and post-processing either side of the
> single-step can be correctly associated with each other. [...]

How much of this would be simplified if we did away with support for
post_handlers (which we don't use in systemtap)?

- FChE


  reply	other threads:[~2006-02-27 14:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-27 11:29 Richard J Moore
2006-02-27 13:51 ` Frank Ch. Eigler
2006-02-27 14:05   ` Richard J Moore [this message]
2006-02-27 17:13 ` James Dickens
2006-02-27 17:34   ` Richard J Moore
2006-02-27 18:18     ` James Dickens

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=OFD1B7132F.675DDBC4-ON80257122.004C8326-80257122.004D447E@uk.ibm.com \
    --to=richardj_moore@uk.ibm.com \
    --cc=fche@redhat.com \
    --cc=systemtap@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).