On 13.06.2024 14:22, Andrew Davis wrote:
We looked into this some time ago, and noticed that the IRQ approach
caused problems in the virtio/rpmsg code. I'd like to understand if
your change was for the same reason, or something else we missed before.
It is most likely the same reason. Seems despite its name,
rproc_vq_interrupt() cannot
be called from an IRQ/atomic context. As the following backtrace shows,
that function
calls down into functions which are not IRQ safe. So we needed to keep
it threaded:
Thanks for confirming. This is exactly what we've been seeing.
Regards,
Dominic
