All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel van Mierlo <marcel.vanmierlo@marel.com>
To: Philippe Gerum <rpm@xenomai.org>,
	Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] High CPU load using q_send under pSOS skin
Date: Fri, 7 Feb 2014 14:32:55 +0000	[thread overview]
Message-ID: <52F4EE97.2070800@marel.com> (raw)
In-Reply-To: <52F4E865.5000200@xenomai.org>


On 07/02/14 14:06, Philippe Gerum wrote:
> On 02/07/2014 02:32 PM, Marcel van Mierlo wrote:
>
>>      - When I comment out q_send (so only call tm_wakeafter) MSW does
>> not increase and stays on zero.
>>      *** Why does q_send cause mode switches?
>
> Where do the data words passed to qsend() come from? Plain regular 
> memory?
>
> Also, what does /proc/xenomai/faults show after runtime?
>

The data words are created on the task stack (struct instance created as 
automatic variable on stack)

I see increasing TRAP 8 (Unaligned access exception) when application is 
running.

TRAP         CPU0
   0:          732    (Data or instruction access)
   1:            0    (Section fault)
   2:            0    (Generic data abort)
   3:            0    (Unknown exception)
   4:            0    (Instruction breakpoint)
   5:            0    (Floating point exception)
   6:            0    (VFP Floating point exception)
   7:            3    (Undefined instruction)
   8:        10067    (Unaligned access exception)

If I comment out q_send TRAP 8 dosent occur. If I pass NULL as data 
words to q_send, TRAP 8 stops... and %CPU remains low....hmmm do I need 
to ensure stack alignment somehow?

Marcel.



  reply	other threads:[~2014-02-07 14:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-06 16:25 [Xenomai] High CPU load using q_send under pSOS skin Marcel van Mierlo
2014-02-06 16:35 ` Gilles Chanteperdrix
2014-02-06 16:57   ` Marcel van Mierlo
2014-02-06 17:26 ` Philippe Gerum
2014-02-06 17:28   ` Philippe Gerum
2014-02-06 19:00   ` Gilles Chanteperdrix
2014-02-07  8:53     ` Philippe Gerum
2014-02-07 13:32       ` Marcel van Mierlo
2014-02-07 13:57         ` Philippe Gerum
2014-02-07 14:03         ` Philippe Gerum
2014-02-07 14:06         ` Philippe Gerum
2014-02-07 14:32           ` Marcel van Mierlo [this message]
2014-02-07 14:38             ` Gilles Chanteperdrix
2014-02-07 15:07               ` Marcel van Mierlo
2014-02-07 15:10                 ` Gilles Chanteperdrix
2014-02-07 15:22                   ` Marcel van Mierlo
2014-02-07 19:23                     ` Gilles Chanteperdrix
2014-02-07 14:08         ` Gilles Chanteperdrix

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=52F4EE97.2070800@marel.com \
    --to=marcel.vanmierlo@marel.com \
    --cc=gilles.chanteperdrix@xenomai.org \
    --cc=rpm@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.