From: Wenji Huang <wenji.huang@oracle.com>
To: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: systemtap@sourceware.org
Subject: Re: [patch] Alter syscall.brk and syscall.mremap to support IA64
Date: Tue, 18 Sep 2007 16:31:00 -0000 [thread overview]
Message-ID: <46EF6DDE.5090007@oracle.com> (raw)
In-Reply-To: <46EF5BEE.8020902@cn.fujitsu.com>
Lai Jiangshan wrote:
> Hi, all
> In the current tapset, kernel function sys_brk and sys_mremap are
> used to probe syscall.brk and syscall.mremap. But on IA64, the entries
> of syscall brk and mremap are actually ia64_brk and ia64_mremap, but not
> sys_brk and sys_mremap. Though I think ia64's kernel function will be
> finally changed to sys_brk and sys_mremap, it will be a long time so it
> is inconvenient for users to probe these 2 syscalls on IA64. So I added
> the probe points to syscall.brk and syscall.mremap for IA64 as following:
>
> diff -Nur /usr/share/systemtap/tapset/syscalls.stp tapset/syscalls.stp
> --- /usr/share/systemtap/tapset/syscalls.stp 2007-09-18
> 10:11:15.000000000 +0900
> +++ tapset/syscalls.stp 2007-09-18 12:07:19.000000000 +0900
> @@ -178,12 +178,14 @@
>
> # brk ________________________________________________________
> # unsigned long sys_brk(unsigned long brk)
> -probe syscall.brk = kernel.function("sys_brk") {
> +probe syscall.brk = kernel.function("sys_brk"),
> + kernel.function("ia64_brk") ? {
> name = "brk"
> brk = $brk
> argstr = sprintf("%p", brk)
> }
sys_brk is generic, use %( arch == "ia64" %? to make it optional. Of
course, it is better to put architecture depended probe into the
corresponding directory.
Regards,
wenji
next prev parent reply other threads:[~2007-09-18 6:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 14:20 Lai Jiangshan
2007-09-18 16:31 ` Wenji Huang [this message]
2007-09-19 9:30 ` Lai Jiangshan
2007-09-25 15:17 ` Lai Jiangshan
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=46EF6DDE.5090007@oracle.com \
--to=wenji.huang@oracle.com \
--cc=laijs@cn.fujitsu.com \
--cc=systemtap@sourceware.org \
/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).