dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: "Noralf Trønnes" <noralf@tronnes.org>,
	"David Herrmann" <dh.herrmann@gmail.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 0/3] drm: Add panic handling
Date: Wed, 5 Oct 2016 15:14:23 +0200	[thread overview]
Message-ID: <CAKMK7uFBxpHYUQF7EqvVuicehnbFi0Ff7HapO3Hed2RPZc-sHw@mail.gmail.com> (raw)
In-Reply-To: <f47bc999-4415-fa44-3f86-2a6049359f18@tronnes.org>

Needs review from David Herrmann, pls keep him on cc for anything
related to panic handling.
-Daniel

On Sun, Oct 2, 2016 at 3:47 PM, Noralf Trønnes <noralf@tronnes.org> wrote:
> Ping.
>
>
> Den 11.09.2016 20:47, skrev Noralf Trønnes:
>>
>> This patchset adds a way for DRM drivers to display kernel messages
>> during panic().
>>
>> This version have lots of changes based on Daniel's review of the RFC
>> where he proposed a different way of interacting with the driver.
>>
>> I have used this script to run some tests on the rendering code:
>> https://gist.github.com/notro/4f42ec20e1be1d47c98fa749ca53c805
>>
>>
>> Noralf.
>>
>>
>> Noralf Trønnes (3):
>>    drm: Add support for panic message output
>>    drm/fb_cma_helper: Add panic handling
>>    drm/simpledrm: Add panic handling
>>
>>   drivers/gpu/drm/Kconfig                   |   1 +
>>   drivers/gpu/drm/Makefile                  |   2 +-
>>   drivers/gpu/drm/drm_drv.c                 |   3 +
>>   drivers/gpu/drm/drm_fb_cma_helper.c       |  10 +
>>   drivers/gpu/drm/drm_framebuffer.c         | 108 +++++
>>   drivers/gpu/drm/drm_internal.h            |   4 +
>>   drivers/gpu/drm/drm_panic.c               | 640
>> ++++++++++++++++++++++++++++++
>>   drivers/gpu/drm/simpledrm/simpledrm_kms.c |  11 +
>>   include/drm/drm_framebuffer.h             |  40 ++
>>   9 files changed, 818 insertions(+), 1 deletion(-)
>>   create mode 100644 drivers/gpu/drm/drm_panic.c
>>
>> --
>> 2.8.2
>>
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel



-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2016-10-05 13:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-11 18:47 [PATCH 0/3] drm: Add panic handling Noralf Trønnes
2016-09-11 18:47 ` [PATCH 1/3] drm: Add support for panic message output Noralf Trønnes
2016-09-12 18:09   ` Noralf Trønnes
2016-09-11 18:47 ` [PATCH 2/3] drm/fb_cma_helper: Add panic handling Noralf Trønnes
2016-10-05 13:22   ` Laurent Pinchart
2016-10-05 19:36     ` Noralf Trønnes
2016-10-06  9:12       ` Daniel Vetter
2016-10-06 10:17         ` Laurent Pinchart
2016-09-11 18:47 ` [PATCH 3/3] drm/simpledrm: " Noralf Trønnes
2016-10-02 13:47 ` [PATCH 0/3] drm: " Noralf Trønnes
2016-10-05 13:14   ` Daniel Vetter [this message]

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=CAKMK7uFBxpHYUQF7EqvVuicehnbFi0Ff7HapO3Hed2RPZc-sHw@mail.gmail.com \
    --to=daniel@ffwll.ch \
    --cc=dh.herrmann@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=noralf@tronnes.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;
as well as URLs for NNTP newsgroup(s).