Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: Jocelyn Falempe <jfalempe@redhat.com>,
	javierm@redhat.com, airlied@gmail.com, simona@ffwll.ch,
	maarten.lankhorst@linux.intel.com, mripard@kernel.org
Cc: dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org,
	amd-gfx@lists.freedesktop.org, rust-for-linux@vger.kernel.org,
	linux-hyperv@vger.kernel.org, intel-gfx@lists.freedesktop.org,
	intel-xe@lists.freedesktop.org, imx@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org,
	nouveau@lists.freedesktop.org, linux-renesas-soc@vger.kernel.org,
	virtualization@lists.linux.dev, sashiko-reviews@lists.linux.dev
Subject: Re: [PATCH 00/12] drm/panic: Split into core and helpers
Date: Fri, 21 Aug 2026 08:38:43 +0200	[thread overview]
Message-ID: <3d0d14e6-05d2-4fc4-befe-e1d0cafc91db@suse.de> (raw)
In-Reply-To: <e4da5ba4-9a02-4080-9a83-19d401017910@redhat.com>

Hi Jocelyn

Am 20.08.26 um 19:49 schrieb Jocelyn Falempe:
> On 18/08/2026 14:27, Thomas Zimmermann wrote:
>> Split DRM's current panic handling into a core and a helper module.
>> The core is still part of DRM's core library. The panic helpers are
>> part of DRM's KMS helper module (for now).
>>
>> The motivation behind this series is to get panic handling's drawing
>> code out of the DRM core. At some point it should share a single
>> module with DRM's other drawing and format conversion.
>>
>> With the series applied, panic hanlding follows DRM's established
>> design pattern of having a DRM core interface with an dedicated
>> implementation in each driver. Drivers share common code in helper
>> modules. For panic handling, the DRM core still contains the panic
>> entry points, the parameters and the debugfs interface. All drawing
>> is now located in the panic helpers.
>>
>> Patches 1 to 4 improve several issues in the current panic code. It
>> makes sense to fix them before moving the core around.
>>
>> Patches 5 to 8 put handling of all panic state and locking into a
>> single place, drm_panic_display_panic_screen(). It is maintained by
>> panic handling's DRM core code. This also enables the test cases to
>> work more independently from the kernel's configuration.
>>
>> Patches 9 to 11 split the panic-handling code into the core and panic
>> helpers. The former maintain all state, locking and public interfaces.
>> The latter handles drawing and details of the involved framebuffers.
>>
>> DRM devices that offer panic handling provide a single callback, struct
>> drm_plane_funcs.display_panic_screen. A new initializer macro makes it
>> point to the existing panic-drawing implementation. Hence there's no
>> change in features or functionality. If panic handling is configured
>> off, it all clears out to NULL.
>>
>> Patch 12 reworks the test cases slighly, so that they can be build as
>> a separate module. Do 'modprobe drm_panic_helper_test' to run them.
>>
>> Tested under bochs with debugfs and test cases.
>
> Overall the series looks good to me, and I like the split between the 
> helper and the core.
> I would just drop the first two patches, as I don't see much 
> difference between static allocation or kmalloc() at init, and I think 
> that memset() the buffers to 0 is not useful in this case.

Ok. Geert also expressed a dislike for these changes.

I have a number of changes done from the Sashiko review and will post an 
update to the series early next week.

Thanks for reviewing.

Best regards
Thomas


>
> Best regards,
>

-- 
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstr. 146, 90461 Nürnberg, Germany, www.suse.com
GF: Jochen Jaser, Andrew McDonald, (HRB 36809, AG Nürnberg)




      reply	other threads:[~2026-08-21  6:40 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-18 12:27 [PATCH 00/12] drm/panic: Split into core and helpers Thomas Zimmermann
2026-08-18 12:27 ` [PATCH 01/12] drm/panic: Allocate QR-code buffers statically Thomas Zimmermann
2026-08-19  9:38   ` Geert Uytterhoeven
2026-08-19 10:45     ` Thomas Zimmermann
2026-08-18 12:28 ` [PATCH 02/12] drm/panic: Make allocation of zlib workspace more robust Thomas Zimmermann
2026-08-18 12:28 ` [PATCH 03/12] drm/panic: Return -EINVAL if font is not available Thomas Zimmermann
2026-08-20 17:04   ` Jocelyn Falempe
2026-08-18 12:28 ` [PATCH 04/12] drm/panic: Return errno codes if panic output fails Thomas Zimmermann
2026-08-20 17:05   ` Jocelyn Falempe
2026-08-18 12:28 ` [PATCH 05/12] drm/panic: Pass colors to draw_panic_dispatch() Thomas Zimmermann
2026-08-20 17:08   ` Jocelyn Falempe
2026-08-18 12:28 ` [PATCH 06/12] drm/panic: Pass global module parameters to drm_panic_dispatch() Thomas Zimmermann
2026-08-20 17:10   ` Jocelyn Falempe
2026-08-18 12:28 ` [PATCH 07/12] drm/panic: Retry in dispatch function if panic output fails Thomas Zimmermann
2026-08-20 17:12   ` Jocelyn Falempe
2026-08-20 17:15   ` Jocelyn Falempe
2026-08-18 12:28 ` [PATCH 08/12] drm/panic: Split draw_panic_plane() Thomas Zimmermann
2026-08-18 12:28 ` [PATCH 09/12] drm/panic: Display panic screen via per-plane callback Thomas Zimmermann
2026-08-20 17:25   ` Jocelyn Falempe
2026-08-18 12:28 ` [PATCH 10/12] drm/panic: Internalize panic locking in DRM core and helpers Thomas Zimmermann
2026-08-18 12:28 ` [PATCH 11/12] drm/panic: Move panic display code into helper library Thomas Zimmermann
2026-08-18 15:55   ` Randy Dunlap
2026-08-19  6:16     ` Thomas Zimmermann
2026-08-18 12:28 ` [PATCH 12/12] drm/panic: Compile KUnit tests as module Thomas Zimmermann
2026-08-20 17:49 ` [PATCH 00/12] drm/panic: Split into core and helpers Jocelyn Falempe
2026-08-21  6:38   ` Thomas Zimmermann [this message]

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=3d0d14e6-05d2-4fc4-befe-e1d0cafc91db@suse.de \
    --to=tzimmermann@suse.de \
    --cc=airlied@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=imx@lists.linux.dev \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=javierm@redhat.com \
    --cc=jfalempe@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=nouveau@lists.freedesktop.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=simona@ffwll.ch \
    --cc=virtualization@lists.linux.dev \
    /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