From: Wenji Huang <wenji.huang@oracle.com>
To: Rajasekhar Duddu <rajduddu@linux.vnet.ibm.com>
Cc: systemtap@sources.redhat.com
Subject: Re: [PATCH V5] Tracepoint Tapset for Memory Subsystem
Date: Mon, 07 Dec 2009 02:52:00 -0000 [thread overview]
Message-ID: <4B1C6D57.7090409@oracle.com> (raw)
In-Reply-To: <20091204120819.GA14359@rajduddu>
Hi,
Rajasekhar Duddu wrote:
> +/* The Formal Parameters will be displayed if available, otherwise \
> + "0" or "unknown" will be displayed */
> +
> +probe __vm.kmalloc.tp = kernel.trace("kmalloc") {
> + name = "kmalloc"
> + call_site = $call_site
> + caller_function = symname(call_site)
> + bytes_req = $bytes_req
> + bytes_alloc = $bytes_alloc
> + gfp_flags = $gfp_flags
> + gfp_flag_name = __gfp_flag_str($gfp_flags)
> + ptr = $ptr
> +}
> +
> +/* It is unsafe to invoke __builtin_return_address() \
> +presently(to get call_site for kporbe based probes) \
> +and that it can be improved later when fix for bugs bz#6961 and bz#6580 is available. */
> +
> +probe __vm.kmalloc.kp = kernel.function("kmalloc").return {
> + name = "kmalloc"
> + call_site = 0
> + caller_function = "unknown"
> + bytes_req = $size
> + bytes_alloc = "unknown"
why let bytes_alloc be "unknown", not 0 ?
The type is not consistent with the above one.
Same issue exists in the following part.
Regards,
Wenji
next prev parent reply other threads:[~2009-12-07 2:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 9:31 [PATCH V4] " Rajasekhar Duddu
2009-11-30 16:26 ` Frank Ch. Eigler
2009-12-04 12:09 ` [PATCH V5] " Rajasekhar Duddu
2009-12-07 2:52 ` Wenji Huang [this message]
2009-12-09 6:57 ` Rajasekhar Duddu
2009-12-11 18:36 ` [PATCH V6] " Rajasekhar Duddu
2009-12-21 11:46 ` Prerna Saxena
2009-12-21 21:49 ` Mark Wielaard
2009-12-22 17:02 ` Prerna Saxena
2009-12-29 21:36 ` Mark Wielaard
[not found] <449125467.1554931259945048608.JavaMail.root@zmail02.collab.prod.int.phx2.redhat.com>
2009-12-04 17:11 ` [PATCH V5] " David Smith
2009-12-09 6:59 ` Rajasekhar Duddu
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=4B1C6D57.7090409@oracle.com \
--to=wenji.huang@oracle.com \
--cc=rajduddu@linux.vnet.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).