[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250526090117.80593-1-ryasuoka@redhat.com>
Date: Mon, 26 May 2025 18:01:04 +0900
From: Ryosuke Yasuoka <ryasuoka@...hat.com>
To: drawat.floss@...il.com,
maarten.lankhorst@...ux.intel.com,
mripard@...nel.org,
tzimmermann@...e.de,
airlied@...il.com,
simona@...ll.ch,
jfalempe@...hat.com
Cc: Ryosuke Yasuoka <ryasuoka@...hat.com>,
linux-hyperv@...r.kernel.org,
linux-kernel@...r.kernel.org,
dri-devel@...ts.freedesktop.org
Subject: [PATCH RFC drm-misc-next v2 0/1] Add support for drm_panic
This patch adds drm_panic support for hyperv-drm driver. This function
works but it's still needed to brush up. Let me hear your opinions.
Once kernel panic occurs we expect to see a panic screen. However, to
see the screen, I need to close/re-open the graphic console client
window. As the panic screen shows correctly in the small preview
window in Hyper-V manager and debugfs API for drm_panic works correctly,
I think kernel needs to send signal to Hyper-V host that the console
client refreshes, but I have no idea what kind of signal is needed.
This patch is tested on Hyper-V 2022.
v2:
- Re-write codes with regular atomic helper. The driver was implemented
with simple KMS. So replace it with regular atomic helper in [1],
implement this feature on it.
[1] https://lore.kernel.org/all/20250427101825.812766-1-ryasuoka@redhat.com/
v1:
https://lore.kernel.org/lkml/20250402084351.1545536-1-ryasuoka@redhat.com/
Ryosuke Yasuoka (1):
drm/hyperv: Add support for drm_panic
drivers/gpu/drm/hyperv/hyperv_drm_modeset.c | 36 +++++++++++++++++++++
1 file changed, 36 insertions(+)
base-commit: c06cb85ad1412c6ff34792b028b2f89495761398
--
2.49.0
Powered by blists - more mailing lists