From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Arjan van de Ven <arjan@infradead.org>,
linux-kernel@vger.kernel.org, x86@kernel.org,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH] scripts: script from kerneloops.org to pretty print oops dumps
Date: Wed, 26 Nov 2008 09:27:44 +0100 [thread overview]
Message-ID: <20081126082744.GL26036@elte.hu> (raw)
In-Reply-To: <20081126001234.19c9a7b0.akpm@linux-foundation.org>
* Andrew Morton <akpm@linux-foundation.org> wrote:
> On Wed, 26 Nov 2008 08:24:45 +0100 Ingo Molnar <mingo@elte.hu> wrote:
>
> > > scripts/markup_oops.pl | 162 ++++++++++++++++++++++++++++++++++++++++++++++++
> > > 1 files changed, 162 insertions(+), 0 deletions(-)
> > > create mode 100644 scripts/markup_oops.pl
> >
> > looks useful - Andrew, Sam, any objections to this?
>
> who-me-no-i-already-merged-it.
>
> I didn't test it though - I don't have particularly high hopes given
> the general deadness of `make mm/memory.lst' for the past numerous
> years.
>
> But it's worth trying. The challenge will be getting people to
> remember that it exists, and to use it.
>
> I often turn off CONFIG_DEUG_INFO because it slows builds down so
> much. It is irritating when such a kernel goes splat.
i keep DEBUG_INFO turned off all the time, and only turn it on if
really needed. But in that case i can just turn it on and rebuild:
recent gccs seem better at keeping the image unmodified. (or at least
so i kid myself)
Years ago the image would mute a bit with DEBUG_INFO enabled, making
the splat info fuzzy. Seems better now.
Ingo
next prev parent reply other threads:[~2008-11-26 8:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-23 21:00 Arjan van de Ven
2008-11-26 7:24 ` Ingo Molnar
2008-11-26 8:12 ` Andrew Morton
2008-11-26 8:27 ` Ingo Molnar [this message]
2008-11-26 14:09 ` Andi Kleen
2008-11-26 8:18 ` Vegard Nossum
2008-11-26 14:49 ` Arjan van de Ven
-- strict thread matches above, loose matches on Subject: below --
2008-11-06 3:07 Arjan van de Ven
2008-11-06 4:15 ` Keith Owens
2008-11-06 5:36 ` Arjan van de Ven
2008-11-06 10:29 ` Américo Wang
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=20081126082744.GL26036@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=x86@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®