From mboxrd@z Thu Jan  1 00:00:00 1970
From: guijianfeng@cn.fujitsu.com (Gui Jianfeng)
Date: Tue, 10 Mar 2009 09:32:31 +0800
Subject: [ltt-dev] format in marker_entry problem
In-Reply-To: <20090309152246.GB10939@Krystal>
References: <49B4D705.4010208@cn.fujitsu.com> <20090309152246.GB10939@Krystal>
Message-ID: <49B5C32F.4010305@cn.fujitsu.com>



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