Re: [Xenomai] interrupt service

[Lowell Gilbert <kludge@be-well.ilk.org>]

Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org> writes:

> On Fri, Mar 06, 2015 at 05:58:25PM -0500, Lowell Gilbert wrote:
>> I meant *without* using /proc/xenomai/affinity. Fixed below:
>> 
>> Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org> writes:
>> 
>> > Another problem may be in handling the /proc/xenomai/affinity, so
>> > could you try without using it? Same for isolcpus. If the ISR runs
>> > on cpu0 and the tasks run on cpu1, an IPI should be sent in
>> > __xnpod_schedule to wake up the task blocked in read, you can check
>> > whether the IPI is sent by using ipipe_trace_special for instance
>> > and checking the tracer trace.
>> 
>> How would I get a kernel task to run on a specific CPU without using
>> /proc/xenomai/affinity? rtdm_task_init() specifically calls out
>> ALL_CPUS.
>> 
>> Yes, I could change that code, but it seems like the sort of thing that
>> exists -- I just can't find it.
>
> The idea is to stop forcing the task to run on a specific CPU to see
> whether the problem you observe comes from there.

I guess I read more into your statement than was intended.

Yes, I have done that, and the behaviour is similar.

Be well.