From: Ryosuke Yasuoka <ryasuoka@redhat.com>
To: maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@gmail.com, simona@ffwll.ch,
drawat.floss@gmail.com, jfalempe@redhat.com
Cc: Ryosuke Yasuoka <ryasuoka@redhat.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-hyperv@vger.kernel.org
Subject: [PATCH RFC drm-next 0/1] Add support for drm_panic
Date: Wed, 2 Apr 2025 17:43:48 +0900 [thread overview]
Message-ID: <20250402084351.1545536-1-ryasuoka@redhat.com> (raw)
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.
Ryosuke Yasuoka (1):
drm/hyperv: Add support for drm_panic
drivers/gpu/drm/drm_simple_kms_helper.c | 26 +++++++++++++
drivers/gpu/drm/hyperv/hyperv_drm_modeset.c | 42 +++++++++++++++++++++
include/drm/drm_simple_kms_helper.h | 22 +++++++++++
3 files changed, 90 insertions(+)
base-commit: cf05922d63e2ae6a9b1b52ff5236a44c3b29f78c
--
2.48.1
next reply other threads:[~2025-04-02 8:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 8:43 Ryosuke Yasuoka [this message]
2025-04-02 8:43 ` [PATCH RFC drm-next 1/1] drm/hyperv: Add support for drm_panic Ryosuke Yasuoka
2025-04-02 9:45 ` [PATCH RFC drm-next 0/1] " Thomas Zimmermann
2025-04-02 13:52 ` Ryosuke Yasuoka
2025-04-03 7:23 ` 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=20250402084351.1545536-1-ryasuoka@redhat.com \
--to=ryasuoka@redhat.com \
--cc=airlied@gmail.com \
--cc=drawat.floss@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jfalempe@redhat.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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