On Tue, 14 Jun 2022 09:28:14 -0700, Dixit, Ashutosh wrote:
> On Thu, 02 Jun 2022 10:21:19 -0700, Zhanjun Dong wrote:
>
> > @@ -481,12 +481,14 @@ static int wait_for_ct_request_update(struct
> > ct_request *req, u32 *status)
> > #define GUC_CTB_RESPONSE_TIMEOUT_SHORT_MS 10
> > #define
Thanks for all comments, I will update code and prepare for next version.
Regards,
Zhanjun
-Original Message-
From: Dixit, Ashutosh
Sent: June 14, 2022 12:28 PM
To: Dong, Zhanjun
Cc: intel-gfx@lists.freedesktop.org; dri-de...@lists.freedesktop.org; Teres
Alexis, Alan Previn ;
On Thu, 02 Jun 2022 10:21:19 -0700, Zhanjun Dong wrote:
>
Hi Zhanjun,
> We are seeing error message of "No response for request". Some cases happened
> while waiting for response and reset/suspend action was triggered. In this
> case, no response is not an error, active requests will be
On Thu, 02 Jun 2022, Zhanjun Dong wrote:
> We are seeing error message of "No response for request". Some cases happened
> while waiting for response and reset/suspend action was triggered. In this
> case, no response is not an error, active requests will be cancelled.
>
> This patch will handle
On 02.06.2022 19:21, Zhanjun Dong wrote:
> We are seeing error message of "No response for request". Some cases happened
> while waiting for response and reset/suspend action was triggered. In this
> case, no response is not an error, active requests will be cancelled.
>
> This patch will
Can't see anything wrong with this.
I consider this only a NIT, so feel : not sure if -ECANCELLED is reflective of
the "ct service being temporarily down"
as opposed to the "requester cancelling". Perhaps a -EPIPE or -EAGAIN (if we
got this far, we know we are probably mid-
reset) ?? (if not
We are seeing error message of "No response for request". Some cases happened
while waiting for response and reset/suspend action was triggered. In this
case, no response is not an error, active requests will be cancelled.
This patch will handle this condition and change the error message into
