From: Keshavamurthy Anil S <anil.s.keshavamurthy@intel.com>
To: Richard J Moore <richardj_moore@uk.ibm.com>
Cc: systemtap@sources.redhat.com
Subject: Re: thoughts about exception-handling requirements for kprobes
Date: Tue, 21 Mar 2006 00:53:00 -0000 [thread overview]
Message-ID: <20060320165352.A16320@unix-os.sc.intel.com> (raw)
In-Reply-To: <OF34DB1785.3C89A314-ON80257138.000263D7-80257138.0002CE0D@uk.ibm.com>; from richardj_moore@uk.ibm.com on Tue, Mar 21, 2006 at 12:30:38AM +0000
On Tue, Mar 21, 2006 at 12:30:38AM +0000, Richard J Moore wrote:
> > What I am saying is that we should look into kprobes to see
> > if we can support calling users pre/post handlers
> > without having to disable preempt.
>
> Anil, I have already explained the difficulty caused by allowing
> pre-emption, namely that the ordering of pre and post single-step events
> is not necessarily preserved.
> I explained how we can overcome this by using a hand-crafted per-thread
> single-step stack. See my append a week or so ago on single-stepping with
> interrupts enabled.
Sure, I will take a look at this and will get back to you.
thanks,
Anil
next prev parent reply other threads:[~2006-03-21 0:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-09 16:00 Richard J Moore
2006-03-10 3:46 ` Frank Ch. Eigler
2006-03-17 21:51 ` Keshavamurthy Anil S
2006-03-19 17:24 ` Prasanna S Panchamukhi
2006-03-20 8:47 ` Richard J Moore
2006-03-20 9:18 ` Prasanna S Panchamukhi
2006-03-20 14:33 ` Frank Ch. Eigler
2006-03-20 9:43 ` Richard J Moore
2006-03-20 18:40 ` Keshavamurthy Anil S
2006-03-21 0:34 ` Richard J Moore
2006-03-21 0:53 ` Keshavamurthy Anil S [this message]
2006-03-21 5:23 ` Ananth N Mavinakayanahalli
2006-03-21 9:41 ` Prasanna S Panchamukhi
2006-03-21 22:46 ` Keshavamurthy Anil S
2006-03-22 2:37 ` Frank Ch. Eigler
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=20060320165352.A16320@unix-os.sc.intel.com \
--to=anil.s.keshavamurthy@intel.com \
--cc=richardj_moore@uk.ibm.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).