From: Li Guanglei <guanglei@cn.ibm.com>
To: "systemtap@sources.redhat.com" <systemtap@sources.redhat.com>
Subject: change the way we found matching tapsets
Date: Thu, 23 Feb 2006 09:06:00 -0000 [thread overview]
Message-ID: <43FD7B0C.4040400@cn.ibm.com> (raw)
Hi,
The syscall table for PowerPC changed from version to version. In
order to let LKET works for different kernel versions, I have to deal
with such changes in my tapsets.
Formerly I usually do that using the conditional preprocessing
offered by stap. But I found it will become hard to read and will
become unmaintainable as more kernel versions are involved. For
example, it's hard to use conditional preprocessing to define the
following scenario:
#if arch is ppc64 then
#if kernel_ver is 2.6.9 then
probe definitions
#elseif kernel_ver is 2.6.15.* then
probe definitions
#endif
#elseif arch is i686 then
...
#endif
So now I am thinking about using different directories for
different kernel versions. I found that the syscall table stays almost
the same for each major kernel version, e.g. the syscall table of all
2.6.15.* are the same. So I want a directory 2.6.15 to handles all
2.6.15.* versions(including 2.6.15.1, 2.6.15.2 etc).
But it seems that stap will found in this order:
Searched 'tapsets//2.6.15.4/ppc64/*.stp', match count 0
Searched 'tapsets//2.6.15.4/*.stp', match count 1
Searched 'tapsets//2.6/ppc64/*.stp', match count 0
Searched 'tapsets//2.6/*.stp', match count 0
It won't look at 2.6.15 directory. So can we change the behavior that
stap search for tapsets, so that I needn't to create the directories
like 2.6.15.1, 2.6.15.2 etc.
next reply other threads:[~2006-02-23 9:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-23 9:06 Li Guanglei [this message]
2006-02-23 14:13 ` 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=43FD7B0C.4040400@cn.ibm.com \
--to=guanglei@cn.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).