Re: Bug in xenomai 3.2.x on ARM

["François Legal" <francois.legal@thom.fr.eu.org>]

Le Mardi, Mars 22, 2022 19:57 CET, Jan Kiszka <jan.kiszka@siemens.com> a écrit:

> On 22.03.22 18:31, Greg Gallagher via Xenomai wrote:
> > On Tue, Mar 22, 2022 at 12:49 PM François Legal via Xenomai <
> > xenomai@xenomai.org> wrote:
> >
> >> Hello,
> >>
> >> trying to port a running Xenomai 3.1.x/Linux 4.4.x system to Xenomai
> >> 3.2.x/Linux 4.4.x running on Zynq7000, I found a (maybe) bug in intr.c
> >>
> >> In xnintr_attach, the call to ipipe_set_irq_affinity (when in SMP) expects
> >> a 0 return code. However, on my platform, I end up in irq_gic.c in
> >> gic_set_affinity() which returns IRQ_SET_MASK_OK_DONE (2) when everything
> >> is fine.
> >>
> >> This IRQ_SET_MASK_OK_DONE does not seem very common in the kernel (I could
> >> find a few occurences, on Gic v3 so maybe AARCH64 has the same problem,
> >> plus some PCI devices).
> >>
> >> I was wondering if this was something to fix in ipipe or xenomai ?
> >>
> >> François
> >
> >
> > Do the newer kernels have the same return value? Do we test 3.2.x on the
> > older kernels? Maybe just cip ?
> >
>
> We limited testing to 4.4-cip with 3.0.x. Newer kernels require newer
> Xenomai, and vice versa.
>
> But let's first understand if the issue if 4.4-specific.
>
> Jan
>
> --
> Siemens AG, Technology
> Competence Center Embedded Linux

 In 4.4, gic_set_affinity returns IRQ_SET_MASK_OK (aka 0). In 4.19 is already returns IRQ_SET_MASK_OK_DONE , but in Xenomai 3.1.x, there were no call to ipipe_set_irq_affinity AFAIK.

François