From: Gavin Shan <gshan@redhat.com>
To: linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org, alexander.duyck@gmail.com,
akpm@linux-foundation.org, david@redhat.com,
anshuman.khandual@arm.com, catalin.marinas@arm.com,
will@kernel.org, shan.gavin@gmail.com
Subject: [PATCH 2/3] mm/page_reporting: Allow architecture to select reporting order
Date: Mon, 21 Jun 2021 13:11:51 +0800 [thread overview]
Message-ID: <20210621051152.305224-3-gshan@redhat.com> (raw)
In-Reply-To: <20210621051152.305224-1-gshan@redhat.com>
This renames PAGE_REPORTING_MIN_ORDER to PAGE_REPORTING_ORDER, to
match with the variable name (@page_reporting_order). Its value is
stick to @pageblock_order if architecture doesn't specify it. This
is going to be used by arm64 when 64KB base page size is selected.
Signed-off-by: Gavin Shan <gshan@redhat.com>
---
mm/page_reporting.c | 2 +-
mm/page_reporting.h | 7 +++++--
2 files changed, 6 insertions(+), 3 deletions(-)
diff --git a/mm/page_reporting.c b/mm/page_reporting.c
index 759b29f6e845..d4d9f5265d6b 100644
--- a/mm/page_reporting.c
+++ b/mm/page_reporting.c
@@ -10,7 +10,7 @@
#include "page_reporting.h"
#include "internal.h"
-unsigned int page_reporting_order = PAGE_REPORTING_MIN_ORDER;
+unsigned int page_reporting_order = PAGE_REPORTING_ORDER;
module_param(page_reporting_order, uint, 0644);
MODULE_PARM_DESC(page_reporting_order, "Set page reporting order");
diff --git a/mm/page_reporting.h b/mm/page_reporting.h
index 19d58a590cc2..91688dd30abe 100644
--- a/mm/page_reporting.h
+++ b/mm/page_reporting.h
@@ -10,9 +10,12 @@
#include <linux/pgtable.h>
#include <linux/scatterlist.h>
-#define PAGE_REPORTING_MIN_ORDER pageblock_order
-
#ifdef CONFIG_PAGE_REPORTING
+
+#ifndef PAGE_REPORTING_ORDER
+#define PAGE_REPORTING_ORDER pageblock_order
+#endif
+
DECLARE_STATIC_KEY_FALSE(page_reporting_enabled);
extern unsigned int page_reporting_order;
void __page_reporting_notify(void);
--
2.23.0
next prev parent reply other threads:[~2021-06-21 3:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 5:11 [PATCH 0/3] mm/page_reporting: Make page reporting work on arm64 with 64KB page size Gavin Shan
2021-06-21 5:11 ` [PATCH 1/3] mm/page_reporting: Allow to set reporting order Gavin Shan
2021-06-21 5:11 ` Gavin Shan [this message]
2021-06-21 5:11 ` [PATCH 3/3] arm64: mm: Specify smaller page " Gavin Shan
2021-06-21 14:02 ` [PATCH 0/3] mm/page_reporting: Make page reporting work on arm64 with 64KB page size Alexander Duyck
2021-06-21 16:06 ` Michael Kelley
2021-06-22 2:04 ` ** POTENTIAL FRAUD ALERT - RED HAT ** " Gavin Shan
2021-06-22 2:01 ` Gavin Shan
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=20210621051152.305224-3-gshan@redhat.com \
--to=gshan@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.duyck@gmail.com \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shan.gavin@gmail.com \
--cc=will@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