The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Onur Özkan" <work@onurozkan.dev>
To: Daniel Almeida <daniel.almeida@collabora.com>
Cc: linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
	dri-devel@lists.freedesktop.org, dakr@kernel.org,
	aliceryhl@google.com, airlied@gmail.com, simona@ffwll.ch,
	ojeda@kernel.org, boqun@kernel.org, gary@garyguo.net,
	bjorn3_gh@protonmail.com, lossin@kernel.org,
	a.hindborg@kernel.org, tmgross@umich.edu
Subject: Re: [PATCH v6 2/3] drm/tyr: add GPU reset infrastructure
Date: Fri, 21 Aug 2026 19:42:30 +0300	[thread overview]
Message-ID: <20260821164232.1118419-1-work@onurozkan.dev> (raw)
In-Reply-To: <2AD43D0D-2B01-47E3-AACB-32032B3358C9@collabora.com>

On Fri, 21 Aug 2026 13:39:45 -0300
Daniel Almeida <daniel.almeida@collabora.com> wrote:

> 
> 
> > On 21 Aug 2026, at 12:58, Onur Özkan <work@onurozkan.dev> wrote:
> > 
> > On Fri, 21 Aug 2026 12:31:03 -0300
> > Daniel Almeida <daniel.almeida@collabora.com> wrote:
> > 
> >> Hi Onur,
> >> 
> >>> On 19 Aug 2026, at 15:45, Onur Özkan <work@onurozkan.dev> wrote:
> >>> 
> >>> Add support for scheduling GPU resets on a dedicated workqueue. Track
> >>> the reset state to avoid queueing another reset while one is already
> >>> pending or in progress.
> >>> 
> >>> Use an SRCU based gate with mutex-protected reader admission to block
> >>> hardware accesses while reset work runs and wait for current users
> >>> before resetting.
> >>> 
> >>> Stop new reset requests during teardown and drain any queued or running
> >>> reset work before releasing the device resources.
> >>> 
> >>> This is the initial reset infrastructure only. It is not wired to a reset
> >>> source yet as those will follow in separate work.
> >>> 
> >>> Link: https://gitlab.freedesktop.org/panfrost/linux/-/work_items/28
> >>> Signed-off-by: Onur Özkan <work@onurozkan.dev>
> >> 
> >> I’d use dev_info instead, I don’t think a reset belongs in dev_dbg.
> > 
> > It was dev_dbg initially, Danillo said otherwise and I changed it. I have no
> > strong feeling on both.
> > 
> 
> You mean it was dev_info initially?

Yeah, I wrote it incorrectly.

> 
> > Does it deserve a new version to switch back into dev_dbg again? I think we can
> > easily switch that when pulling this series.
> 
> My point is that resetting the GPU should not be a “debug” trace, but rather something
> that should hit dmesg unconditionally. Of all things that are printed on a driver, a 
> “hey the GPU is being reset because something crashed” is something that should
> always show up IMHO.
> 
> I don’t think you need to send a new version though, let’s wait for more feedback
> as well.
> 

Okay.

- Onur

> 
> — Daniel
> 

  reply	other threads:[~2026-08-21 16:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-19 18:45 [PATCH v6 0/3] drm/tyr: GPU reset infrastructure Onur Özkan
2026-08-19 18:45 ` [PATCH v6 1/3] drm/tyr: clear stale IRQ state before soft reset Onur Özkan
2026-08-19 18:45 ` [PATCH v6 2/3] drm/tyr: add GPU reset infrastructure Onur Özkan
2026-08-21 15:31   ` Daniel Almeida
2026-08-21 15:58     ` Onur Özkan
2026-08-21 16:12       ` Danilo Krummrich
2026-08-21 16:39       ` Daniel Almeida
2026-08-21 16:42         ` Onur Özkan [this message]
2026-08-21 17:01         ` Danilo Krummrich
2026-08-21 17:23           ` Daniel Almeida
2026-08-21 18:53             ` Danilo Krummrich
2026-08-19 18:45 ` [PATCH v6 3/3] drm/tyr: put iomem behind the hardware gate Onur Özkan

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=20260821164232.1118419-1-work@onurozkan.dev \
    --to=work@onurozkan.dev \
    --cc=a.hindborg@kernel.org \
    --cc=airlied@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun@kernel.org \
    --cc=dakr@kernel.org \
    --cc=daniel.almeida@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gary@garyguo.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=simona@ffwll.ch \
    --cc=tmgross@umich.edu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox