Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] [RFC PATCH] Fix missing data pointer for	trace_mark_tp
Date: Fri, 3 Sep 2010 14:45:58 -0400	[thread overview]
Message-ID: <20100903184558.GB3324@Krystal> (raw)
In-Reply-To: <1283534595-23133-1-git-send-email-david.goulet@polymtl.ca>

* David Goulet (david.goulet at polymtl.ca) wrote:
> ---
>  include/ust/marker.h |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/include/ust/marker.h b/include/ust/marker.h
> index d0b06f5..3625da5 100644
> --- a/include/ust/marker.h
> +++ b/include/ust/marker.h
> @@ -191,7 +191,7 @@ struct marker {
>  		struct registers regs;								\
>  		void __check_tp_type(void)				\
>  		{							\
> -			register_trace_##tp_name(tp_cb);		\
> +			register_trace_##tp_name(call_private, tp_cb);		\

Please double-check with the LTTng implementation. This looks incorrect.
LTTng pass (tp_cb, NULL). (but maybe could pass (tp_cb, call_private),
but call_private is not used at the moment).

So please fix the argument order. I think keeping   (tp_cb,
call_private) would be fine.

> /* Is call_private suppose to be the data pointer that
>  * we just added to tracepoints? If so, this is always set to
>  * NULL using trace_mark_tp. Same below.
>  *
>  * As now, the trace_mark_tp macro is broken without this change
>  */
>  		}							\
>  		DEFINE_MARKER_TP(channel, name, tp_name, tp_cb, format);\
>  		__mark_check_format(format, ## args);			\
> @@ -213,7 +213,7 @@ extern void marker_update_probe_range(struct marker *begin,
>  	do {								\
>  		void __check_tp_type(void)				\
>  		{							\
> -			register_trace_##tp_name(tp_cb);		\
> +			register_trace_##tp_name(call_private, tp_cb);		\

Same here.

Thanks

Mathieu

>  		}							\
>  		__mark_check_format(format, ## args);			\
>  	} while (0)
> -- 
> 1.7.2.2
> 
> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
> 

-- 
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com




      reply	other threads:[~2010-09-03 18:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-03 17:23 David Goulet
2010-09-03 18:45 ` 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=20100903184558.GB3324@Krystal \
    --to=compudj@krystal.dyndns.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