Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: guijianfeng@cn.fujitsu.com (Gui Jianfeng)
Subject: [ltt-dev] format in marker_entry problem
Date: Tue, 10 Mar 2009 09:32:31 +0800	[thread overview]
Message-ID: <49B5C32F.4010305@cn.fujitsu.com> (raw)
In-Reply-To: <20090309152246.GB10939@Krystal>



Mathieu Desnoyers wrote:
> * Gui Jianfeng (guijianfeng at cn.fujitsu.com) wrote:
>> Hi Mathieu,
>>
>> I'd like to know what's the actual value of the *format* member in 
>> struct marker_entry. Why i have to pass a format parameter when calling
>> marker_probe_register(). Consider the following scenario:
>> There are two are markers A and B with same channel and name, but 
>> different format like this: 
>> A("mychan", "mymarker", "format 1")
>> B("mychan", "mymarker", "format 2")
>>
>> Call marker_probe_register("mychan", "mymarker", "format 1",....)
>> here A is activated.
>> IIUC, B can't be activated until A is deactivated.
>> I guess this is what we don't want.
>>
> 
> marker.c will detect a format mismatch and show an error. It will not

  So, why this kind of detection is needed? Isn't the format in marker
  section enough?

> care about the second marker. Therefore, you should consider a 1 -> 1
> mapping between channel/marker names -> format string.
> 
> Mathieu
> 
>> -- 
>> Regards
>> Gui Jianfeng
>>
>>
>> _______________________________________________
>> ltt-dev mailing list
>> ltt-dev at lists.casi.polymtl.ca
>> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
>>
> 

-- 
Regards
Gui Jianfeng




      reply	other threads:[~2009-03-10  1:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-09  8:44 Gui Jianfeng
2009-03-09 15:22 ` Mathieu Desnoyers
2009-03-10  1:32   ` Gui Jianfeng [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=49B5C32F.4010305@cn.fujitsu.com \
    --to=guijianfeng@cn.fujitsu.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