On Tue, Dec 10, 2024 at 8:11 AM spudaneco <spudan...@gmail.com> wrote:
> I wonder if we should also disable the prioritization APIs. In the > normal, default case, any reprioritization of an IRQ introduces a fatal, > mysterious bug. That is because nested interrupts will occur and may not > be supported.Sent from my Galaxy Aren't the prioritization APIs needed for setting up the Zero Latency Interrupts? They exist "outside" the OS so they don't touch any OS structures, so no mysterious bug should occur. Maybe the prioritization APIs should be enabled with CONFIG_ARCH_HIPRI_INTERRUPT? And the docstrings can explain not to use them for interrupts handled by the OS. Cheers, Nathan
