All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Dave Airlie <airlied@gmail.com>
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.sf.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] vt/console: try harder to print output when panicing
Date: Wed, 23 Jun 2010 15:43:05 +0000	[thread overview]
Message-ID: <20100623084305.033df51e@virtuousgeek.org> (raw)
In-Reply-To: <1277262779-19338-1-git-send-email-airlied@gmail.com>

On Wed, 23 Jun 2010 13:12:59 +1000
Dave Airlie <airlied@gmail.com> wrote:

> From: Jesse Barnes <jbarnes@virtuousgeek.org>
> 
> Jesse's initial patch commit said:
> 
> "At panic time (i.e. when oops_in_progress is set) we should try a bit
> harder to update the screen and make sure output gets to the VT, since
> some drivers are capable of flipping back to it.
> 
> So make sure we try to unblank and update the display if called from a
> panic context."
> 
> I've enhanced this to add a flag to the vc that console layer can set
> to indicate they want this behaviour to occur. This also adds support
> to fbcon for that flag and adds an fb flag for drivers to indicate
> they want to use the support. It enables this for KMS drivers.
> 
> Signed-off-by: Dave Airlie <airlied@redhat.com>
> ---

Yeah this looks a little nicer, thanks.

Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>

-- 
Jesse Barnes, Intel Open Source Technology Center

WARNING: multiple messages have this Message-ID (diff)
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Dave Airlie <airlied@gmail.com>
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.sf.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] vt/console: try harder to print output when panicing
Date: Wed, 23 Jun 2010 08:43:05 -0700	[thread overview]
Message-ID: <20100623084305.033df51e@virtuousgeek.org> (raw)
In-Reply-To: <1277262779-19338-1-git-send-email-airlied@gmail.com>

On Wed, 23 Jun 2010 13:12:59 +1000
Dave Airlie <airlied@gmail.com> wrote:

> From: Jesse Barnes <jbarnes@virtuousgeek.org>
> 
> Jesse's initial patch commit said:
> 
> "At panic time (i.e. when oops_in_progress is set) we should try a bit
> harder to update the screen and make sure output gets to the VT, since
> some drivers are capable of flipping back to it.
> 
> So make sure we try to unblank and update the display if called from a
> panic context."
> 
> I've enhanced this to add a flag to the vc that console layer can set
> to indicate they want this behaviour to occur. This also adds support
> to fbcon for that flag and adds an fb flag for drivers to indicate
> they want to use the support. It enables this for KMS drivers.
> 
> Signed-off-by: Dave Airlie <airlied@redhat.com>
> ---

Yeah this looks a little nicer, thanks.

Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>

-- 
Jesse Barnes, Intel Open Source Technology Center

  reply	other threads:[~2010-06-23 15:43 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-23  3:12 [PATCH] vt/console: try harder to print output when panicing Dave Airlie
2010-06-23  3:12 ` Dave Airlie
2010-06-23 15:43 ` Jesse Barnes [this message]
2010-06-23 15:43   ` Jesse Barnes
2010-06-23 15:43 ` Jesse Barnes
2010-06-23 15:57 ` James Simmons
2010-06-23 15:57   ` James Simmons
2010-06-23 15:57 ` James Simmons
2010-06-23 19:56 ` Andrew Morton
2010-06-23 19:56 ` Andrew Morton
2010-06-23 19:56   ` Andrew Morton
2010-06-23 20:05   ` Jesse Barnes
2010-06-23 20:05     ` Jesse Barnes
2010-06-23 20:36     ` Andrew Morton
2010-06-23 20:36       ` Andrew Morton
2010-06-23 20:40       ` Jesse Barnes
2010-06-23 20:40       ` Jesse Barnes
2010-06-23 20:40         ` Jesse Barnes
2010-06-23 20:36     ` Andrew Morton
2010-06-23 20:05   ` Jesse Barnes
  -- strict thread matches above, loose matches on Subject: below --
2010-06-23  3:12 Dave Airlie

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=20100623084305.033df51e@virtuousgeek.org \
    --to=jbarnes@virtuousgeek.org \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.sf.net \
    --cc=linux-fbdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.