From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Xenomai core <Xenomai-core@domain.hid>
Subject: Re: [Xenomai-core] [Xenomai-git] Jan Kiszka : nucleus: Fix interrupt handler tails
Date: Fri, 17 Jun 2011 18:53:51 +0200 [thread overview]
Message-ID: <4DFB869F.9080006@domain.hid> (raw)
In-Reply-To: <E1QXaC2-0007dE-Ar@domain.hid>
On 06/17/2011 04:38 PM, GIT version control wrote:
> Module: xenomai-jki
> Branch: for-upstream
> Commit: 7203b1a66ca0825d5bcda1c3abab9ca048177914
> URL: http://git.xenomai.org/?p=xenomai-jki.git;a=commit;h=7203b1a66ca0825d5bcda1c3abab9ca048177914
>
> Author: Jan Kiszka <jan.kiszka@domain.hid>
> Date: Fri Jun 17 09:46:19 2011 +0200
>
> nucleus: Fix interrupt handler tails
>
> Our current interrupt handlers assume that they leave over the same task
> and CPU they entered. But commit f6af9b831c broke this assumption:
> xnpod_schedule invoked from the handler tail can now actually trigger a
> domain migration, and that can also include a CPU migration. This causes
> subtle corruptions as invalid xnstat_exectime_t objects may be restored
> and - even worse - we may improperly flush XNHTICK of the old CPU,
> leaving Linux timer-wise dead there (as happened to us).
>
> Fix this by moving XNHTICK replay and exectime accounting before the
> scheduling point. Note that this introduces a tiny imprecision in the
> accounting.
I am not sure I understand why moving the XNHTICK replay is needed: if
we switch to secondary mode, the HTICK is handled by xnpod_schedule
anyway, or am I missing something?
--
Gilles.
next parent reply other threads:[~2011-06-17 16:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1QXaC2-0007dE-Ar@domain.hid>
2011-06-17 16:53 ` Gilles Chanteperdrix [this message]
2011-06-17 17:03 ` [Xenomai-core] [Xenomai-git] Jan Kiszka : nucleus: Fix interrupt handler tails Jan Kiszka
2011-06-17 18:55 ` Gilles Chanteperdrix
2011-06-18 10:21 ` Jan Kiszka
2011-06-18 12:09 ` Gilles Chanteperdrix
2011-06-18 12:10 ` Jan Kiszka
2011-06-18 12:56 ` Gilles Chanteperdrix
2011-06-18 13:07 ` Jan Kiszka
2011-06-18 13:12 ` Gilles Chanteperdrix
2011-06-18 13:16 ` Jan Kiszka
2011-06-18 13:40 ` Gilles Chanteperdrix
2011-06-18 13:47 ` Jan Kiszka
2011-06-18 14:01 ` Gilles Chanteperdrix
2011-06-18 14:06 ` Jan Kiszka
2011-06-18 15:01 ` Gilles Chanteperdrix
2011-06-18 15:57 ` Jan Kiszka
2011-06-18 13:58 ` Jan Kiszka
2011-06-19 15:41 ` Gilles Chanteperdrix
2011-06-20 16:43 ` Jan Kiszka
2011-06-20 17:33 ` Gilles Chanteperdrix
2011-06-20 19:38 ` Jan Kiszka
2011-06-20 19:41 ` Gilles Chanteperdrix
2011-06-20 19:41 ` Jan Kiszka
2011-06-20 19:51 ` Gilles Chanteperdrix
2011-06-20 20:41 ` Jan Kiszka
2011-06-20 20:52 ` Gilles Chanteperdrix
2011-06-20 21:13 ` Jan Kiszka
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=4DFB869F.9080006@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=Xenomai-core@domain.hid \
/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.