From: Philippe Gerum <rpm@xenomai.org>
To: Fillod Stephane <stephane.fillod@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [PATCH] I see negative faults
Date: Thu, 03 Jan 2008 12:29:50 +0100 [thread overview]
Message-ID: <477CC72E.4060402@domain.hid> (raw)
In-Reply-To: <0B45E93C5FF65740AEAE690BF3848B7A4AB2FD@rennsmail04.eu.thmulti.com>
Fillod Stephane wrote:
> Philippe Gerum wrote:
>> Fillod Stephane wrote:
>>> Attached is an obvious patch (to me). Part of it is across I-Pipe.
>>> Is there a reason why the counter was declared signed?
>>>
>> Well, because the number of faults was not expected to increase
>> indefinitely... Is it the PF count we are talking about, on a mpc85xx?
>
> Indeed. It's a MPC8541E.
>
> $ cat /proc/xenomai/faults
> TRAP CPU0
> 0: 4 (Data or instruction access)
> 1: 0 (Alignment)
> 2: 0 (Altivec unavailable)
> 3: 0 (Program check exception)
> 4: 0 (Machine check exception)
> 5: 0 (Unknown)
> 6: 0 (Instruction breakpoint)
> 7: 0 (Run mode exception)
> 8: 0 (Single-step exception)
> 9: 0 (Non-recoverable exception)
> 10: 0 (Software emulation)
> 11: 0 (Debug)
> 12: 0 (SPE)
> 13: 0 (Altivec assist)
> 14: 3221526824 (Cache-locking exception)
> 15: 0 (Kernel FP unavailable)
>
> Any clue?
>
Book-E cache locking instructions are still considered as privileged ops
by the kernel, so userland gets a SIGILL as a result of issuing them,
therefore Xenomai has to switch back the context to secondary mode for
this reason. There seems to be something going on at application level.
--
Philippe.
next prev parent reply other threads:[~2008-01-03 11:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-03 10:59 [Xenomai-core] [PATCH] I see negative faults Fillod Stephane
2008-01-03 11:29 ` Philippe Gerum [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-12-17 15:10 Fillod Stephane
2007-12-27 20:33 ` Philippe Gerum
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=477CC72E.4060402@domain.hid \
--to=rpm@xenomai.org \
--cc=stephane.fillod@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.