[ltt-dev] format in marker_entry problem

[ltt-dev] format in marker_entry problem

[Gui Jianfeng]

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.

-- 
Regards
Gui Jianfeng

[ltt-dev] format in marker_entry problem

[Mathieu Desnoyers]

* 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
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
> 

-- 
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68

[ltt-dev] format in marker_entry problem

[Gui Jianfeng]

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