[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b9344b71-3ae9-95c0-ccc2-ec3db37ccf9f@intel.com>
Date: Tue, 4 Sep 2018 12:27:48 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Alexander Duyck <alexander.duyck@...il.com>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Cc: alexander.h.duyck@...el.com, pavel.tatashin@...rosoft.com,
mhocko@...e.com, akpm@...ux-foundation.org, mingo@...nel.org,
kirill.shutemov@...ux.intel.com
Subject: Re: [PATCH 2/2] mm: Create non-atomic version of SetPageReserved for
init use
On 09/04/2018 11:33 AM, Alexander Duyck wrote:
> +++ b/mm/page_alloc.c
> @@ -1231,7 +1231,7 @@ void __meminit reserve_bootmem_region(phys_addr_t start, phys_addr_t end)
> /* Avoid false-positive PageTail() */
> INIT_LIST_HEAD(&page->lru);
>
> - SetPageReserved(page);
> + __SetPageReserved(page);
> }
> }
> }
> @@ -5518,7 +5518,7 @@ void __meminit memmap_init_zone(unsigned long size, int nid, unsigned long zone,
> page = pfn_to_page(pfn);
> __init_single_page(page, pfn, zone, nid);
> if (context == MEMMAP_HOTPLUG)
> - SetPageReserved(page);
> + __SetPageReserved(page);
Comments needed, please. SetPageReserved() is opaque enough by itself,
but having to discern between it and an __ variant is even less fun.
Powered by blists - more mailing lists