All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Lange Norbert <norbert.lange@andritz.com>,
	"Xenomai (xenomai@xenomai.org)" <xenomai@xenomai.org>
Subject: Re: xenomai.supported_cpus not working as intended?
Date: Mon, 13 Jul 2020 19:52:20 +0200	[thread overview]
Message-ID: <2d3027e0-83d7-0e98-8c2b-7b7bf06cadb3@siemens.com> (raw)
In-Reply-To: <VI1PR05MB591724DFD45C58A897803F95F6600@VI1PR05MB5917.eurprd05.prod.outlook.com>

On 13.07.20 15:37, Lange Norbert via Xenomai wrote:
> Hello,
> 
> I am using Xenomai 3.1 and I tried once more to tie Linux to Core0, and RT to the remaining Cores.
> It seems that both Linux and Xenomai favor Core0, as rtnet-stack rtnet-rtpc seem to always run on that.
> Network drivers will process the IRQs on all cores, but realistally all are handles at Core0.
> 
> I tries the commandline xenomai.supported_cpus=0xFFFE, but this doesn’t seem to work right.
> 
> I get stuck Xenomai processes, and entries in dmesg (both with and without the isolcpus parameter).
> Kernel cmdline is like this: irqaffinity=0 xenomai.smi=disabled isolcpus=1-3 xenomai.supported_cpus=0xFFFE
> 
> Running a Xenomai Process looks like this:
> 
> # /usr/xenomai/bin/clocktest
> [  191.759690] [Xenomai] thread clocktest[575] switched to non-rt CPU0, aborted.
> == Testing built-in CLOCK_REALTIME (0)
> CPU      ToD offset [us] ToD drift [us/s]      warps max delta [us]
> --- -------------------- ---------------- ---------- --------------
>    0                  0.0            0.000          0            0.0
>    1           -1450249.3          -36.240          0            0.0
>    2           -1450249.8          -36.040          0            0.0
>    3           -1450249.4          -35.292          0            0.0
> 
> And similar stuff happens when booting, Kernel dmesg is following.
> 
> So I don’t see how xenomai.supported_cpus can be safely used,
> It more or less works by chance for me (processes not getting stuck)

IIRC, we had troubles with starting off RTDM kernel tasks (like RTnet 
uses) when supported_cpus is used. There is no good control over where a 
kernel task comes up, specifically when it started by a built-in driver.

Or are you seeing issues even without RTnet in the picture?

cpus_supported is one of those "would be nice but usually broken when 
needed" feature because we do not consistently test it.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux


  reply	other threads:[~2020-07-13 17:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-13 13:37 xenomai.supported_cpus not working as intended? Lange Norbert
2020-07-13 17:52 ` Jan Kiszka [this message]
2020-07-14  7:41   ` Lange Norbert

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=2d3027e0-83d7-0e98-8c2b-7b7bf06cadb3@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=norbert.lange@andritz.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.