From: Tom Z <tomz30@yahoo.com>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] questions regarding context switch
Date: Thu, 21 Mar 2013 16:37:05 -0500 [thread overview]
Message-ID: <514B7D81.8040103@yahoo.com> (raw)
In-Reply-To: <514B7676.1090404@xenomai.org>
Hi Gilles,
Thanks for your prompt reply. You are amazing:)
> Any news about the issue you described here:
> http://www.xenomai.org/pipermail/xenomai/2013-March/028005.html
> ?
You are correct. The link order is wrong. I figured out a working order
by trial&error, as follows:
CFLAGS=$(shell xeno-config --skin=native --cflags)
LDFLAGS=$(shell xeno-config --skin=native --ldflags)
gcc $(CFLAGS) main.c $(LDFLAGS) -o main
Sincerely,
Tom
On 3/21/2013 4:07 PM, Gilles Chanteperdrix wrote:
> On 03/21/2013 10:02 PM, Tom Z wrote:
>
>> when an RT_ALARM expires and executes a handler, shouldn't
>> there be a context switch if an RT_TASK is running? The task mentioned
>> above executes rt_timer_spin for 100ms during each period, and the
>> highest priority among all the 8 tasks, so while it is executing, the
>> RT_ALARM must expire for many times -- but why does it NOT increase the
>> number of the tasks' context switches?
>
> Hi,
>
> Because the number of context switches is the number of task switches.
> An alarm in kernel-space is simply triggered on the timer interrupt, so,
> it does not need any task switch. An alarm is not a task.
>
> Any news about the issue you described here:
> http://www.xenomai.org/pipermail/xenomai/2013-March/028005.html
> ?
>
> Regards.
>
>
prev parent reply other threads:[~2013-03-21 21:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 21:02 [Xenomai] questions regarding context switch Tom Z
2013-03-21 21:07 ` Gilles Chanteperdrix
2013-03-21 21:37 ` Tom Z [this message]
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=514B7D81.8040103@yahoo.com \
--to=tomz30@yahoo.com \
--cc=gilles.chanteperdrix@xenomai.org \
--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.