From: Tschaeche IT-Services <services@domain.hid>
To: xenomai@xenomai.org
Subject: [Xenomai-help] Monitoring Xenomai scheduler switches
Date: Thu, 20 May 2010 16:26:14 +0200 [thread overview]
Message-ID: <20100520142614.GA23058@domain.hid> (raw)
[-- Attachment #1: Type: text/plain, Size: 599 bytes --]
Hi,
we started an application which monitors task switches
using Xenomai 2.5.3.
For monitoring primary domain switches we hooked
in our code by using rt_task_add_hook(T_HOOK_SWITCH)
(storing a timestamp and the Xenomai task ID in an array,
which is read later by user space appl from shared memory).
It seems, that our code is not called when Xenomai switches to the ROOT task.
We already had this issue with Xenomai 2.4.10
and solved it by applying the attached patch.
How can we catch these Xenomai scheduler events in 2.5.3?
What is the reason for filtering them out?
Best regards,
Olli
[-- Attachment #2: Add-scheduler-switch-notification-for-all-switches.patch --]
[-- Type: text/x-diff, Size: 613 bytes --]
Index: xenomai-2.4.10/ksrc/nucleus/pod.c
===================================================================
--- xenomai-2.4.10.orig/ksrc/nucleus/pod.c 2009-08-11 15:53:55.000000000 +0200
+++ xenomai-2.4.10/ksrc/nucleus/pod.c 2010-01-27 12:41:05.000000000 +0100
@@ -2561,7 +2561,7 @@
nkpod->schedhook(runthread, XNRUNNING);
#endif /* __XENO_SIM__ */
- if (!emptyq_p(&nkpod->tswitchq) && !xnthread_test_state(runthread, XNROOT)) {
+ if (!emptyq_p(&nkpod->tswitchq)) {
trace_mark(xn_nucleus, thread_callout,
"thread %p thread_name %s hook %s",
runthread, xnthread_name(runthread), "SWITCH");
next reply other threads:[~2010-05-20 14:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 14:26 Tschaeche IT-Services [this message]
2010-05-20 14:54 ` [Xenomai-help] Monitoring Xenomai scheduler switches Andreas Glatz
2010-05-21 9:04 ` Gilles Chanteperdrix
2010-05-21 9:28 ` Philippe Gerum
2010-05-25 11:44 ` Tschaeche IT-Services
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=20100520142614.GA23058@domain.hid \
--to=services@domain.hid \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.