linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: calls to notify_die missing -> ftrace_dump_on_oops non-functional
Date: Sun, 13 Sep 2009 21:01:17 +0100	[thread overview]
Message-ID: <20090913200117.GA30169@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20090913195543.GA9104@pengutronix.de>

On Sun, Sep 13, 2009 at 09:55:44PM +0200, Uwe Kleine-K?nig wrote:
> Hello Russell,
> 
> On Sat, Sep 12, 2009 at 10:36:48PM +0100, Russell King - ARM Linux wrote:
> > On Sat, Sep 12, 2009 at 09:54:54PM +0200, Uwe Kleine-K?nig wrote:
> > > Dying on ARM looks quite different to dying on x86.  Russell, what's
> > > your position here?  Would you accept a patch that makes them more
> > > similar?
> > 
> > The position is that I got tired of chasing x86 in this area, and
> > we've got what was the most correct implementation that I could come
> > up with.  We do quite a number of things differently from x86,
> > including providing as complete as possible siginfo stuff everywhere
> > possible.
> > 
> > So, here's a patch which does an overall update to the ARM die()
> > implementation, including adding the notify support, kexec support
> > and loglevel stuff to printks.
> There are still a few printks without loglevel.  Is this intended?
> Just looking at the patch, I think it's good.  I will test it for a
> while in my tree.  Thanks.

Getting them into the backtrace isn't easy atm - that's also used for
printing stuff other than just the oops, and we currently have no easy
way to provide the log level to it.  Eg, we wouldn't want things like
the task debug backtraces to be printed at EMERG level.

      reply	other threads:[~2009-09-13 20:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-12 19:54 calls to notify_die missing -> ftrace_dump_on_oops non-functional Uwe Kleine-König
2009-09-12 21:36 ` Russell King - ARM Linux
2009-09-13 19:55   ` Uwe Kleine-König
2009-09-13 20:01     ` Russell King - ARM Linux [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=20090913200117.GA30169@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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).