<div dir="ltr"><div dir="ltr"><div dir="ltr"><div>Hi Björn.</div><div><br></div><div>I meant the IRQ field in the trace logs. The -x parameter did not bring the records relative to UNLOCK as you said. Looking at ftdump records, I noticed that the UNLOCK_START and UNLOCK_END records are interleaved by SCHED and SCHED2 records (see below). Could this be why these records are not being counted? The protocol I am testing is not suspension-based, but it can call the litmus_reschedule() method at the end of unlock() plugin method. I'll try with the standard tools to get the records of the other processors, as you suggested. Thank you again.</div><div><br></div><div><font face="courier new, monospace">UNLOCK_START seq: 372140 pid: 5086 timestamp: 7003579867914 cpu: 0 type: RT irq: 1 irqc: 01</font></div><div><font face="courier new, monospace">SCHED_START seq: 372141 pid: 5086 timestamp: 7003579871038 cpu: 0 type: UNKNOWN irq: 0 irqc: 00</font></div><div><font face="courier new, monospace">SCHED_END seq: 372142 pid: 5086 timestamp: 7003579875406 cpu: 0 type: RT irq: 0 irqc: 00</font></div><div><font face="courier new, monospace">SCHED2_START seq: 372143 pid: 5086 timestamp: 7003579875842 cpu: 0 type: RT irq: 0 irqc: 00</font></div><div><font face="courier new, monospace">SCHED2_END seq: 372144 pid: 5086 timestamp: 7003579876844 cpu: 0 type: RT irq: 0 irqc: 00</font></div><div><font face="courier new, monospace">UNLOCK_END seq: 372145 pid: 5086 timestamp: 7003579877156 cpu: 0 type: RT irq: 0 irqc: 00</font></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Em qua, 15 de mai de 2019 às 07:00, <<a href="mailto:litmus-dev-request@lists.litmus-rt.org">litmus-dev-request@lists.litmus-rt.org</a>> escreveu:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send litmus-dev mailing list submissions to<br>
<a href="mailto:litmus-dev@lists.litmus-rt.org" target="_blank">litmus-dev@lists.litmus-rt.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://lists.litmus-rt.org/listinfo/litmus-dev" rel="noreferrer" target="_blank">https://lists.litmus-rt.org/listinfo/litmus-dev</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:litmus-dev-request@lists.litmus-rt.org" target="_blank">litmus-dev-request@lists.litmus-rt.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:litmus-dev-owner@lists.litmus-rt.org" target="_blank">litmus-dev-owner@lists.litmus-rt.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of litmus-dev digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: litmus-dev Digest, Vol 81, Issue 3 (Björn Brandenburg)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Wed, 15 May 2019 09:30:12 +0200<br>
From: Björn Brandenburg <<a href="mailto:bbb@mpi-sws.org" target="_blank">bbb@mpi-sws.org</a>><br>
To: <a href="mailto:litmus-dev@lists.litmus-rt.org" target="_blank">litmus-dev@lists.litmus-rt.org</a><br>
Subject: Re: [LITMUS^RT] litmus-dev Digest, Vol 81, Issue 3<br>
Message-ID: <<a href="mailto:78F281B5-EC75-4510-B1C1-C11F0D63A5BE@mpi-sws.org" target="_blank">78F281B5-EC75-4510-B1C1-C11F0D63A5BE@mpi-sws.org</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi Ricardo,<br>
<br>
> On 15. May 2019, at 02:44, Ricardo Teixeira <<a href="mailto:ricardo.btxr@gmail.com" target="_blank">ricardo.btxr@gmail.com</a>> wrote:<br>
> <br>
>> Below are the kernel messages for the overhead and schedule tracers.<br>
<br>
these messages look reasonable; I don’t see anything suggesting that there might be a problem. <br>
<br>
>> When I'm looking for UNLOCK events through ftdump, I noticed that almost all UNLOCK_START records are generated with IRQ enabled for both protocols I'm running.<br>
<br>
What do you mean with “almost all [...] with IRQ enabled”? Do you have different lock entry paths, some with IRQs enabled and some without? <br>
<br>
Or do you mean the IRQ field in the trace records? That’s a snapshot of the core’s IRQ *counter*, which is reset when it is read. It’s perfectly normal for this number to be non-zero for a _START event — on average, you’d expect there to have been some interrupts since the last time that an event was recorded. <br>
<br>
>> Is this why these records are not being counted? Is there any parameter so I can collect these records? <br>
<br>
Yes, -x disables interrupt filtering, but, again, this should not be an issue for _START events. <br>
<br>
<a href="https://github.com/LITMUS-RT/feather-trace-tools/blob/master/src/ft2csv.c#L397" rel="noreferrer" target="_blank">https://github.com/LITMUS-RT/feather-trace-tools/blob/master/src/ft2csv.c#L397</a><br>
<br>
You had mentioned in some email that you use “inherited” scripts that produce a single .ft file — I have no idea what these scripts are, where they come from, or what they do, so I can’t really help you debug them. I would recommend to use the standard tools as described in the tutorial. <br>
<br>
<a href="https://github.com/LITMUS-RT/feather-trace-tools/blob/master/doc/howto-trace-and-process-overheads.md" rel="noreferrer" target="_blank">https://github.com/LITMUS-RT/feather-trace-tools/blob/master/doc/howto-trace-and-process-overheads.md</a><br>
<br>
At the very least, see if the problem persists if you follow that approach. <br>
<br>
Regards,<br>
Björn<br>
<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.litmus-rt.org/pipermail/litmus-dev/attachments/20190515/824b17dc/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.litmus-rt.org/pipermail/litmus-dev/attachments/20190515/824b17dc/attachment-0001.html</a>><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: smime.p7s<br>
Type: application/pkcs7-signature<br>
Size: 2334 bytes<br>
Desc: not available<br>
URL: <<a href="http://lists.litmus-rt.org/pipermail/litmus-dev/attachments/20190515/824b17dc/attachment-0001.bin" rel="noreferrer" target="_blank">http://lists.litmus-rt.org/pipermail/litmus-dev/attachments/20190515/824b17dc/attachment-0001.bin</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
litmus-dev mailing list<br>
<a href="mailto:litmus-dev@lists.litmus-rt.org" target="_blank">litmus-dev@lists.litmus-rt.org</a><br>
<a href="https://lists.litmus-rt.org/listinfo/litmus-dev" rel="noreferrer" target="_blank">https://lists.litmus-rt.org/listinfo/litmus-dev</a><br>
<br>
<br>
------------------------------<br>
<br>
End of litmus-dev Digest, Vol 81, Issue 5<br>
*****************************************<br>
</blockquote></div>