On Fri 10 Jan 13:28 PST 2020, Mathieu Poirier wrote:
> On Thu, Dec 26, 2019 at 09:32:14PM -0800, Bjorn Andersson wrote:
> > Add a common panic handler that invokes a stop request and sleep enough
> > to let the remoteproc flush it's caches etc in order to aid post mortem
> > debugging.
> >
> > Signed-off-by: Bjorn Andersson <bjorn.andersson@xxxxxxxxxx>
> > ---
> >
> > Changes since v1:
> > - None
> >
> > drivers/remoteproc/qcom_q6v5.c | 19 +++++++++++++++++++
> > drivers/remoteproc/qcom_q6v5.h | 1 +
> > 2 files changed, 20 insertions(+)
> >
> > diff --git a/drivers/remoteproc/qcom_q6v5.c b/drivers/remoteproc/qcom_q6v5.c
> > index cb0f4a0be032..17167c980e02 100644
> > --- a/drivers/remoteproc/qcom_q6v5.c
> > +++ b/drivers/remoteproc/qcom_q6v5.c
> > @@ -6,6 +6,7 @@
> > * Copyright (C) 2014 Sony Mobile Communications AB
> > * Copyright (c) 2012-2013, The Linux Foundation. All rights reserved.
> > */
> > +#include <linux/delay.h>
> > #include <linux/kernel.h>
> > #include <linux/platform_device.h>
> > #include <linux/interrupt.h>
> > @@ -15,6 +16,8 @@
> > #include <linux/remoteproc.h>
> > #include "qcom_q6v5.h"
> >
> > +#define Q6V5_PANIC_DELAY_MS 200
> > +
> > /**
> > * qcom_q6v5_prepare() - reinitialize the qcom_q6v5 context before start
> > * @q6v5: reference to qcom_q6v5 context to be reinitialized
> > @@ -162,6 +165,22 @@ int qcom_q6v5_request_stop(struct qcom_q6v5 *q6v5)
> > }
> > EXPORT_SYMBOL_GPL(qcom_q6v5_request_stop);
> >
> > +/**
> > + * qcom_q6v5_panic() - panic handler to invoke a stop on the remote
> > + * @q6v5: reference to qcom_q6v5 context
> > + *
> > + * Set the stop bit and sleep in order to allow the remote processor to flush
> > + * its caches etc for post mortem debugging.
> > + */
> > +void qcom_q6v5_panic(struct qcom_q6v5 *q6v5)
> > +{
> > + qcom_smem_state_update_bits(q6v5->state,
> > + BIT(q6v5->stop_bit), BIT(q6v5->stop_bit));
> > +
> > + mdelay(Q6V5_PANIC_DELAY_MS);
>
> I really wonder if the delay should be part of the remoteproc core and
> configurable via device tree. Wanting the remote processor to flush its caches
> is likely something other vendors will want when dealing with a kernel panic.
> It would be nice to see if other people have an opinion on this topic. If not
> then we can keep the delay here and move it to the core if need be.
>
I gave this some more thought and what we're trying to achieve is to
signal the remote processors about the panic and then give them time to
react, but per the proposal (and Qualcomm downstream iirc) we will do
this for each remote processor, one by one.
So in the typical case of a Qualcomm platform with 4-5 remoteprocs we'll
end up giving the first one a whole second to react and the last one
"only" 200ms.
Moving the delay to the core by iterating over rproc_list calling
panic() and then delaying would be cleaner imo.
It might be nice to make this configurable in DT, but I agree that it
would be nice to hear from others if this would be useful.
Regards,
Bjorn
> Thanks,
> Mathieu
>
> > +}
> > +EXPORT_SYMBOL_GPL(qcom_q6v5_panic);
> > +
> > /**
> > * qcom_q6v5_init() - initializer of the q6v5 common struct
> > * @q6v5: handle to be initialized
> > diff --git a/drivers/remoteproc/qcom_q6v5.h b/drivers/remoteproc/qcom_q6v5.h
> > index 7ac92c1e0f49..c37e6fd063e4 100644
> > --- a/drivers/remoteproc/qcom_q6v5.h
> > +++ b/drivers/remoteproc/qcom_q6v5.h
> > @@ -42,5 +42,6 @@ int qcom_q6v5_prepare(struct qcom_q6v5 *q6v5);
> > int qcom_q6v5_unprepare(struct qcom_q6v5 *q6v5);
> > int qcom_q6v5_request_stop(struct qcom_q6v5 *q6v5);
> > int qcom_q6v5_wait_for_start(struct qcom_q6v5 *q6v5, int timeout);
> > +void qcom_q6v5_panic(struct qcom_q6v5 *q6v5);
> >
> > #endif
> > --
> > 2.24.0
> >
