On Fri 26 May 16:51 PDT 2017, Sarangdhar Joshi wrote:
> In the context of recovering from crash, rproc_trigger_recovery() does
> rproc_shutdown() followed by rproc_boot(). The remoteproc resources are
> cleaned up in rproc_shutdown() and immediately reallocated in
> rproc_boot() which is an unnecessary overhead. Furthermore, we want the
> memory regions to be accessible after stopping the remote processor, to
> be able to extract the memory content for a coredump.
>
> This patch factors out the code in rproc_boot() and rproc_shutdown()
> path and introduces rproc_{start,stop}() in order to avoid resource
> allocation overhead.
>
> Signed-off-by: Sarangdhar Joshi <spjoshi@xxxxxxxxxxxxxx>
Both patches applied.
Thanks,
Bjorn
--
To unsubscribe from this list: send the line "unsubscribe linux-remoteproc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
