<div dir="ltr"><div dir="ltr"><div>Hi Björn,</div><div><br></div><div>UNLOCK overhead records continued to be incomplete, even without the -i parameter. Debugging the ft2csv code, I noticed that it is coming out of the loop in the statement below:</div><div><br></div><div><a href="https://github.com/LITMUS-RT/feather-trace-tools/blob/master/src/ft2csv.c#L156">https://github.com/LITMUS-RT/feather-trace-tools/blob/master/src/ft2csv.c#L156</a></div><div><br></div><div>By modifying this piece of code, I was able to retrieve the records. </div><div><br></div><div>Best regards,</div><div><br></div><div>Ricardo</div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Em qui, 16 de mai de 2019 às 17:46, <<a href="mailto:litmus-dev-request@lists.litmus-rt.org" target="_blank">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: P-RES: waking up tasks before timeout (Björn Brandenburg)<br>
2. Re: litmus-dev Digest, Vol 81, Issue 5 (Björn Brandenburg)<br>
3. Overheads (Martinez Garcia Jorge Luis (PS-EC/ESB2))<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Thu, 16 May 2019 12:17:41 +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] P-RES: waking up tasks before timeout<br>
Message-ID: <<a href="mailto:55682065-9CC1-4992-8D9D-B2E45966C0CD@mpi-sws.org" target="_blank">55682065-9CC1-4992-8D9D-B2E45966C0CD@mpi-sws.org</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
<br>
<br>
> On 16. May 2019, at 11:32, Julien Haibach <<a href="mailto:julien.haibach@yahoo.de" target="_blank">julien.haibach@yahoo.de</a>> wrote:<br>
> <br>
> currently I am working on a mode change implementation, on top of the P-RES plugin.<br>
> In the case of a mode change, tasks sleeping may need to be woken up before their previous mode release time.<br>
> <br>
> On job completion tasks are put asleep with <br>
> schedule_hrtimeout(&next_release, HRTIMER_MODE_ABS);<br>
> the task state is TASK_INTERRUPTIBLE - litmus/jobs.c:147<br>
> <br>
> So my question is what is the best way to wake up a sleeping task in this plugin?<br>
> I tried to call wake_up_process() from the plugin, but this did not work out of the box.<br>
> <br>
<br>
Hi Julien,<br>
<br>
these are standard Linux interfaces, so the regular methods apply. For instance, interruptible tasks can be woken up prematurely by a signal. Thus, presumably there are APIs for waking sleeping tasks early to implement signal delivery. I’d investigate that code path (or read through the various wake-up wrappers) to find the right API to use. <br>
<br>
Best,<br>
Björn<br>
<br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: smime.p7s<br>
Type: application/pkcs7-signature<br>
Size: 5061 bytes<br>
Desc: not available<br>
URL: <<a href="http://lists.litmus-rt.org/pipermail/litmus-dev/attachments/20190516/5f1a084b/attachment-0001.bin" rel="noreferrer" target="_blank">http://lists.litmus-rt.org/pipermail/litmus-dev/attachments/20190516/5f1a084b/attachment-0001.bin</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Thu, 16 May 2019 12:21:52 +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 5<br>
Message-ID: <<a href="mailto:087E2F91-462C-460E-8165-EDECE0E6F4A0@mpi-sws.org" target="_blank">087E2F91-462C-460E-8165-EDECE0E6F4A0@mpi-sws.org</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
<br>
<br>
> On 16. May 2019, at 04:16, Ricardo Teixeira <<a href="mailto:ricardo.btxr@gmail.com" target="_blank">ricardo.btxr@gmail.com</a>> wrote:<br>
> <br>
> 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? <br>
<br>
Unless you are using the -i option, this should not make a difference. <br>
<br>
- Björn<br>
<br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: smime.p7s<br>
Type: application/pkcs7-signature<br>
Size: 5061 bytes<br>
Desc: not available<br>
URL: <<a href="http://lists.litmus-rt.org/pipermail/litmus-dev/attachments/20190516/51e8a3e0/attachment-0001.bin" rel="noreferrer" target="_blank">http://lists.litmus-rt.org/pipermail/litmus-dev/attachments/20190516/51e8a3e0/attachment-0001.bin</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Thu, 16 May 2019 20:45:23 +0000<br>
From: "Martinez Garcia Jorge Luis (PS-EC/ESB2)"<br>
<<a href="mailto:JorgeLuis.MartinezGarcia@de.bosch.com" target="_blank">JorgeLuis.MartinezGarcia@de.bosch.com</a>><br>
To: "<a href="mailto:litmus-dev@lists.litmus-rt.org" target="_blank">litmus-dev@lists.litmus-rt.org</a>" <<a href="mailto:litmus-dev@lists.litmus-rt.org" target="_blank">litmus-dev@lists.litmus-rt.org</a>><br>
Subject: [LITMUS^RT] Overheads<br>
Message-ID: <<a href="mailto:f87dc7aaa9464c66b526b04f88bd9c0f@de.bosch.com" target="_blank">f87dc7aaa9464c66b526b04f88bd9c0f@de.bosch.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
Dear Björn,<br>
I'm currently trying to compare scheduling overheads under different schedulers. To that end, I would like to understand the overhead name convention used in Litmus. After computing some statistics by means of ft-compute-stats, I can see the following categories: CXS, RELEASE, RELEASE-LATENCY, SCHED2, SCHED, and SEND-RESCHED.<br>
Please correct me, if I am wrong, I assume that CXS accounts for the overhead related to process switching (context-switch overhead) and SCHED + SCHED2 for process selection (scheduling overhead).<br>
Do RELEASE and RELEASE-LATENCY account for the execution of a release ISR (release overhead) and the delay until the release ISR starts execution (event latency)?<br>
What does SEND-RESCHED account for?<br>
Once a job is completed there is some kind of overhead involved like the one related to the trap generated by its completion, does this overhead fall under one of those categories?<br>
Best,<br>
Jorge<br>
<br>
<br>
<br>
<br>
<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.litmus-rt.org/pipermail/litmus-dev/attachments/20190516/dc200284/attachment.html" rel="noreferrer" target="_blank">http://lists.litmus-rt.org/pipermail/litmus-dev/attachments/20190516/dc200284/attachment.html</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 7<br>
*****************************************<br>
</blockquote></div>