From: js1304@gmail.com
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Vlastimil Babka <vbabka@suse.cz>,
Laura Abbott <labbott@redhat.com>,
"Aneesh Kumar K . V" <aneesh.kumar@linux.ibm.com>,
Mel Gorman <mgorman@techsingularity.net>,
Michal Hocko <mhocko@suse.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Roman Gushchin <guro@fb.com>, Minchan Kim <minchan@kernel.org>,
Rik van Riel <riel@surriel.com>,
Christian Koenig <christian.koenig@amd.com>,
Huang Rui <ray.huang@amd.com>,
Eric Biederman <ebiederm@xmission.com>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Pavel Machek <pavel@ucw.cz>, Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: [PATCH 09/10] mm/page_alloc: correct the use of is_highmem_idx()
Date: Mon, 20 Apr 2020 16:59:41 +0900 [thread overview]
Message-ID: <1587369582-3882-10-git-send-email-iamjoonsoo.kim@lge.com> (raw)
In-Reply-To: <1587369582-3882-1-git-send-email-iamjoonsoo.kim@lge.com>
From: Joonsoo Kim <iamjoonsoo.kim@lge.com>
What we'd like to check here is whether page has direct mapping or not.
Use PageHighMem() since it is perfectly matched for this purpose.
Signed-off-by: Joonsoo Kim <iamjoonsoo.kim@lge.com>
---
mm/page_alloc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index 9997f87..e07148d 100644
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -1399,7 +1399,7 @@ static void __meminit __init_single_page(struct page *page, unsigned long pfn,
INIT_LIST_HEAD(&page->lru);
#ifdef WANT_PAGE_VIRTUAL
/* The shift won't overflow because ZONE_NORMAL is below 4G. */
- if (!is_highmem_idx(zone))
+ if (!PageHighMem(page))
set_page_address(page, __va(pfn << PAGE_SHIFT));
#endif
}
--
2.7.4
next prev parent reply other threads:[~2020-04-20 8:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 7:59 [PATCH 00/10] change the implemenation of the PageHighMem() js1304
2020-04-20 7:59 ` [PATCH 01/10] mm/page-flags: introduce PageHighMemZone() js1304
2020-04-20 11:20 ` Matthew Wilcox
2020-04-20 11:37 ` Vlastimil Babka
2020-04-21 6:43 ` Joonsoo Kim
2021-02-10 12:56 ` Prakash Gupta
2020-04-21 9:00 ` Christoph Hellwig
2020-04-22 1:02 ` Roman Gushchin
2020-04-22 7:42 ` Joonsoo Kim
2020-04-22 7:40 ` Joonsoo Kim
2020-04-20 7:59 ` [PATCH 02/10] drm/ttm: separate PageHighMem() and PageHighMemZone() use case js1304
2020-04-20 8:42 ` Christian König
2020-04-21 6:49 ` Joonsoo Kim
2020-04-20 7:59 ` [PATCH 03/10] mm/migrate: " js1304
2020-04-22 7:44 ` Christoph Hellwig
2020-04-22 7:55 ` Joonsoo Kim
2020-04-20 7:59 ` [PATCH 04/10] kexec: " js1304
2020-04-20 7:59 ` [PATCH 05/10] power: " js1304
2020-04-20 7:59 ` [PATCH 06/10] mm/gup: " js1304
2020-04-20 7:59 ` [PATCH 07/10] mm/hugetlb: " js1304
2020-04-20 7:59 ` [PATCH 08/10] mm: " js1304
2020-04-20 7:59 ` js1304 [this message]
2020-04-20 7:59 ` [PATCH 10/10] mm/page-flags: change the implementation of the PageHighMem() js1304
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=1587369582-3882-10-git-send-email-iamjoonsoo.kim@lge.com \
--to=js1304@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=christian.koenig@amd.com \
--cc=ebiederm@xmission.com \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=minchan@kernel.org \
--cc=pavel@ucw.cz \
--cc=ray.huang@amd.com \
--cc=riel@surriel.com \
--cc=rjw@rjwysocki.net \
--cc=vbabka@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).