From: Borislav Petkov <bp@alien8.de>
To: Kazuhito Hagio <k-hagio@ab.jp.nec.com>
Cc: lijiang <lijiang@redhat.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"bhe@redhat.com" <bhe@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
"x86@kernel.org" <x86@kernel.org>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"dyoung@redhat.com" <dyoung@redhat.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/2 v2] kdump: add the vmcoreinfo documentation
Date: Mon, 10 Dec 2018 19:32:21 +0100 [thread overview]
Message-ID: <20181210183221.GA5482@zn.tnic> (raw)
In-Reply-To: <4AE2DC15AC0B8543882A74EA0D43DBEC0356426E@BPXM09GP.gisp.nec.co.jp>
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.
next prev parent reply other threads:[~2018-12-10 18:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181202030839.29945-1-lijiang@redhat.com>
[not found] ` <20181202030839.29945-2-lijiang@redhat.com>
2018-12-03 15:08 ` [PATCH 1/2 v2] kdump: add the vmcoreinfo documentation Borislav Petkov
2018-12-04 9:35 ` lijiang
2018-12-05 10:16 ` Dave Young
2018-12-05 14:21 ` lijiang
2018-12-05 11:30 ` Borislav Petkov
2018-12-05 14:21 ` lijiang
2018-12-05 20:29 ` Kazuhito Hagio
2018-12-10 18:32 ` Borislav Petkov [this message]
2018-12-10 21:10 ` Kazuhito Hagio
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=20181210183221.GA5482@zn.tnic \
--to=bp@alien8.de \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=corbet@lwn.net \
--cc=dyoung@redhat.com \
--cc=k-hagio@ab.jp.nec.com \
--cc=kexec@lists.infradead.org \
--cc=lijiang@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).