From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: GP Orcullo <kinsamanka@gmail.com>
Cc: Xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] Switchtest failures on ODROIDU3
Date: Thu, 09 Oct 2014 17:14:19 +0200 [thread overview]
Message-ID: <5436A64B.90705@xenomai.org> (raw)
In-Reply-To: <CACreCV+HdWC9Deysy2miL2NZ65RFVRRk87uG9rBaUBrn=hhqag@mail.gmail.com>
On 10/09/2014 01:06 PM, GP Orcullo wrote:
> On Oct 9, 2014 6:16 PM, "Gilles Chanteperdrix" <
> gilles.chanteperdrix@xenomai.org> wrote:
>>
>> On 10/09/2014 12:12 PM, GP Orcullo wrote:
>>> On Thu, Oct 9, 2014 at 6:06 PM, Gilles Chanteperdrix
>>> <gilles.chanteperdrix@xenomai.org> wrote:
>>>> On 10/09/2014 12:02 PM, GP Orcullo wrote:
>>>>> On Mon, Oct 6, 2014 at 6:30 AM, Gilles Chanteperdrix
>>>>> <gilles.chanteperdrix@xenomai.org> wrote:
>>>>>>
>>>>>> It means that Linux was interrupted by Xenomai during its timer
>>>>>> interrupt, and that Xenomai interrupted it for 280us. This may
>>>>>> happens with switchtest if it has a really long chain of context
>>>>>> switches. If you want to check what happened, enable the I-pipe
>>>>>> tracer, and trigger a trace freeze right before this message.
>>>>>>
>>>>>> --
>>>>>> Gilles.
>>>>>
>>>>> One more piece to the puzzle: disabling CONFIG_IPIPE_DEBUG_INTERNAL
>>>>> causes the system to lockup.
>>>>>
>>>> How do you know this is related?
>>>>
>>>> --
>>>> Gilles.
>>>
>>> Sorry, I quoted the wrong message.
>>>
>>> If CONFIG_PREEMPT is disabled and CONFIG_IPIPE_DEBUG_INTERNAL is not
>>> disabled, the system works fine.
>>>
>> So, there is a problem, likely in your port with CONFIG_PREEMPT, but
>> maybe in Xenomai (I need to check, because I am not so sure I tested
>> xeno-regression-test without CONFIG_PREEMPT).
>>
>> And there is a problem in your port without CONFIG_IPIPE_DEBUG_INTERNAL.
>> This I do not need to check, I have tested Xenomai wihout this option
>> enabled.
>>
>> So, my question is: how do you know the two issues are related?
>>
>> --
>> Gilles.
>
> I don't know the answer.
>
> I'm only looking at the effects and not the cause of the issue.
>
> So, where shall I start digging? What's in CONFIG_IPIPE_DEBUG_INTERNAL
> that would somehow suppress the problem?
>
Quite frankly, I would go the other way: check that every piece of code
which may be executed over real-time context does not use any Linux
code. That does not include a lot of code, actually all that is covered
by the porting guide:
- the interrupt controller callbacks (note that the GIC handles some SOC
specific callabcks, so if you have some, you need to check them)
- the chained interrupt demux handlers
- the timer and tsc management functions.
- some workaround specific code that hooks in the iowrite/writel
functions, such as the L2 cache synchronization on omap4.
And it seems that is all, so, there should not be a lot of code to check.
--
Gilles.
next prev parent reply other threads:[~2014-10-09 15:14 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 5:31 [Xenomai] Switchtest failures on ODROIDU3 GP Orcullo
2014-09-30 11:22 ` Gilles Chanteperdrix
2014-09-30 11:30 ` Gilles Chanteperdrix
2014-09-30 12:04 ` GP Orcullo
2014-09-30 12:16 ` Gilles Chanteperdrix
2014-09-30 23:32 ` GP Orcullo
2014-10-01 7:54 ` Gilles Chanteperdrix
2014-10-01 9:12 ` GP Orcullo
2014-10-01 9:20 ` Gilles Chanteperdrix
2014-10-02 13:27 ` GP Orcullo
2014-10-02 13:36 ` Gilles Chanteperdrix
2014-10-02 15:52 ` GP Orcullo
2014-10-02 17:13 ` Gilles Chanteperdrix
2014-10-02 23:40 ` GP Orcullo
2014-10-03 3:35 ` GP Orcullo
2014-10-03 7:20 ` Gilles Chanteperdrix
2014-10-03 8:45 ` GP Orcullo
2014-10-03 8:57 ` Gilles Chanteperdrix
2014-10-03 10:58 ` GP Orcullo
2014-10-03 13:37 ` Gilles Chanteperdrix
2014-10-03 15:28 ` GP Orcullo
2014-10-03 19:14 ` Gilles Chanteperdrix
2014-10-03 22:45 ` GP Orcullo
2014-10-03 22:48 ` Gilles Chanteperdrix
2014-10-04 10:26 ` GP Orcullo
2014-10-04 11:31 ` Gilles Chanteperdrix
2014-10-05 22:00 ` GP Orcullo
2014-10-05 22:04 ` Gilles Chanteperdrix
2014-10-05 22:24 ` GP Orcullo
2014-10-05 22:30 ` Gilles Chanteperdrix
2014-10-09 10:02 ` GP Orcullo
2014-10-09 10:06 ` Gilles Chanteperdrix
2014-10-09 10:12 ` GP Orcullo
2014-10-09 10:16 ` Gilles Chanteperdrix
2014-10-09 10:41 ` Gilles Chanteperdrix
2014-10-09 11:06 ` GP Orcullo
2014-10-09 13:06 ` Gilles Chanteperdrix
2014-10-09 15:14 ` Gilles Chanteperdrix [this message]
2014-10-20 7:29 ` GP Orcullo
2014-10-20 7:33 ` Gilles Chanteperdrix
2014-10-22 6:28 ` Gilles Chanteperdrix
2014-10-29 1:23 ` GP Orcullo
2014-10-29 6:16 ` Gilles Chanteperdrix
2014-10-29 7:24 ` GP Orcullo
2014-10-29 7:26 ` Gilles Chanteperdrix
2014-10-29 7:47 ` GP Orcullo
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=5436A64B.90705@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=kinsamanka@gmail.com \
--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.