From: Bernhard Walle <bwalle@suse.de>
To: kexec@lists.infradead.org
Subject: Re: [PATCH]: add dmesg log symbols to /proc/vmcoreinfo lists
Date: Tue, 20 Jan 2009 15:20:59 +0100 [thread overview]
Message-ID: <200901201521.00220.bwalle@suse.de> (raw)
In-Reply-To: <20090120141551.GA5125@redhat.com>
* Vivek Goyal [2009-01-20 15:15:51]:
> On Mon, Jan 19, 2009 at 04:21:27PM -0500, Neil Horman wrote:
> > Hey all-
> > It would be nice to be able to extract the dmesg log from a vmcore
> > file without needing to keep the debug symbols for the running
> > kernel handy all the time. We have a facility to do this in
> > /proc/vmcore. This patch adds the log_buf and log_end symbols to
> > the vmcoreinfo area so that tools (like makedumpfile) can easily
> > extract the dmesg logs from a vmcore image.
>
> It would be nice to get dmesg log if debug symbols are not around.
> Can't we use System.map for getting symbol addresses? vmcoreinfo had
> started small and seems to be growing now. I am thinking down the
> line will making use of System.map for such cases make sense?
Or: Just include the address of the kallsyms buffer in the VMCOREINFO,
and you even can extract the System.map from the memory, no need to have
System.map files copied.
Yes, that's the same amount of addition in the initrd, but it opens more
possibilities than just the log buffer.
Bernhard
--
Bernhard Walle, SUSE Linux Products GmbH, Architecture Development
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2009-01-20 14:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-19 21:21 [PATCH]: add dmesg log symbols to /proc/vmcoreinfo lists Neil Horman
2009-01-20 4:12 ` Simon Horman
2009-01-20 14:15 ` Vivek Goyal
2009-01-20 14:20 ` Bernhard Walle [this message]
2009-01-20 15:09 ` Neil Horman
2009-01-20 15:22 ` Vivek Goyal
2009-01-27 8:12 ` Andrew Morton
2009-01-27 11:55 ` Neil Horman
2009-01-27 15:37 ` Vivek Goyal
2009-01-28 4:11 ` Simon Horman
2009-02-03 20:45 ` Eric W. Biederman
2009-02-04 12:05 ` Neil Horman
2009-02-04 15:37 ` Eric W. Biederman
2009-02-04 21:41 ` Neil Horman
2009-02-05 0:23 ` Ken'ichi Ohmichi
2009-02-05 11:52 ` Neil Horman
2009-02-08 8:52 ` Simon Horman
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=200901201521.00220.bwalle@suse.de \
--to=bwalle@suse.de \
--cc=kexec@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