Sebastian Huber commented on a discussion: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1253#note_151514 Oh, yes. You surfaced some of the dirty corners of the testing infrastructure. For various tests, you need the ability to trigger a software interrupt or even two with different interrupt priorities so that they can nest. It is surprisingly difficult to trigger software interrupts for a large range of BSPs since not all provide this feature at the interrupt controller level. Sometimes the software interrupts provided by the interrupt controller have constraints making them useless for testing. So, this feature is provided by the BSP through the `<tm27.h>` header file. Right now the BSP provided header files are not visible for the cpukit build items. If we want to have the full testing support in librtemstest, then one option would be to add `${BSP_INCLUDES}` to the includes. A cleaner solution would be to define the API for this testing infrastructure in a cpukit `<rtems/test*.h>` header file and let the BSPs implement it. This would be a larger refactoring work. -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1253#note_151514 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
