Re: [Xenomai-help] Saving floating point registers inside ISR

[Jan Kiszka <jan.kiszka@domain.hid>]

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

Henry Bausley wrote:
> I am converting a 440EP power pc FSM Labs RT-Linux application to a
> Xenomai 2.4.2 posix application. Previously we saved the floating point
> registers in the ISR.  I had the following code with RTLinux.
> 
> //-----------------------------------------------------------------------------
> int phase_intr(xnintr_t *cookie)
> {
>   rthal_fpenv_t fpustate;

Do you know how large this structure is? And do you know how much stack
space is still free when entering here, in the worst case? That may
differ from RTLinux, probably running on some older kernel.

> 
>   rthal_save_fpu(&fpustate);
> 
>   phase();
> 
>   rthal_restore_fpu(&fpustate);
>   return (XN_ISR_HANDLED);
> }
> 
> with xenomai if we do the the same thing the system hangs.
> 
> 
> However if we make the location where we save the registers global, or
> declare it static inside the ISR we don't have a problem.  I don't want

That should ring the bell above...

> to do that since there are cases when the interrupt can be re-entered.
> Does anyone have any ideas?
> 
> rthal_fpenv_t fpustate;
> 
> //-----------------------------------------------------------------------------
> int phase_intr(xnintr_t *cookie)
> {
> 
>   rthal_save_fpu(&fpustate);
> 
>   phase();
> 
>   rthal_restore_fpu(&fpustate);
>   return (XN_ISR_HANDLED);
> }
> 

If the stack size is not the problem here, compare to disassembly of the
involved versions, local vs. global fpustate, and then the one from RTLinux.

Jan


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