All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dawid Osuchowski <dawid.osuchowski@linux.intel.com>
To: Karol Wachowski <karol.wachowski@linux.intel.com>,
	dri-devel@lists.freedesktop.org
Cc: oded.gabbay@gmail.com, jeff.hugo@oss.qualcomm.com,
	lizhi.hou@amd.com, andrzej.kacprowski@linux.intel.com,
	Jakub Pawlak <jakub.pawlak@intel.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH v2] accel/ivpu: Use separate flag for job timeout
Date: Mon, 21 Sep 2026 16:56:22 +0200	[thread overview]
Message-ID: <ac09bf4a-2b65-421a-a5f6-87c5a89ba734@linux.intel.com> (raw)
In-Reply-To: <20260914084301.894028-1-karol.wachowski@linux.intel.com>

On 2026-09-14 10:43 AM, Karol Wachowski wrote:
> From: Jakub Pawlak <jakub.pawlak@intel.com>
> 
> Use separate flag to mark a job timeout as a reason
> of starting context_abort_work. This allows to distinguish
> engine reset reason and clearly adjust reset procedure flow.
> 
> The flag is cleared in ivpu_prepare_for_reset(), which every
> recovery and suspend path already funnels through, so that the
> state is clean after recovery.
> 
> Cc: <stable@vger.kernel.org> # v7.1+
> Fixes: ade00a6c903f ("accel/ivpu: Perform engine reset instead of device recovery on TDR")

Reviewed-by: Dawid Osuchowski <dawid.osuchowski@linux.intel.com>

> Signed-off-by: Jakub Pawlak <jakub.pawlak@intel.com>
> Signed-off-by: Karol Wachowski <karol.wachowski@linux.intel.com>
> ---
> Changes in v2:
>   - add Cc: tag
>   - link to v1: https://lore.kernel.org/dri-devel/20260914082800.892044-1-karol.wachowski@linux.intel.com/T/#u
> ---
>   drivers/accel/ivpu/ivpu_drv.c | 3 ++-
>   drivers/accel/ivpu/ivpu_drv.h | 2 +-
>   drivers/accel/ivpu/ivpu_job.c | 7 +++----
>   drivers/accel/ivpu/ivpu_mmu.c | 1 -
>   drivers/accel/ivpu/ivpu_pm.c  | 1 +
>   5 files changed, 7 insertions(+), 7 deletions(-)



  parent reply	other threads:[~2026-09-21 15:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14  8:43 [PATCH v2] accel/ivpu: Use separate flag for job timeout Karol Wachowski
2026-09-14  8:58 ` sashiko-bot
2026-09-21 14:50   ` Wachowski, Karol
2026-09-21 14:56 ` Dawid Osuchowski [this message]
2026-09-22  6:02   ` Wachowski, Karol

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ac09bf4a-2b65-421a-a5f6-87c5a89ba734@linux.intel.com \
    --to=dawid.osuchowski@linux.intel.com \
    --cc=andrzej.kacprowski@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jakub.pawlak@intel.com \
    --cc=jeff.hugo@oss.qualcomm.com \
    --cc=karol.wachowski@linux.intel.com \
    --cc=lizhi.hou@amd.com \
    --cc=oded.gabbay@gmail.com \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.