From: Daniel.Thibault@drdc-rddc.gc.ca (Thibault, Daniel)
Subject: [lttng-dev] sched_switch event
Date: Thu, 6 Feb 2014 20:18:27 +0000 [thread overview]
Message-ID: <48CF5AC71E61DB46B70D0F388054EFFD267DFB0B@VAL-E-02.valcartier.drdc-rddc.gc.ca> (raw)
-----Message d'origine-----
> In linux-source-3.2.0/include/trace/events/sched.h, or
> linux-headers-3.2.0-53/include/trace/events/sched.h, or
> lttng-modules/instrumentation/events/mainline/sched.h,
> we have in part:
>
> TP_fast_assign(
> memcpy(__entry->next_comm, next->comm, TASK_COMM_LEN);
> __entry->prev_pid = prev->pid;
> __entry->prev_prio = prev->prio;
> __entry->prev_state = __trace_sched_switch_state(prev);
> memcpy(__entry->prev_comm, prev->comm, TASK_COMM_LEN);
> __entry->next_pid = next->pid;
> __entry->next_prio = next->prio;
> ),
Scratch that, lttng-modules/instrumentation/events/lttng-module/sched.h has the same code, and I now realise the TP_fast_assign is not switching the prev_comm and next_comm fields (it is correctly mapping __entry->next_comm to next->comm), it's just that the copies are declared out of order. TP_fast_assign is essentially a parallelised process.
Sorry about the false alarm.
Daniel U. Thibault
Protection des syst?mes et contremesures (PSC) | Systems Protection & Countermeasures (SPC) Cyber s?curit? pour les missions essentielles (CME) | Mission Critical Cyber Security (MCCS) R & D pour la d?fense Canada - Valcartier (RDDC Valcartier) | Defence R&D Canada - Valcartier (DRDC Valcartier)
2459 route de la Bravoure
Qu?bec QC? G3J 1X5
CANADA
Vox?: (418) 844-4000 x4245
Fax?: (418) 844-4538
NAC?: 918V QSDJ <http://www.travelgis.com/map.asp?addr=918V%20QSDJ>
Gouvernement du Canada?| Government of Canada <http://www.valcartier.drdc-rddc.gc.ca/>
next reply other threads:[~2014-02-06 20:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 20:18 Thibault, Daniel [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-02-06 20:04 Thibault, Daniel
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=48CF5AC71E61DB46B70D0F388054EFFD267DFB0B@VAL-E-02.valcartier.drdc-rddc.gc.ca \
--to=daniel.thibault@drdc-rddc.gc.ca \
/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