* Re: [PATCH] x86_64: add an option to configure oops stack dump
[not found] <200410201907.i9KJ7r2s022648@hera.kernel.org>
@ 2004-10-21 15:13 ` Randy.Dunlap
0 siblings, 0 replies; only message in thread
From: Randy.Dunlap @ 2004-10-21 15:13 UTC (permalink / raw)
To: Linux Kernel Mailing List
Linux Kernel Mailing List wrote:
> ChangeSet 1.2016, 2004/10/20 08:11:53-07:00, ak@muc.de
>
> [PATCH] x86_64: add an option to configure oops stack dump
>
> Add an kstack= option to configure how much stack should be printed on a
> oops.
>
> Signed-off-by: Andi Kleen <ak@suse.de>
> Signed-off-by: Andrew Morton <akpm@osdl.org>
> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
>
>
>
> traps.c | 8 ++++++++
> 1 files changed, 8 insertions(+)
>
>
> diff -Nru a/arch/x86_64/kernel/traps.c b/arch/x86_64/kernel/traps.c
> --- a/arch/x86_64/kernel/traps.c 2004-10-20 12:08:04 -07:00
> +++ b/arch/x86_64/kernel/traps.c 2004-10-20 12:08:04 -07:00
> @@ -900,3 +900,11 @@
> return -1;
> }
> __setup("oops=", oops_dummy);
> +
> +static int __init kstack_setup(char *s)
> +{
> + kstack_depth_to_print = simple_strtoul(s,NULL,0);
> + return 0;
> +}
> +__setup("kstack=", kstack_setup);
I'm happy to see this, but I don't see why it's arch-specific...
--
~Randy
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2004-10-21 15:26 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <200410201907.i9KJ7r2s022648@hera.kernel.org>
2004-10-21 15:13 ` [PATCH] x86_64: add an option to configure oops stack dump Randy.Dunlap
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.