[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4AE2DC15AC0B8543882A74EA0D43DBEC0356426E@BPXM09GP.gisp.nec.co.jp>
Date: Wed, 5 Dec 2018 20:29:14 +0000
From: Kazuhito Hagio <k-hagio@...jp.nec.com>
To: lijiang <lijiang@...hat.com>, Borislav Petkov <bp@...en8.de>
CC: "linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"bhe@...hat.com" <bhe@...hat.com>,
Jonathan Corbet <corbet@....net>,
"x86@...nel.org" <x86@...nel.org>,
"kexec@...ts.infradead.org" <kexec@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"mingo@...hat.com" <mingo@...hat.com>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"dyoung@...hat.com" <dyoung@...hat.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>
Subject: RE: [PATCH 1/2 v2] kdump: add the vmcoreinfo documentation
> >> Generating VMCOREINFO is easy in the first kernel, for example:
> >> # makedumpfile -g VMCOREINFO -x vmlinux
> >
> > I get:
> >
> > $ makedumpfile -g VMCOREINFO -x vmlinux
> > The kernel version is not supported.
> > The makedumpfile operation may be incomplete.
> >
> > The vmcoreinfo is saved to VMCOREINFO.
> >
> > makedumpfile Completed.
> >
> > But the text file looks ok AFAICT. Please add that command to the
> > documentation file.
> >
Please note that this VMCOREINFO is generated from the information in
the vmlinux only, not from the running kernel and /proc/kcore. So if
we add a command to dump it from running kernel, it's not suitable.
(This switch is intended to make a data that is used instead of vmlinux
when vmcore didn't have VMCOREINFO and makedumpfile is in a situation
that we don't have vmlinux. Please see the explanation of the -i and
-g options in makefumpfile(8).)
makedumpfile doesn't have any switch which dumps VMCOREINFO from kcore
for now. (I'm thinking to have makedumpfile dump it as debug message,
though.)
Thanks,
Kazu
Powered by blists - more mailing lists