I believe this is also sometimes referred to as "deferred interrupt" servicing or handling, so it may be worth using that term to find candidates.
It is perhaps possible to 'fake' it by reserving the highest priority task levels for ISR servicing, so say you have 32 interrupt vectors, you would reserve priority levels 0 to 31 (assuming zero is high) for the ISR2 levels. Each real interrupt then simply sets an event flag signalling the ISR2 task. It remains your responsibility in this case not to call blocking functions in the ISR2 tasks, nut non-blocking kernel services can be used freely.
I am not sure whether this gives you exactly the same effect (I'd have to study it more fully than I have - or care to right now), but it does mean that you can do minimal work in the true ISR, and a true ISR will always preempt any ISR2.
发布评论
评论（1）
我相信这有时也被称为“延迟中断”服务或处理，因此可能值得使用该术语来寻找候选者。
也许可以通过为 ISR 服务保留最高优先级任务级别来“伪造”它，因此假设您有 32 个中断向量，您将为 ISR2 级别保留优先级 0 到 31（假设零为高）。每个实际中断只需设置一个事件标志来指示 ISR2 任务。在这种情况下，您有责任不要在 ISR2 任务中调用阻塞函数，坚果非阻塞内核服务可以自由使用。
我不确定这是否会给你带来完全相同的效果（我必须比我更全面地研究它 - 或者现在关心），但这确实意味着你可以在真正的 ISR 中做最少的工作，并且真正的 ISR 总是会抢占任何 ISR2。
I believe this is also sometimes referred to as "deferred interrupt" servicing or handling, so it may be worth using that term to find candidates.
It is perhaps possible to 'fake' it by reserving the highest priority task levels for ISR servicing, so say you have 32 interrupt vectors, you would reserve priority levels 0 to 31 (assuming zero is high) for the ISR2 levels. Each real interrupt then simply sets an event flag signalling the ISR2 task. It remains your responsibility in this case not to call blocking functions in the ISR2 tasks, nut non-blocking kernel services can be used freely.
I am not sure whether this gives you exactly the same effect (I'd have to study it more fully than I have - or care to right now), but it does mean that you can do minimal work in the true ISR, and a true ISR will always preempt any ISR2.