[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181210183221.GA5482@zn.tnic>
Date: Mon, 10 Dec 2018 19:32:21 +0100
From: Borislav Petkov <bp@...en8.de>
To: Kazuhito Hagio <k-hagio@...jp.nec.com>
Cc: lijiang <lijiang@...hat.com>,
"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
On Wed, Dec 05, 2018 at 08:29:14PM +0000, Kazuhito Hagio wrote:
> 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.
Sure, I used a vmlinux for that.
> 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.)
Might be useful as people are looking into using VMCOREINFO when
debugging a live kernel...
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
Powered by blists - more mailing lists