From: Ryosuke Yasuoka <ryasuoka@redhat.com>
To: zack.rusin@broadcom.com, maarten.lankhorst@linux.intel.com,
mripard@kernel.org, tzimmermann@suse.de, airlied@gmail.com,
simona@ffwll.ch, ian.forbes@broadcom.com, jfalempe@redhat.com
Cc: Ryosuke Yasuoka <ryasuoka@redhat.com>,
bcm-kernel-feedback-list@broadcom.com,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: [PATCH drm-misc-next v2 0/1] add drm_panic_support for vmwgfx-stdu
Date: Mon, 8 Sep 2025 23:11:33 +0900 [thread overview]
Message-ID: <20250908141152.221291-1-ryasuoka@redhat.com> (raw)
Add drm_panic support for stdu in vmwgfx. This patch was tested in
a VM with VMSVGA on Virtual Box.
I got 2 type of suggestions from reviewers:
1. Write the panic screen to guest_memory_bo and send dirty/flush
command
2. Write it to VRAM directly and then switch back to legacy mode
Since option 2 is simpler than another one and ldu might be able
to re-use some codes if ldu supports drm_panic, I re-write this
v2 patch with option 2.
Ryosuke Yasuoka (1):
drm/vmwgfx: add drm_panic support for stdu
drivers/gpu/drm/vmwgfx/vmwgfx_cmd.c | 73 ++++++++++++++++++++++++++++
drivers/gpu/drm/vmwgfx/vmwgfx_drv.h | 18 +++++++
drivers/gpu/drm/vmwgfx/vmwgfx_kms.c | 9 ++++
drivers/gpu/drm/vmwgfx/vmwgfx_kms.h | 1 +
drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c | 43 ++++++++++++++++
drivers/gpu/drm/vmwgfx/vmwgfx_stdu.c | 34 +++++++++++++
6 files changed, 178 insertions(+)
base-commit: 306c8959b5fdfdc3900aebe4e56257a349f5765f
--
2.51.0
next reply other threads:[~2025-09-08 14:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 14:11 Ryosuke Yasuoka [this message]
2025-09-08 14:11 ` [PATCH drm-misc-next v2 1/1] drm/vmwgfx: add drm_panic support for stdu Ryosuke Yasuoka
2025-09-09 20:48 ` Ian Forbes
2025-09-10 11:17 ` Ryosuke Yasuoka
2025-09-09 0:32 ` [PATCH drm-misc-next v2 0/1] add drm_panic_support for vmwgfx-stdu Ryosuke Yasuoka
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=20250908141152.221291-1-ryasuoka@redhat.com \
--to=ryasuoka@redhat.com \
--cc=airlied@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=ian.forbes@broadcom.com \
--cc=jfalempe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=zack.rusin@broadcom.com \
/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