From: Thomas Zimmermann <tzimmermann@suse.de>
To: simona@ffwll.ch, airlied@gmail.com, alexander.deucher@amd.com,
christian.koenig@amd.com, lyude@redhat.com, dakr@kernel.org,
deller@gmx.de, mripard@kernel.org,
maarten.lankhorst@linux.intel.com, jason.wessel@windriver.com,
danielt@kernel.org, dianders@chromium.org
Cc: dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
nouveau@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] drm: Remove remaining support for kdb
Date: Tue, 25 Nov 2025 14:10:55 +0100 [thread overview]
Message-ID: <d1decb2e-ce22-47db-9e17-2492364e5886@suse.de> (raw)
In-Reply-To: <20251125130634.1080966-1-tzimmermann@suse.de>
Am 25.11.25 um 13:52 schrieb Thomas Zimmermann:
> Remove the rest of the kbd support from DRM. Driver support has been
s/kbd/kdb/g as in 'kernel debugger'
> broken for years without anyone complaining.
>
> Kdb cannot use regular DRM mode setting, so DRM drivers have to
> implement an additional hook to make it work (in theory). As outlined
> by Sima in commit 9c79e0b1d096 ("drm/fb-helper: Give up on kgdb for
> atomic drivers") from 2017, kdb is not compatible with DRM atomic mode
> setting. Non-atomic mode setting meanwhile has become rare.
>
> Only 3 DRM drivers implement the hooks for kdb support. Amdgpu and
> nouveau use non-atomic mode setting on older devices. But both drivers
> have switched to generic fbdev emulation, which isn't compatible with
> kdb. Radeon still runs kdb, but it doesn't work in practice. See the
> commits in this series for details
>
> Therefore remove the remaining support for kdb from the DRM drivers
> and from DRM fbdev emulation. Also remove the hooks from fbdev, as
> there are no fbdev drivers with kdb support.
>
> If we ever want to address kdb support within DRM drivers, a place to
> start would be the scanout buffers used by DRM's panic screen. These
> use the current display mode. They can be written and flushed without
> mode setting involved.
>
> Note: kdb over serial lines is not affected by this series and continues
> to work as before.
>
> Thomas Zimmermann (5):
> drm/amdgpu: Do not implement mode_set_base_atomic callback
> drm/nouveau: Do not implement mode_set_base_atomic callback
> drm/radeon: Do not implement mode_set_base_atomic callback
> drm/fbdev-helper: Remove drm_fb_helper_debug_enter/_leave()
> fbcon: Remove fb_debug_enter/_leave from struct fb_ops
>
> Documentation/process/debugging/kgdb.rst | 28 -----
> drivers/gpu/drm/amd/amdgpu/dce_v10_0.c | 35 ++-----
> drivers/gpu/drm/amd/amdgpu/dce_v6_0.c | 35 ++-----
> drivers/gpu/drm/amd/amdgpu/dce_v8_0.c | 35 ++-----
> drivers/gpu/drm/drm_fb_helper.c | 108 --------------------
> drivers/gpu/drm/nouveau/dispnv04/crtc.c | 24 +----
> drivers/gpu/drm/radeon/atombios_crtc.c | 74 ++++----------
> drivers/gpu/drm/radeon/radeon_legacy_crtc.c | 23 ++---
> drivers/gpu/drm/radeon/radeon_mode.h | 10 +-
> drivers/video/fbdev/core/fbcon.c | 24 -----
> drivers/video/fbdev/core/fbcon.h | 1 -
> include/drm/drm_fb_helper.h | 21 ----
> include/drm/drm_modeset_helper_vtables.h | 23 -----
> include/linux/fb.h | 4 -
> 14 files changed, 63 insertions(+), 382 deletions(-)
>
>
> base-commit: 0a21e96e0b6840d2a4e0b45a957679eeddeb4362
--
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstr. 146, 90461 Nürnberg, Germany, www.suse.com
GF: Jochen Jaser, Andrew McDonald, Werner Knoblich, (HRB 36809, AG Nürnberg)
next prev parent reply other threads:[~2025-11-25 13:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 12:52 [PATCH 0/5] drm: Remove remaining support for kdb Thomas Zimmermann
2025-11-25 12:52 ` [PATCH 1/5] drm/amdgpu: Do not implement mode_set_base_atomic callback Thomas Zimmermann
2025-11-25 12:52 ` [PATCH 2/5] drm/nouveau: " Thomas Zimmermann
2025-11-26 23:07 ` Lyude Paul
2025-11-25 12:52 ` [PATCH 3/5] drm/radeon: " Thomas Zimmermann
2025-11-25 12:52 ` [PATCH 4/5] drm/fbdev-helper: Remove drm_fb_helper_debug_enter/_leave() Thomas Zimmermann
2025-11-25 12:52 ` [PATCH 5/5] fbcon: Remove fb_debug_enter/_leave from struct fb_ops Thomas Zimmermann
2025-11-25 13:10 ` Thomas Zimmermann [this message]
2025-11-25 13:16 ` [PATCH 0/5] drm: Remove remaining support for kdb Christian König
2025-11-25 14:24 ` Thomas Zimmermann
2025-11-25 15:26 ` Doug Anderson
2025-11-25 16:22 ` Thomas Zimmermann
2025-11-26 12:19 ` Daniel Thompson
2025-11-26 13:32 ` Thomas Zimmermann
2025-11-26 14:20 ` Daniel Thompson
2025-11-25 16:25 ` Maarten Lankhorst
2025-11-26 7:44 ` Thomas Zimmermann
2025-12-01 16:41 ` Thomas Zimmermann
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=d1decb2e-ce22-47db-9e17-2492364e5886@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dakr@kernel.org \
--cc=danielt@kernel.org \
--cc=deller@gmx.de \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jason.wessel@windriver.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=simona@ffwll.ch \
/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;
as well as URLs for NNTP newsgroup(s).