linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2] setup: Move unmask of async interrupts after possible earlycon setup
Date: Wed, 27 Aug 2014 10:16:59 +0100	[thread overview]
Message-ID: <20140827091659.GF6968@arm.com> (raw)
In-Reply-To: <1409084618-14693-1-git-send-email-jcm@redhat.com>

On Tue, Aug 26, 2014 at 09:23:38PM +0100, Jon Masters wrote:
> The kernel wants to enable reporting of asynchronous interrupts (i.e.
> System Errors) as early as possible. But if this happens too early then
> any pending System Error on initial entry into the kernel may never be
> reported where a user can see it. This situation will occur if the kernel
> is configured with CONFIG_PANIC_ON_OOPS set and (default or command line)
> enabled, in which case the kernel will panic as intended, however the
> associated logging messages indicating this failure condition will remain
> only in the kernel ring buffer and never be flushed out to the (not yet
> configured) console. Therefore, this patch moves the enabling of
> asynchronous interrupts during early setup to as early as reasonable,
> but after parsing any possible earlycon parameters setting up earlycon.
> 
> Signed-off-by: Jon Masters <jcm@redhat.com>

The patch looks fine, we'll pick it up. We initially didn't have this at
all and it was only showing when it got to user space. But I moved it
too early afterwards.

Thanks.

-- 
Catalin

      reply	other threads:[~2014-08-27  9:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-26 20:23 [PATCH V2] setup: Move unmask of async interrupts after possible earlycon setup Jon Masters
2014-08-27  9:16 ` Catalin Marinas [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=20140827091659.GF6968@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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).