From: David Hildenbrand <david@redhat.com>
To: linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org,
David Hildenbrand <david@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Dave Young <dyoung@redhat.com>, Baoquan He <bhe@redhat.com>,
Hari Bathini <hbathini@linux.vnet.ibm.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Michal Hocko <mhocko@kernel.org>
Subject: [PATCH v1 2/2] kdump: include PG_reserved value in VMCOREINFO
Date: Fri, 20 Jul 2018 14:34:22 +0200 [thread overview]
Message-ID: <20180720123422.10127-3-david@redhat.com> (raw)
In-Reply-To: <20180720123422.10127-1-david@redhat.com>
PG_reserved pages should never be touched by enybody except their owner.
Let's allow dumping tools to skip these pages.
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Dave Young <dyoung@redhat.com>
Cc: Baoquan He <bhe@redhat.com>
Cc: Hari Bathini <hbathini@linux.vnet.ibm.com>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Cc: Michal Hocko <mhocko@kernel.org>
Signed-off-by: David Hildenbrand <david@redhat.com>
---
kernel/crash_core.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/crash_core.c b/kernel/crash_core.c
index b66aced5e8c2..ab216accf96a 100644
--- a/kernel/crash_core.c
+++ b/kernel/crash_core.c
@@ -451,6 +451,7 @@ static int __init crash_save_vmcoreinfo_init(void)
log_buf_vmcoreinfo_setup();
VMCOREINFO_LENGTH(free_area.free_list, MIGRATE_TYPES);
VMCOREINFO_NUMBER(NR_FREE_PAGES);
+ VMCOREINFO_NUMBER(PG_reserved);
VMCOREINFO_NUMBER(PG_lru);
VMCOREINFO_NUMBER(PG_private);
VMCOREINFO_NUMBER(PG_swapcache);
--
2.17.1
next prev parent reply other threads:[~2018-07-20 12:34 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 12:34 [PATCH v1 0/2] mm/kdump: exclude reserved pages in dumps David Hildenbrand
2018-07-20 12:34 ` [PATCH v1 1/2] mm: clarify semantics of reserved pages David Hildenbrand
2018-07-23 10:48 ` Michal Hocko
2018-07-20 12:34 ` David Hildenbrand [this message]
2018-07-23 11:45 ` [PATCH v1 0/2] mm/kdump: exclude reserved pages in dumps Vlastimil Babka
2018-07-23 12:30 ` Michal Hocko
2018-07-23 17:20 ` David Hildenbrand
2018-07-24 7:25 ` Michal Hocko
2018-07-24 8:46 ` David Hildenbrand
2018-07-24 8:53 ` Michal Hocko
2018-07-24 9:18 ` David Hildenbrand
2018-07-24 12:17 ` David Hildenbrand
2018-07-24 13:13 ` Michal Hocko
2018-07-24 13:27 ` David Hildenbrand
2018-07-24 13:35 ` Michal Hocko
2018-07-24 14:13 ` David Hildenbrand
2018-07-25 13:51 ` Michal Hocko
2018-07-25 14:20 ` David Hildenbrand
2018-07-26 8:27 ` Michal Hocko
2018-07-26 8:37 ` David Hildenbrand
2018-07-24 9:47 ` Vlastimil Babka
2018-07-24 11:19 ` Michal Hocko
2018-07-24 12:22 ` Vlastimil Babka
2018-07-24 12:33 ` David Hildenbrand
2018-07-24 13:06 ` Michal Hocko
2018-07-23 17:12 ` David Hildenbrand
2018-07-24 7:22 ` Michal Hocko
2018-07-24 9:48 ` Vlastimil Babka
2018-07-26 8:22 ` David Hildenbrand
2018-07-26 8:30 ` Michal Hocko
2018-07-26 8:45 ` David Hildenbrand
2018-07-26 19:50 ` Andrew Morton
2018-07-30 8:17 ` David Hildenbrand
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=20180720123422.10127-3-david@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=dyoung@redhat.com \
--cc=hbathini@linux.vnet.ibm.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@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