From: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>
To: Atsushi Kumagai <kumagai-atsushi@mxc.nes.nec.co.jp>
Cc: kexec@lists.infradead.org, cpw@sgi.com
Subject: Re: [PATCH] makedumpfile: Petr Tesarik's hugepage filtering
Date: Fri, 24 May 2013 11:40:47 +0900 [thread overview]
Message-ID: <519ED32F.6090005@jp.fujitsu.com> (raw)
In-Reply-To: <519ECF57.1080600@jp.fujitsu.com>
(2013/05/24 11:24), HATAYAMA Daisuke wrote:
> (2013/05/24 10:11), Atsushi Kumagai wrote:
>> On Wed, 15 May 2013 13:43:59 -0500
>> Cliff Wickman <cpw@sgi.com> wrote:
> Also, hugetlbfs pages are "user data". They should get filtered when user data dump level
> is specified. So how about:
>
> Dump | zero without with user free hugetlbfs
> Level | page private private data page page
> -------+-----------------------------------------------------
> 0 |
> 1 | X
> 2 | X
> 4 | X X
> 8 | X X
> 16 | X
> 32 | X
> 63 | X X X X X X
>
> On dump level 8, hugetlbfs pages also get filtered.
Thinking further, it might be unlikely that we want user data but don't want hugetlbfs pages
on crash dump case. If so, I think Petr's implementation seems also OK. It seems no problem
to postpone introducing new dump level after someone who wants to filter hugetlbfs pages only,
actually occurs.
--
Thanks.
HATAYAMA, Daisuke
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2013-05-24 2:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1UcggB-0005gy-4i@eag09.americas.sgi.com>
2013-05-24 1:11 ` [PATCH] makedumpfile: Petr Tesarik's hugepage filtering Atsushi Kumagai
2013-05-24 2:24 ` HATAYAMA Daisuke
2013-05-24 2:40 ` HATAYAMA Daisuke [this message]
2013-05-27 10:56 ` Atsushi Kumagai
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=519ED32F.6090005@jp.fujitsu.com \
--to=d.hatayama@jp.fujitsu.com \
--cc=cpw@sgi.com \
--cc=kexec@lists.infradead.org \
--cc=kumagai-atsushi@mxc.nes.nec.co.jp \
/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