Re: RTEMS | testsuites/validation: Fix interrupt validation assumptions (!1254)

[SHIVAM DEOLANKAR (@D3athSkulll)]

SHIVAM DEOLANKAR commented: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1254#note_150669


Use following config for the below testing.

```ini
[DEFAULT]
RTEMS_POSIX_API = True
RTEMS_DEBUG = True
BUILD_TESTS = True
BUILD_SAMPLES=True
[riscv/rv64imafdc]
```

Before: `ts-validation-intr.exe` failed with 127 failures in 
`RtemsIntrReqSetPriority` and 32 failures in `RtemsIntrReqVectorIsEnabled` due 
to some BSP-specific interrupt assumptions in the `tc-intr-set-priority.c `and 
`tc-intr-vector-is-enabled.c` .

![image.png](/uploads/b73b227cda4d9054d50b633acdd3818b/image.png){width=900 
height=586}

![image.png](/uploads/fe146d34d0739cc2d3c7a6b0fc05d16f/image.png){width=900 
height=596}

![image.png](/uploads/3cfbc44a08c20b8ee31e806b498fe43f/image.png){width=900 
height=486}

After Fix: Test compiled successfully and all failures in 
`RtemsIntrReqSetPriority` and `RtemsIntrReqVectorIsEnabled` were resolved.

![image.png](/uploads/db5eaba99556d80552102a88bf43dc34/image.png){width=900 
height=408}

Updated `tc-intr-set-priority.c` to avoid assuming `UINT32_MAX` is always 
invalid. 

Updated `tc-intr-vector-is-enabled.c` to remove assumption about automatic 
interrupt vector enabling after handler installation.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1254#note_150669
You're receiving this email because of your account on gitlab.rtems.org.



_______________________________________________
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs