public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "prasanna at in dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug kprobes/2637] skipped probes in FC6
Date: Fri, 05 May 2006 06:56:00 -0000	[thread overview]
Message-ID: <20060505065635.14580.qmail@sourceware.org> (raw)
In-Reply-To: <20060502201312.2637.hunt@redhat.com>


------- Additional Comments From prasanna at in dot ibm dot com  2006-05-05 06:56 -------
The example given by Martin, accesses the data in user address space. Most
likely the data accessed from user address space may not be present in memory.
It is known that such accesses causes page_faults, where in the
fixup_exception() may not succeed most of the times, hence nmissed count goes up
 (even with the current above patch).

Should we remove incrementing the nmissed count even if fixup_exception() fails?
Most of the system calls access user address space to copy the agruments and
they may experience the similar page_faults as above. 

Is it acceptable, if the probe handler fails most of the time, while accessing
arguments from user address space. OR do we need to find some other way to
get the agruments of the syscalls?

Any thoughts?

Thanks
Prasanna

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=2637

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

  parent reply	other threads:[~2006-05-05  6:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-02 20:13 [Bug kprobes/2637] New: " hunt at redhat dot com
2006-05-02 20:18 ` [Bug kprobes/2637] " hunt at redhat dot com
2006-05-02 20:25 ` hunt at redhat dot com
2006-05-03 13:05 ` prasanna at in dot ibm dot com
2006-05-03 13:08 ` fche at redhat dot com
2006-05-04  4:22 ` hunt at redhat dot com
2006-05-05  6:56 ` prasanna at in dot ibm dot com [this message]
2006-05-05 13:49 ` fche at redhat dot com
2006-05-05 16:45   ` Martin Hunt
2006-05-05 16:42 ` hunt at redhat dot com
2006-05-05 16:45 ` hunt at redhat dot com
2006-05-05 21:33 ` anil dot s dot keshavamurthy at intel dot com
2006-05-11 16:30   ` Martin Hunt
2006-05-11 16:30 ` hunt at redhat dot com
2006-05-11 17:01 ` anil dot s dot keshavamurthy at intel dot com
2006-05-15  6:52 ` prasanna at in dot ibm dot com
2006-05-31 21:58 ` [Bug runtime/2637] " jkenisto at us dot ibm dot com

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=20060505065635.14580.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --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).