From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] (forw) [chris.meyers.fsu@gmail.com: Re: ltt channel thread safe?]
Date: Thu, 9 Sep 2010 12:40:24 -0400 [thread overview]
Message-ID: <20100909164024.GB15254@Krystal> (raw)
In-Reply-To: <4C887A6C.8070100@polymtl.ca>
* Pierre-Marc Fournier (pierre-marc.fournier at polymtl.ca) wrote:
> On 08/27/2010 01:01 PM, Mathieu Desnoyers wrote:
>> * Fu Juntang(David) (juntang.fu at windriver.com) wrote:
>>> Hi,Mathieu:
>>> has the issue any update?
>>>
>>> please see my test case and the trace logs(in the attachment), from
>>> the trace log,we can see we can only see the trace datas from cpu_0:
>>> ust.myevent: 18161.506516049
>>> (/home/Large_Space/Part_B/LogStore/LTTngLog_wrlinux-4.0/UST/UST_Logs/multi-thread/david-desktop-20100811163524864824113/11520_5504068123890634635/ust_0), 0, 0, , , 0, 0x0, MODE_UNKNOWN { firstthread = 2 }
>>> ust.myevent: 18163.506594856
>>> (/home/Large_Space/Part_B/LogStore/LTTngLog_wrlinux-4.0/UST/UST_Logs/multi-thread/david-desktop-20100811163524864824113/11520_5504068123890634635/ust_0), 0, 0, , , 0, 0x0, MODE_UNKNOWN { firstthread = 3 }
>>> ust.myevent: 18165.506667869
>>> (/home/Large_Space/Part_B/LogStore/LTTngLog_wrlinux-4.0/UST/UST_Logs/multi-thread/david-desktop-20100811163524864824113/11520_5504068123890634635/ust_0), 0, 0, , , 0, 0x0, MODE_UNKNOWN { firstthread = 5 }
>>> ust.myevent: 18167.506735881
>>> (/home/Large_Space/Part_B/LogStore/LTTngLog_wrlinux-4.0/UST/UST_Logs/multi-thread/david-desktop-20100811163524864824113/11520_5504068123890634635/ust_0), 0, 0, , , 0, 0x0, MODE_UNKNOWN { firstthread = 7 }
>>> ust.myevent: 18169.506818732
>>> (/home/Large_Space/Part_B/LogStore/LTTngLog_wrlinux-4.0/UST/UST_Logs/multi-thread/david-desktop-20100811163524864824113/11520_5504068123890634635/ust_0), 0, 0, , , 0, 0x0, MODE_UNKNOWN { firstthread = 8 }
>>> ust.myevent: 18171.506903062
>>> (/home/Large_Space/Part_B/LogStore/LTTngLog_wrlinux-4.0/UST/UST_Logs/multi-thread/david-desktop-20100811163524864824113/11520_5504068123890634635/ust_0), 0, 0, , , 0, 0x0, MODE_UNKNOWN { firstthread = 10 }
>>> End trace set
>>>
>>> we missed the trace logs:
>>> trace_mark(ust, myevent, "secondthread %d", number);
>>
>> Oh, you created two events with same channel and same name, but with a
>> different first parameter name. This should be forbidden. UST should
>> take care of checking for these duplicate markers with non-matching
>> parameters.
>>
>> libust marker.c is checking for this, as it should:
>>
>> static int set_marker(struct marker_entry *entry, struct marker *elem,
>> int active)
>> {
>> int ret = 0;
>> WARN_ON(strcmp(entry->name, elem->name) != 0);
>>
>> if (entry->format) {
>> if (strcmp(entry->format, elem->format) != 0) {
>> DBG("Format mismatch for probe %s (%s), marker (%s)",
>> entry->name,
>> entry->format,
>> elem->format);
>> return -EPERM;
>> }
>> } else {
>>
>> Pierre-Marc, why it this only showing the warning if UST_DEBUG is
>> defined ? This should always spit out the warning.
>>
>
> Agreed, it should probably be a WARN or ERR.
Nils/David, do you want to make a patch for this ?
pmf, I guess handing me a commit access might be handy.
Thanks!
Mathieu
>
> pmf
>
--
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2010-09-09 16:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 21:07 Mathieu Desnoyers
2010-08-10 21:07 ` Mathieu Desnoyers
2010-08-10 21:07 ` Mathieu Desnoyers
2010-08-11 15:39 ` Mathieu Desnoyers
2010-08-12 8:03 ` Fu Juntang(David)
2010-08-12 13:40 ` Mathieu Desnoyers
2010-08-13 7:37 ` Fu Juntang(David)
2010-08-13 12:24 ` Mathieu Desnoyers
2010-08-16 2:45 ` Fu Juntang(David)
[not found] ` <1282881078.21590.26.camel@david-desktop>
2010-08-27 17:01 ` Mathieu Desnoyers
2010-09-09 6:10 ` Pierre-Marc Fournier
2010-09-09 16:40 ` Mathieu Desnoyers [this message]
2010-09-09 16:54 ` David Goulet
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=20100909164024.GB15254@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