[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140507173728.GW30445@twins.programming.kicks-ass.net>
Date: Wed, 7 May 2014 19:37:28 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Ingo Molnar <mingo@...nel.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Richard Yao <ryao@...too.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
the arch/x86 maintainers <x86@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Tejun Heo <tj@...nel.org>, Vineet Gupta <vgupta@...opsys.com>,
Jesper Nilsson <jesper.nilsson@...s.com>,
Jiri Slaby <jslaby@...e.cz>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
kernel@...too.org, Brian Behlendorf <behlendorf1@...l.gov>,
Frédéric Weisbecker <fweisbec@...il.com>,
Arnaldo Carvalho de Melo <acme@...radead.org>,
Jiri Olsa <jolsa@...hat.com>
Subject: Re: [PATCH] x86/dumpstack: Walk frames when built with frame pointers
On Wed, May 07, 2014 at 07:18:22PM +0200, Ingo Molnar wrote:
>
> Conclusion:
>
> So to me #4 looks best, and it's 16 lines instead of 31. Not as
> compact as your mockup that has 13 lines, but pretty close.
>
> (I'd also do the color tricks on #6, but that's more technically
> challenging and I also don't look forward fighting the syslog guys
> over it...)
>
> I'd guess that some people would prefer #2 or #3, depending on how
> ergonomic the parentheses and brackets are for them.
>
Can we get a CONFIG option to retain the old (current) format? My brain
is all used to those and since I use a logging serial console there's no
space issues what so ever.
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists