From: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
To: Jocelyn Falempe <jfalempe@redhat.com>,
Michael Kelley <mhklinux@outlook.com>,
John Ogness <john.ogness@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Daniel Vetter <daniel@ffwll.ch>,
Andrew Morton <akpm@linux-foundation.org>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
Lukas Wunner <lukas@wunner.de>, Uros Bizjak <ubizjak@gmail.com>,
Petr Mladek <pmladek@suse.com>,
Daniel Thompson <daniel.thompson@linaro.org>,
Douglas Anderson <dianders@chromium.org>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
David Airlie <airlied@redhat.com>,
Thomas Zimmermann <tzimmermann@suse.de>
Subject: Re: [RFC] How to test panic handlers, without crashing the kernel
Date: Thu, 7 Mar 2024 14:30:05 -0300 [thread overview]
Message-ID: <0f8e9c87-ab40-fe49-da2c-fdcfdc9deeae@igalia.com> (raw)
In-Reply-To: <adeac189-87f8-4b70-9c04-3eaaf2ed7bc5@redhat.com>
On 07/03/2024 14:22, Jocelyn Falempe wrote:
> [...]
>
> For drm_panic, I changed the way the debugfs is calling the drm_panic
> functions in the last version:
> https://patchwork.freedesktop.org/patch/581845/?series=122244&rev=9
>
> It doesn't use the panic notifier list, but create a file for each plane
> of each device directly.
> It allows to test the panic handler, not in a real panic condition, but
> that's still better than nothing.
>
Nice! Seems a very good idea, at least as a first step to unblock the
work you're doing.
Thanks again for the effort, much appreciated =)
next prev parent reply other threads:[~2024-03-07 17:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 11:14 Jocelyn Falempe
2024-03-04 21:12 ` John Ogness
2024-03-04 21:43 ` Guilherme G. Piccoli
2024-03-05 16:23 ` Michael Kelley
2024-03-05 16:52 ` Jocelyn Falempe
2024-03-05 17:50 ` Guilherme G. Piccoli
2024-03-07 17:22 ` Jocelyn Falempe
2024-03-07 17:30 ` Guilherme G. Piccoli [this message]
2024-03-05 16:31 ` 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=0f8e9c87-ab40-fe49-da2c-fdcfdc9deeae@igalia.com \
--to=gpiccoli@igalia.com \
--cc=airlied@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=daniel.thompson@linaro.org \
--cc=daniel@ffwll.ch \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jfalempe@redhat.com \
--cc=john.ogness@linutronix.de \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mhklinux@outlook.com \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=tzimmermann@suse.de \
--cc=ubizjak@gmail.com \
--cc=wangkefeng.wang@huawei.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
all inboxes | Powered by JetHome®