From: Philippe Gerum <rpm@xenomai.org>
To: belatronix@domain.hid
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Meaning of cache locking in /proc/xenomai/faults
Date: Fri, 27 Mar 2009 11:28:47 +0100 [thread overview]
Message-ID: <1238149727.6815.151.camel@domain.hid> (raw)
In-Reply-To: <49CC9E46.3050501@domain.hid>
On Fri, 2009-03-27 at 10:37 +0100, Axel Beierlein wrote:
> Philippe Gerum schrieb:
> > On Fri, 2009-03-27 at 10:00 +0100, Axel Beierlein wrote:
> >> Hello,
> >>
> >> on my MPC5200 i have the following output of /proc/xenomai/faults
> >>
> >> TRAP CPU0
> >> 0: 0 (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: -1072753084 (Cache-locking exception)
> >> 15: 0 (Kernel FP unavailable)
> >>
> >> Now i am trying to find out what the negative Value of Cache-locking and
> >> what this Trap general mean and when it was triggered.
> >
> > The negative value is only the sign of an overflow. However, a cache
> > locking exception is specific to FSL_BOOKE archs. What is your kernel
> > release and exact ppc platform configuration?
You can ignore the last two counters, when 2.4.25-ppc is involved, they
contain garbage in fact; this does not have any consequences beyond that
strange output. The patch below should fix them, actually leave them
zeroed.
--- include/asm-ppc/ipipe.h~ 2008-06-08 16:15:51.000000000 +0200
+++ include/asm-ppc/ipipe.h 2009-03-27 11:22:31.000000000 +0100
@@ -80,7 +80,7 @@ do { \
#define IPIPE_TRAP_DEBUG 11 /* Debug exception */
#define IPIPE_TRAP_SPE 12 /* SPE exception */
#define IPIPE_TRAP_ALTASSIST 13 /* Altivec assist exception */
-#define IPIPE_NR_FAULTS 14
+#define IPIPE_NR_FAULTS 16
/* Pseudo-vectors used for kernel events */
#define IPIPE_FIRST_EVENT IPIPE_NR_FAULTS
#define IPIPE_EVENT_SYSCALL (IPIPE_FIRST_EVENT)
--
Philippe.
next prev parent reply other threads:[~2009-03-27 10:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 9:00 [Xenomai-help] Meaning of cache locking in /proc/xenomai/faults Axel Beierlein
2009-03-27 9:25 ` Philippe Gerum
[not found] ` <49CC9E46.3050501@domain.hid>
2009-03-27 10:28 ` Philippe Gerum [this message]
2009-03-27 13:11 ` Axel Beierlein
2009-03-27 13:46 ` Philippe Gerum
2009-03-27 14:15 ` Axel Beierlein
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=1238149727.6815.151.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=belatronix@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.