Re: [Xenomai] interrupt service

[Philippe Gerum <rpm@xenomai.org>]

On 02/25/2015 12:01 AM, Lowell Gilbert wrote:
> Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org> writes:
> 
>> On Fri, Feb 20, 2015 at 02:38:12PM -0500, Lowell Gilbert wrote:
> 
>>> The mailing list stripped my code, so I'll attach it inline.
>>
>> It does not strip it, it puts it on a server that can be accessed
>> with http, so that only the people who want to see it download it,
>> instead of forcibly sending it to all the subscribers.
> 
> And if I'd actually *read* the autogenerated text including the link,
> I'd have known that...
> 
>> Will look at your code later. But at a quick glance I see nothing
>> wrong.
> 
> That's unfortunate, because I'm kind of stuck on this. If I don't
> resolve it soon my colleagues will move the real-time functionality into
> hardware, which I really don't want to see.
> 
> I thought it might have been something in my kernel set-up, but I get
> the same results after I worked my setup back to basics: latest 3.14
> kernel, merged in the i-pipe code from the 3.14 branch in the
> Xenomai.org repository, checked out the v2.6.4 release of Xenomai, ran
> the prepare-kernel script, put the i-pipe TSC code back into smp_twd.c
> to get a high-resolution clock. I may try Xenomai 3 if I have time.
> 

Looks like the real-time core does not reschedule due to the wrong
status returned by the ISR. Does this patch help?

--- attachment.c~	2015-02-25 09:17:31.391445993 +0100
+++ attachment.c	2015-02-25 09:28:25.379426965 +0100
@@ -59,7 +59,7 @@
 	interrupts++;
 	rtdm_event_signal(&tick_ev);

-	return 0;
+	return RTDM_IRQ_HANDLED;
 }

 rtdm_irq_t irq_handle;	/* device IRQ handle */

-- 
Philippe.