[Xenomai-core] v2.1-rc4 RTDM bug

[Xenomai-core] v2.1-rc4 RTDM bug

[Hannes Mayer]

Ciao Jan!

It doesn't seem to make a difference if one uses
RTDM_IRQ_NONE or RTDM_IRQ_HANDLED.
With RTDM_IRQ_NONE the IRQ should be passed to linux,
right ? But it doesn't seem to happen - this brought
up the "top" problem I've posted a few days ago.

Best regards,
Hannes.

Re: [Xenomai-core] v2.1-rc4 RTDM bug

[Hannes Mayer]

Hannes Mayer wrote:
> Ciao Jan!
> 
> It doesn't seem to make a difference if one uses
> RTDM_IRQ_NONE or RTDM_IRQ_HANDLED.
> With RTDM_IRQ_NONE the IRQ should be passed to linux,
> right ? But it doesn't seem to happen - this brought
> up the "top" problem I've posted a few days ago.

Returning XN_ISR_PROPAGATE passes the grabbed timer
interrupt to Linux and "top" works again.

Best regards,
Hannes.

Re: [Xenomai-core] v2.1-rc4 RTDM bug

[Jan Kiszka]

[-- Attachment #1: Type: text/plain, Size: 776 bytes --]

Hannes Mayer wrote:
> Hannes Mayer wrote:
>> Ciao Jan!
>>
>> It doesn't seem to make a difference if one uses
>> RTDM_IRQ_NONE or RTDM_IRQ_HANDLED.
>> With RTDM_IRQ_NONE the IRQ should be passed to linux,
>> right ? But it doesn't seem to happen - this brought
>> up the "top" problem I've posted a few days ago.
> 
> Returning XN_ISR_PROPAGATE passes the grabbed timer
> interrupt to Linux and "top" works again.
> 

As forwarding interrupts to the non-realtime domain is not a common
use-case of realtime device drivers, I decided to drop the propagation
support at RTDM level. So if you are including this mechanism in your
demo, please mark this pattern as something RTDM drivers should normally
NOT do (and explain what's reason for it here).

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

Re: [Xenomai-core] v2.1-rc4 RTDM bug

[Hannes Mayer]

Jan Kiszka wrote:
> Hannes Mayer wrote:
>> Hannes Mayer wrote:
>>> Ciao Jan!
>>>
>>> It doesn't seem to make a difference if one uses
>>> RTDM_IRQ_NONE or RTDM_IRQ_HANDLED.
>>> With RTDM_IRQ_NONE the IRQ should be passed to linux,
>>> right ? But it doesn't seem to happen - this brought
>>> up the "top" problem I've posted a few days ago.
>> Returning XN_ISR_PROPAGATE passes the grabbed timer
>> interrupt to Linux and "top" works again.
>>
> 
> As forwarding interrupts to the non-realtime domain is not a common
> use-case of realtime device drivers, I decided to drop the propagation
> support at RTDM level. So if you are including this mechanism in your
> demo, please mark this pattern as something RTDM drivers should normally
> NOT do (and explain what's reason for it here).

Thanks Jan!

I'll add that in a few.

Best regards,
Hannes.