From: dgoulet@ev0ke.net (David Goulet)
Subject: [lttng-dev] [PATCH lttng-modules] Fix: missing event's prefix in btrfs probe
Date: Fri, 25 Jan 2013 14:49:31 -0500 [thread overview]
Message-ID: <1359143371-1953-1-git-send-email-dgoulet@ev0ke.net> (raw)
From: David Goulet <dgoulet@efficios.com>
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
next reply other threads:[~2013-01-25 19:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 19:49 David Goulet [this message]
2013-01-25 19:51 ` David Goulet
2013-01-25 20:01 ` Mathieu Desnoyers
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=1359143371-1953-1-git-send-email-dgoulet@ev0ke.net \
--to=dgoulet@ev0ke.net \
/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