Re: [Xenomai] I-Pipe Tracer and linux ftrace

[Jan Kiszka <jan.kiszka@siemens.com>]

On 2015-06-23 19:00, Jan Kiszka wrote:
> On 2015-06-23 18:18, Antoine Durand wrote:
>> booting with 'maxcpus=2' in my case has the same behavior than
>> CONFIG_NR_CPUS=2
>> the clocksource switche to refined-jiffies and system time is wrong (very
>> very slow)
> 
> Ugh, reproduced something with a 4-core VM and maxcpus=2. I get a kernel
> crash in __ipipe_ack_hrtimer_irq. Probably an online vs. possible cpus
> issue. Will look into this.

Interesting: maxcpus limits the number of cores the kernel will bring
online on its own, but it does not stop the kernel from detecting more,
keeping them recorded as offline. Now userland jumps in and may decide
to bring them online as well, which happens with my recent OpenSUSE
system, not with a much older one. And that means cpu hotplugging, which
does not work when Xenomai considers those CPUs as part of the RT set.
Still, excluding the additional ones per supported_cpus mask is not
sufficient.

Anyway, what works fine here is nr_cpus=2 - clocksource TSC is chosen,
and no crash. Could you check that as well?

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux