From: Andi Kleen <andi@firstfloor.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Mike Snitzer <snitzer@gmail.com>,
Nicholas Miell <nmiell@comcast.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
jim owens <jowens@hp.com>, "H. Peter Anvin" <hpa@zytor.com>,
Chris Mason <chris.mason@oracle.com>,
Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
paulmck@linux.vnet.ibm.com, Gregory Haskins <ghaskins@novell.com>,
Matthew Wilcox <matthew@wil.cx>, Andi Kleen <andi@firstfloor.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Nick Piggin <npiggin@suse.de>,
Peter Morreale <pmorreale@novell.com>,
Sven Dietrich <SDietrich@novell.com>,
sam@ravnborg.org, Dave Anderson <anderson@redhat.com>
Subject: Re: source line numbers with x86_64 modules? [Was: Re: [patch] measurements, numbers about CONFIG_OPTIMIZE_INLINING=y impact]
Date: Sun, 11 Jan 2009 19:05:45 +0100 [thread overview]
Message-ID: <20090111180545.GL26290@one.firstfloor.org> (raw)
In-Reply-To: <20090111012811.GG12885@elte.hu>
> 'kdump light' perhaps that dumps the most important data structures like
> registers of all CPUs, task struct and the symbol tables, the current task
> itself including the kernel stack plus the surrounding 4K of all pointers
> that are in current registers and that point into kernel memory - maybe
> straight to kerneloops.org [if the user agrees] - or something like that.
All you would need for that would be a new custom level in makedumpfile
that dumps only this data (except that for live dumps it can be difficult to get
the full register contents) No kernel changes needed.
-Andi
--
ak@linux.intel.com
prev parent reply other threads:[~2009-01-11 18:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-10 14:21 source line numbers with x86_64 modules? [Was: Re: [patch] measurements, numbers about CONFIG_OPTIMIZE_INLINING=y impact] Mike Snitzer
2009-01-10 15:34 ` Ingo Molnar
2009-01-10 18:21 ` Mike Snitzer
2009-01-10 21:15 ` Theodore Tso
2009-01-10 22:21 ` Andi Kleen
2009-01-10 22:21 ` Andi Kleen
2009-01-10 22:21 ` Andi Kleen
2009-01-10 22:58 ` Linus Torvalds
2009-01-10 23:22 ` Ingo Molnar
2009-01-11 10:11 ` Andreas Dilger
2009-01-11 10:11 ` Andreas Dilger
2009-01-11 15:31 ` Mike Snitzer
2009-01-11 15:31 ` Mike Snitzer
2009-01-11 20:45 ` Theodore Tso
2009-01-11 10:11 ` Andreas Dilger
2009-01-11 1:28 ` Ingo Molnar
2009-01-11 4:52 ` Mike Snitzer
2009-01-13 3:19 ` Eric W. Biederman
2009-01-13 3:19 ` Eric W. Biederman
2009-01-13 3:19 ` Eric W. Biederman
2009-01-11 18:05 ` Andi Kleen [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=20090111180545.GL26290@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=SDietrich@novell.com \
--cc=akpm@linux-foundation.org \
--cc=anderson@redhat.com \
--cc=chris.mason@oracle.com \
--cc=ghaskins@novell.com \
--cc=hpa@zytor.com \
--cc=jowens@hp.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=mingo@elte.hu \
--cc=nmiell@comcast.net \
--cc=npiggin@suse.de \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=pmorreale@novell.com \
--cc=rostedt@goodmis.org \
--cc=sam@ravnborg.org \
--cc=snitzer@gmail.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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 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.