From: Takashi Iwai <tiwai@suse.de>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: dri-devel <dri-devel@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Herrmann <dh.herrmann@gmail.com>
Subject: Re: Atomicity in KMS panic notifier
Date: Mon, 05 May 2014 17:04:57 +0200 [thread overview]
Message-ID: <s5h8uqgfequ.wl%tiwai@suse.de> (raw)
In-Reply-To: <CAKMK7uGD5JCQSfk+Vuf=qrjU9x+Y+-W3o-xyGyTM_BreR_XZcw@mail.gmail.com>
At Mon, 5 May 2014 16:52:45 +0200,
Daniel Vetter wrote:
>
> On Mon, May 5, 2014 at 4:48 PM, Takashi Iwai <tiwai@suse.de> wrote:
> >
> > The current problem I see is that the rest of panic notifier chain
> > won't be called once when we hit the problem in KMS notifier. So,
> > this bug in KMS influences on the rest panic behavior.
> >
> > Maybe a hackish solution would be to keep KMS notifier at the end of
> > notifier chain so that it crashes at last. I don't like this either,
> > but...
>
> You need to do that with both the kms panic notifier in
> drm_fb_helper.c and with the fbcon panic notifier. And iirc there's
> also a console->unblank call somewhere which _also_ can end up in
> ->set_par. But I'm not sure anymore when exactly that one is run, I've
> tried hard to forget this all ;-)
Oh well, you're suggesting the need for Propranolol overdose ;)
Takashi
next prev parent reply other threads:[~2014-05-05 15:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 13:02 Takashi Iwai
2014-05-05 14:29 ` Daniel Vetter
2014-05-05 14:48 ` Takashi Iwai
2014-05-05 14:52 ` Daniel Vetter
2014-05-05 15:04 ` Takashi Iwai [this message]
2014-05-06 13:27 ` Takashi Iwai
2014-05-06 13:32 ` David Herrmann
2014-05-06 13:38 ` Takashi Iwai
2014-05-06 13:53 ` David Herrmann
2014-05-06 14:07 ` Takashi Iwai
2014-05-07 16:15 ` One Thousand Gnomes
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=s5h8uqgfequ.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=daniel@ffwll.ch \
--cc=dh.herrmann@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
/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®