From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Philippe Gerum <rpm@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] High CPU load using q_send under pSOS skin
Date: Thu, 06 Feb 2014 20:00:43 +0100 [thread overview]
Message-ID: <52F3DBDB.4060805@xenomai.org> (raw)
In-Reply-To: <52F3C5DD.8010208@xenomai.org>
On 02/06/2014 06:26 PM, Philippe Gerum wrote:
>> Every 2.0s: cat /proc/xenomai/stat Sat Jan 1
>> 00:09:03 2000
>>
>> CPU PID MSW CSW PF STAT %CPU NAME
>> 0 0 0 186436 0 00500080 94.2 ROOT/0
>> 0 2882 16 427 0 00300380 0.0 MAIN
>> 0 2883 0 54128 0 00300184 1.0 onemsscheduler
>> 0 2884 0 542 0 00300184 0.0 FREE
>> 0 2885 0 1499 0 00300184 0.0 flsh
>> 0 2886 0 1 0 00300182 0.0 EWRN
>> 0 2887 0 45158 0 00300186 0.8 EEDT
>> 0 2888 0 53921 0 00300184 1.4 RESP
>> 0 2889 1 1 0 00300380 0.0 SERV
>> 0 2890 0 10784 0 00300184 0.4 CMND
>> 0 2891 2 1370 0 00300186 0.1 SERP
>> 0 2896 0 53080 0 00300184 0.8 SERO
>> 0 2899 0 536 0 00300186 0.0 CANP
>> 0 2900 0 1 0 00300182 0.0 CANG
>> 0 2901 0 1 0 00300182 0.0 CANE
>> 0 2902 0 315 0 00300182 0.0 CANT
>> 0 2903 1 1 0 00300380 0.0 CNMN
>> 0 2904 236 628 0 00300184 0.0 CIOW
>> 0 0 0 699350 0 00000000 1.0 IRQ83: [timer]
>>
>>
>> So questions are:
>>
>> - Why does the %CPU under xenomai/stat not reflect whats reported by top
>
> Because top reports the CPU consumed when Linux is active, which
> excludes Xenomai activity.
>
>> (where is the 40% going)?
>
> Good question.
I think we have a known issue: the registers passed to Linux timer tick
are the ones of the last timer tick, which may very well happen to
always hit the same task. Could this be the cause?
Is the MAIN task the one which does the tm_wkafter ?
Is the hardware timer of the beaglebone black shared with Linux (like
omap4) or do linux and xenomai have different timers (like omap3)?
Could you arm the T_WARNSW bit to see if the MAIN task experiences mode
switches?
--
Gilles.
next prev parent reply other threads:[~2014-02-06 19:00 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 [this message]
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
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=52F3DBDB.4060805@xenomai.org \
--to=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.