From: Thomas Zimmermann <tzimmermann@suse.de>
To: jfalempe@redhat.com, javierm@redhat.com, simona@ffwll.ch,
airlied@gmail.com, mripard@kernel.org,
maarten.lankhorst@linux.intel.com, gregkh@linuxfoundation.org,
jirislaby@kernel.org
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org,
Thomas Zimmermann <tzimmermann@suse.de>
Subject: [PATCH 0/3] drm/client: Wire up sysrq for all clients and update drm_log
Date: Fri, 7 Nov 2025 15:19:24 +0100 [thread overview]
Message-ID: <20251107142612.467817-1-tzimmermann@suse.de> (raw)
DRM's fbdev emulation has long supported SysRq+v to bring up the
framebuffer console for emergency output. Wire up sysrq for all
DRM clients and make it work with drm_log.
Patch 1 and 2 set up DRM client functionality for sysrq. The patches
adopt existing conventions from fbdev emulation, so that there's no
visible change to users. Invoke SysRq+v to bring up the in-kernel DRM
client.
Patch 3 adds restore functionality to drm_log. This enables SysRq, but
also brings back drm_log when the user-space releases control of the
display.
Tested on amdgpu and bochs.
Thomas Zimmermann (3):
drm/client: Pass force parameter to client restore
drm/client: Support emergency restore via sysrq for all clients
drm/client: log: Implement struct drm_client_funcs.restore
drivers/gpu/drm/Makefile | 3 +-
drivers/gpu/drm/clients/drm_fbdev_client.c | 6 +-
drivers/gpu/drm/clients/drm_log.c | 13 ++++
drivers/gpu/drm/drm_client.c | 1 +
drivers/gpu/drm/drm_client_event.c | 4 +-
drivers/gpu/drm/drm_client_sysrq.c | 65 ++++++++++++++++++++
drivers/gpu/drm/drm_drv.c | 3 +
drivers/gpu/drm/drm_fb_helper.c | 69 +++-------------------
drivers/gpu/drm/drm_file.c | 2 +-
drivers/gpu/drm/drm_internal.h | 11 ++++
include/drm/drm_client.h | 8 ++-
include/drm/drm_client_event.h | 4 +-
include/drm/drm_device.h | 8 +++
include/drm/drm_fb_helper.h | 8 +--
14 files changed, 126 insertions(+), 79 deletions(-)
create mode 100644 drivers/gpu/drm/drm_client_sysrq.c
--
2.51.1
next reply other threads:[~2025-11-07 14:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 14:19 Thomas Zimmermann [this message]
2025-11-07 14:19 ` [PATCH 1/3] drm/client: Pass force parameter to client restore Thomas Zimmermann
2025-11-10 14:02 ` Jocelyn Falempe
2025-11-07 14:19 ` [PATCH 2/3] drm/client: Support emergency restore via sysrq for all clients Thomas Zimmermann
2025-11-10 11:29 ` kernel test robot
2025-11-10 12:12 ` kernel test robot
2025-11-10 13:47 ` kernel test robot
2025-11-07 14:19 ` [PATCH 3/3] drm/client: log: Implement struct drm_client_funcs.restore Thomas Zimmermann
2025-11-10 14:05 ` Jocelyn Falempe
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=20251107142612.467817-1-tzimmermann@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=javierm@redhat.com \
--cc=jfalempe@redhat.com \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.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