From: Per Oberg <pero@wolfram.com>
To: xenomai@lists.linux.dev
Subject: Re: Controlling cpu for interrupts
Date: Tue, 10 Jun 2025 11:00:05 -0500 (CDT) [thread overview]
Message-ID: <681487015.1166416.1749571205337.JavaMail.zimbra@wolfram.com> (raw)
In-Reply-To: <0f7091b9-5c6f-4c44-8919-8e8c7e21913e@siemens.com>
----- Den 10 jun 2025, på kl 16:09, Jan Kiszka jan.kiszka@siemens.com skrev:
>> Hi
>> I have a setup with
>> - Xenomai 3.1
>> - Linux 4.14 ish
> Ouch - dead horse (kernel) warning!
Thanks, yes, I know. I am currently debugging an older setup.
>> - RT Net e1000e + igb
>> - Peak PCAN
> Standard Linux driver for CAN, right? This is at least my interpretation
> based on the irq names below.
No, actually not. I should have said. It's the Peak PCAN xenomai driver
>> When I look closely on the rt-threads I can see that the IRQ from the CAN seems
>> to be coming in on certain cores, but now always the same.
>>
>> Here is an example of my ../xenomai/irq file:
>>
>> IRQ CPU0 CPU1 CPU2 CPU3
>> 18: 0 0 0 130419960 pcan pcan pcan pcan
>> pcan pcan
>> 19: 88638780 0 0 0 pcan pcan pcan pcan
>> 127: 3215 0 0 0 rteth0-TxRx-0
>> Thus, for this case it seems like IRQ19 is handled by CPU0 while IRQ18 is
>> handled on CPU3
>>
>> What is the heuristics, if any, used for decing this ?
>>
> /proc/irq/*/smp_affinity apply here, at least for standard IRQs. If the
> mask is containing more than one core, it's up to the IRQ controllers
> and CPUs who will take an event first.
Thanks, what would be the corresponding place to look for the RTDM stuff ?
> Jan
Thanks
Per Öberg
> --
> Siemens AG, Foundational Technologies
> Linux Expert Center
prev parent reply other threads:[~2025-06-10 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 11:27 Controlling cpu for interrupts Per Oberg
2025-06-10 14:09 ` Jan Kiszka
2025-06-10 16:00 ` Per Oberg [this message]
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=681487015.1166416.1749571205337.JavaMail.zimbra@wolfram.com \
--to=pero@wolfram.com \
--cc=xenomai@lists.linux.dev \
/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.