Messages in this thread Patch in this message | | | From | Zi Yan <> | Subject | [RFC PATCH v2 08/12] mm/page_reporting: set page_reporting_order to -1 to prevent it running | Date | Thu, 11 Aug 2022 19:16:39 -0400 |
| |
From: Zi Yan <ziy@nvidia.com>
page_reporting_order was initialized to MAX_ORDER to prevent it running before its value is overwritten. Use -1 instead to remove the dependency on MAX_ORDER.
Signed-off-by: Zi Yan <ziy@nvidia.com> Cc: David Hildenbrand <david@redhat.com> Cc: linux-mm@kvack.org Cc: linux-kernel@vger.kernel.org --- mm/page_reporting.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/mm/page_reporting.c b/mm/page_reporting.c index b48d6ad82998..001438f3dbeb 100644 --- a/mm/page_reporting.c +++ b/mm/page_reporting.c @@ -11,7 +11,11 @@ #include "page_reporting.h" #include "internal.h" -unsigned int page_reporting_order = MAX_PHYS_CONTIG_ORDER + 1; +/* + * Set page_reporting_order to (unsigned int)-1 to prevent it running until the + * value is being overwritten + */ +unsigned int page_reporting_order = (unsigned int)-1; module_param(page_reporting_order, uint, 0644); MODULE_PARM_DESC(page_reporting_order, "Set page reporting order"); -- 2.35.1
| |