From: lijiang <lijiang@redhat.com>
To: Kazuhito Hagio <k-hagio@ab.jp.nec.com>
Cc: "bhe@redhat.com" <bhe@redhat.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"bp@alien8.de" <bp@alien8.de>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"dyoung@redhat.com" <dyoung@redhat.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2 v4] kdump: add the vmcoreinfo documentation
Date: Fri, 4 Jan 2019 10:28:20 +0800 [thread overview]
Message-ID: <bf26e868-9dfd-5344-df56-df8ff0442df0@redhat.com> (raw)
In-Reply-To: <4AE2DC15AC0B8543882A74EA0D43DBEC035656E1@BPXM09GP.gisp.nec.co.jp>
在 2019年01月04日 03:28, Kazuhito Hagio 写道:
> Hi Lianbo,
>
> -----Original Message-----
>> +=======================
>> +What is the VMCOREINFO?
>> +=======================
>> +
>> +VMCOREINFO is a special ELF note section. It contains various
>> +information from the kernel like structure size, page size, symbol
>> +values, field offsets, etc. These data are packed into an ELF note
>> +section and used by user-space tools like crash and makedumpfile to
>> +analyze a kernel's memory layout.
>> +
>> +To dump the VMCOREINFO contents, one can do:
>> +
>> +# makedumpfile -g VMCOREINFO -x vmlinux
>
> again, this command does not dump the VMCOREINFO in ELF note section.
> It converts the vmlinux's debug infomation into a VMCOREINFO-like data.
> So I don't think this command is suitable to introduce here.
>
Thank you, Kazu.
As you mentioned, makedumpfile in 'devel' branch can print VMCOREINFO in /proc/kcore,
can i add the following command to this document?
#makedumpfile --mem-usage /proc/kcore -D
>> +PG_lru|PG_private|PG_swapcache|PG_swapbacked|PG_slab|
>> +PG_hwpoision|PG_head_mask
>> +-----------------------------------------------------
>> +
>> +Page attributes. These flags are used to filter free pages.
>
> Some of these are not used to filter *free* pages, so
>
> ... used to filter various unnecessary pages.
>
Great. I will modify it in next post.
And also merge the 'PG_buddy' and 'PG_offline' into the PG_* flag here.
Many thanks.
Lianbo
>> +PAGE_BUDDY_MAPCOUNT_VALUE or ~PG_buddy
>> +--------------------------------------
>
> then, this can be merged into the one above?
>
>> +======
>> +x86_64
>> +======
> ...
>> +PAGE_OFFLINE_MAPCOUNT_VALUE(~PG_offline)
>> +----------------------------------------
>
> This looks not only for x86_64, and also can be merged into
> the PG_* flags?
>
> Thank you for your effort!
> Kazu
>
>
next prev parent reply other threads:[~2019-01-04 2:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 5:40 [PATCH 0/2 v4] kdump,vmcoreinfo: Export the value of sme mask to vmcoreinfo Lianbo Jiang
2018-12-20 5:40 ` [PATCH 1/2 v4] kdump: add the vmcoreinfo documentation Lianbo Jiang
2019-01-03 19:28 ` Kazuhito Hagio
2019-01-04 2:28 ` lijiang [this message]
2019-01-04 15:31 ` Kazuhito Hagio
2018-12-20 5:40 ` [PATCH 2/2 v4] kdump,vmcoreinfo: Export the value of sme mask to vmcoreinfo Lianbo Jiang
2018-12-26 3:33 ` [PATCH 0/2 " Dave Young
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=bf26e868-9dfd-5344-df56-df8ff0442df0@redhat.com \
--to=lijiang@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=dyoung@redhat.com \
--cc=k-hagio@ab.jp.nec.com \
--cc=kexec@lists.infradead.org \
--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).