From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [lttng-dev] [PATCH lttng-modules] Fix: missing event's prefix in btrfs probe
Date: Fri, 25 Jan 2013 15:01:59 -0500 [thread overview]
Message-ID: <20130125200159.GA6859@Krystal> (raw)
In-Reply-To: <1359143371-1953-1-git-send-email-dgoulet@ev0ke.net>
* David Goulet (dgoulet at ev0ke.net) wrote:
> From: David Goulet <dgoulet@efficios.com>
Nope, those prefix are missing upstream. I cannot take them until Linux
upstream is fixed. You might want to submit a patch on LKML, ccing those
responsible for:
commit 3f7de037fb3727b20bc27332cdcf2488b702394c
Author: Josef Bacik <josef at redhat.com>
Date: Thu Nov 10 08:29:20 2011 -0500
Btrfs: add allocator tracepoints
I used these tracepoints when figuring out what the cluster stuff was doing, so
add them to mainline in case we need to profile this stuff again. Thanks,
Signed-off-by: Josef Bacik <josef at redhat.com>
And the btrfs maintainer (found in MAINTAINERS).
Thanks,
Mathieu
>
> Signed-off-by: David Goulet <dgoulet at efficios.com>
> ---
> instrumentation/events/lttng-module/btrfs.h | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/instrumentation/events/lttng-module/btrfs.h b/instrumentation/events/lttng-module/btrfs.h
> index c01a6e0..34ae480 100644
> --- a/instrumentation/events/lttng-module/btrfs.h
> +++ b/instrumentation/events/lttng-module/btrfs.h
> @@ -390,7 +390,7 @@ DECLARE_EVENT_CLASS(btrfs__writepage,
> #endif
> )
>
> -DEFINE_EVENT(btrfs__writepage, __extent_writepage,
> +DEFINE_EVENT(btrfs__writepage, btrfs_extent_writepage,
>
> TP_PROTO(struct page *page, struct inode *inode,
> struct writeback_control *wbc),
> @@ -792,7 +792,7 @@ DEFINE_EVENT(btrfs__reserved_extent, btrfs_reserved_extent_free,
> )
>
> #if (LINUX_VERSION_CODE >= KERNEL_VERSION(3,3,0))
> -TRACE_EVENT(find_free_extent,
> +TRACE_EVENT(btrfs_find_free_extent,
>
> TP_PROTO(struct btrfs_root *root, u64 num_bytes, u64 empty_size,
> u64 data),
> @@ -956,7 +956,7 @@ TRACE_EVENT(btrfs_setup_cluster,
> #endif
>
> #if (LINUX_VERSION_CODE >= KERNEL_VERSION(3,4,0))
> -TRACE_EVENT(alloc_extent_state,
> +TRACE_EVENT(btrfs_alloc_extent_state,
>
> TP_PROTO(struct extent_state *state, gfp_t mask, unsigned long IP),
>
> @@ -978,7 +978,7 @@ TRACE_EVENT(alloc_extent_state,
> show_gfp_flags(__entry->mask), (void *)__entry->ip)
> )
>
> -TRACE_EVENT(free_extent_state,
> +TRACE_EVENT(btrfs_free_extent_state,
>
> TP_PROTO(struct extent_state *state, unsigned long IP),
>
> --
> 1.7.10.4
>
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
prev parent reply other threads:[~2013-01-25 20:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 19:49 David Goulet
2013-01-25 19:51 ` David Goulet
2013-01-25 20:01 ` Mathieu Desnoyers [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=20130125200159.GA6859@Krystal \
--to=mathieu.desnoyers@efficios.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