From: Richard J Moore <richardj_moore@uk.ibm.com>
To: systemtap@sources.redhat.com
Subject: Re: thoughts about exception-handling requirements for kprobes
Date: Mon, 20 Mar 2006 08:47:00 -0000 [thread overview]
Message-ID: <OF7089112C.EAE9E722-ON80257137.002FB37F-80257137.002FF94A@uk.ibm.com> (raw)
In-Reply-To: <20060319172454.GA17181@in.ibm.com>
systemtap-owner@sourceware.org wrote on 19/03/2006 17:24:54:
> On Fri, Mar 17, 2006 at 01:50:57PM -0800, Keshavamurthy Anil S wrote:
> > On Thu, Mar 09, 2006 at 07:57:18AM -0800, Richard J Moore wrote:
> > >
> > > I've been thinking about the need for exception-handling and how
the
> > > current implementation has become a little muddled.
> >
> > Here is my thinking on this kprobe fault handling...
> > Ideally we want the ability to recover from all
> > the page faults happening from either pre-handler
> > or happening from post-handler transparently in the
> > same way as the normal kernel would recover from
> > do_page_fault() function. In order for this to happen,
> > I think we should not be calling pre-handler/post-handler
> > by disabling preempt which is a major design change.
> > Also in the current code if fixup_exception() fails to
> > fixup the exception then falling back on the normal
> > do_page_fault() is a bad thing with preempt disabled.
> >
> > I was thinking on this issue for the past several days
> > and I believe that currently we are disabling preempt
> > before calling pre/post handler, because we don;t
> > want the process to get migrated to different CPU
> > and we don't want another process to be scheduled
> > while we are servicing kprobe as the newly scheduled
> > process might trigger another probe and we don;t
> > have space to save the kprobe control block(kprobe_ctlbk)
> > info, because we save kprobe_ctlbk in the per cpu structure.
> >
> > If we move this saving kprobe_ctlbk to task struct then
> > I think we will have the ability to call pre/post-handler
> > without having to disable preempt and their by any faults
> > happening from either pre/post handler can recover transparently
> > in the same way as the normal kernel would recover.
> >
>
> Kprobes user-specified pre/post handler are called within
> the interrupt context and if we allow page faults while within
Clarify what you mean by "allow"
> user-specified pre/post handler, then it might sleep.
Clarify what you mean by "it"
Richard
.
.
> --
> Prasanna S Panchamukhi
> Linux Technology Center
> India Software Labs, IBM Bangalore
> Email: prasanna@in.ibm.com
> Ph: 91-80-51776329
next prev parent reply other threads:[~2006-03-20 8:47 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 [this message]
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
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=OF7089112C.EAE9E722-ON80257137.002FB37F-80257137.002FF94A@uk.ibm.com \
--to=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).