From: Martin Hunt <hunt@redhat.com>
To: "Gui,Jian" <guij@cn.ibm.com>
Cc: "systemtap@sources.redhat.com" <systemtap@sources.redhat.com>
Subject: Re: obsolete syscall probe points in tapset for ppc64?
Date: Thu, 16 Feb 2006 16:04:00 -0000 [thread overview]
Message-ID: <1140105909.4471.3.camel@monkey2> (raw)
In-Reply-To: <011f01c632c5$b5bf5840$9d85b509@IBM528414E28E4>
On Thu, 2006-02-16 at 14:53 +0800, Gui,Jian wrote:
>
> The errors come from the probe points for sys_fstat, sys_mmap2
> defined in tapset/syscalls.stp and the probe points for sys_stat,
> sys_setgroups16 in tapset/syscalls2.stp.
>
> I grep /proc/kallsyms and found these four syscalls are not exported.
>
> I check the kernel source and find they are replaced by newer versions
> or removed (?) in ppc64 kernel:
> sys_fstat --> sys_newfstat
> sys_mmap2 --> sys32_mmap2
> sys_setgroups16 --> ?
> sys_stat --> sys_newstat
Thanks for reporting these. I have not had a chance to test on ppc yet.
I will make the proper changes.
Martin
prev parent reply other threads:[~2006-02-16 16:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-16 6:54 Gui,Jian
2006-02-16 16:04 ` Martin Hunt [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=1140105909.4471.3.camel@monkey2 \
--to=hunt@redhat.com \
--cc=guij@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).