public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Prasanna S Panchamukhi <prasanna@in.ibm.com>
To: Keshavamurthy Anil S <anil.s.keshavamurthy@intel.com>
Cc: systemtap@sources.redhat.com
Subject: Re: [1/5 PATCH] Kprobes fix for broken fault handling for i386
Date: Wed, 08 Mar 2006 05:13:00 -0000	[thread overview]
Message-ID: <20060308051457.GA4844@in.ibm.com> (raw)
In-Reply-To: <440E07FE.2060804@us.ibm.com>

Anil,

You can use the test script mentioned by Hien below.
Also to test the fault handling, you need to just
call copy_from_user(), that will generate a page fault.
In the post/pre handler allocate a buffer and 
copy some data from the user address space.

copy_from_user(&buf, (unsigned long *)0xbff2d020, 10);

where the from address should be a valid user space address.


Thanks
Prasanna

On Tue, Mar 07, 2006 at 02:23:58PM -0800, Hien Nguyen wrote:
> Keshavamurthy Anil S wrote:
> 
> >On Tue, Mar 07, 2006 at 05:38:32AM -0800, Prasanna S Panchamukhi wrote:
> > 
> >
> >>  Hi,
> >>
> >>  Below is the set of patches to fix broken fault handling
> >>  for i386, x86_64, ppc64, ia64 and sparc64 architectures
> >>  against 2.6.16-rc5-mm2.
> >>
> >>  These patches are tested for i386 and x86_64 architectures.
> >>  Could you please test it for ia64 and ppc64.
> >>   
> >>
> >
> >Prasanna,
> >	Can you share your test module code here,
> >so that the same can be used(with minor tweak, if requred)
> >for testing other architecture. Also in you testing, did 
> >you cover fault handling during pre/post/singlestep
> >cases?
> >
> >Thanks,
> >Anil
> >
> > 
> >
> I tested Prasanna's fault handling patch with the current syscalls 
> tapset (latest from CVS) which does lots of user copies. Without the 
> patch the system crashes right away, but with this patch I finally can 
> test the system calls tapset.
> 
> I use Martin's sys.stp script below
> 
> probe syscall.*, syscall.*.return {
>        if (pid() == target()) {
>                if (returnp)
>                        printf("%d\n", returnval())
>                else
>                        printf("%s (%s) = ", name, argstr)
>        }
> }
> 
> Invoke the script as follow
> stap -c bash sys.stp
> to exit the script, just type exit.
> 
> Hien.
> 
> 
> 

-- 
Prasanna S Panchamukhi
Linux Technology Center
India Software Labs, IBM Bangalore
Email: prasanna@in.ibm.com
Ph: 91-80-51776329

      reply	other threads:[~2006-03-08  5:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-07 13:37 Prasanna S Panchamukhi
2006-03-07 13:40 ` [2/5 PATCH] Kprobes fix for broken fault handling for x86_64 Prasanna S Panchamukhi
2006-03-07 13:39   ` [3/5 PATCH] Kprobes fix for broken fault handling for ppc64 Prasanna S Panchamukhi
2006-03-07 13:40     ` [4/5 PATCH] Kprobes fix for broken fault handling for ia64 Prasanna S Panchamukhi
2006-03-07 13:41       ` [5/5 PATCH] Kprobes fix for broken fault handling for sparc64 Prasanna S Panchamukhi
2006-03-08  8:13       ` [4/5 PATCH] Kprobes fix for broken fault handling for ia64 bibo,mao
2006-03-08 11:17         ` Prasanna S Panchamukhi
2006-03-07 21:26 ` [1/5 PATCH] Kprobes fix for broken fault handling for i386 Keshavamurthy Anil S
2006-03-07 22:24   ` Hien Nguyen
2006-03-08  5:13     ` Prasanna S Panchamukhi [this message]

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=20060308051457.GA4844@in.ibm.com \
    --to=prasanna@in.ibm.com \
    --cc=anil.s.keshavamurthy@intel.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).