public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: fche@redhat.com (Frank Ch. Eigler)
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: systemtap@sources.redhat.com
Subject: Re: pfaults.stp fix (for 2.6.13 and beyond)
Date: Wed, 05 Oct 2005 18:18:00 -0000	[thread overview]
Message-ID: <y0mpsqjzv82.fsf@toenail.toronto.redhat.com> (raw)
In-Reply-To: <1128533722.4754.65.camel@dyn9047017102.beaverton.ibm.com>


Badari Pulavarty <pbadari@us.ibm.com> writes:

> Yes. I noticed that too. Is there a sane of handling these between
> two kernel versions ? (like function name changes, #define changes,
> disappearing functions).

There isn't an easy way for end-user scripts.  Scripts installed under
tapset/ can use the kernel-version-sensitive search paths.  I
envisioned hiding such version drift in these tapset variants exactly
so that end-user scripts would not need to be aware.  But perhaps this
is not sufficient.

> I tried doing,
> #if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,13)
> probe kernel.function("handle_mm_fault") {
> #else
> probe kernel.function("__handle_mm_fault") {
> #endif
> But doesn't work.

That is because stp sources are not processed through cpp, and even if
they were, it'd have to be told to locate kernel headers that define
such macros, and yet avoid pulling in all the C code.

Several people have suggested a version-sensitive ifdef construct for
the scripting language, and I'm finally coming around on that.  I'll
open a bugzilla entry to track its implementation.

- FChE

      reply	other threads:[~2005-10-05 18:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-05 15:21 Badari Pulavarty
2005-10-05 16:14 ` William Cohen
2005-10-05 17:36   ` Badari Pulavarty
2005-10-05 18:18     ` Frank Ch. Eigler [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=y0mpsqjzv82.fsf@toenail.toronto.redhat.com \
    --to=fche@redhat.com \
    --cc=pbadari@us.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).