Re: [PATCH v2 04/10] power: separate PageHighMem() and PageHighMemZone() use case

2020-05-03 Thread Joonsoo Kim
2020년 5월 1일 (금) 오후 9:22, Christoph Hellwig 님이 작성: > > On Wed, Apr 29, 2020 at 12:26:37PM +0900, js1...@gmail.com wrote: > > index 6598001..be759a6 100644 > > --- a/kernel/power/snapshot.c > > +++ b/kernel/power/snapshot.c > > @@ -1227,7 +1227,7 @@ static struct page *saveable_highmem_page(struct

Re: [PATCH v2 04/10] power: separate PageHighMem() and PageHighMemZone() use case

2020-05-01 Thread Christoph Hellwig
On Wed, Apr 29, 2020 at 12:26:37PM +0900, js1...@gmail.com wrote: > index 6598001..be759a6 100644 > --- a/kernel/power/snapshot.c > +++ b/kernel/power/snapshot.c > @@ -1227,7 +1227,7 @@ static struct page *saveable_highmem_page(struct zone > *zone, unsigned long pfn) > if (!page ||

[PATCH v2 04/10] power: separate PageHighMem() and PageHighMemZone() use case

2020-04-28 Thread js1304
From: Joonsoo Kim Until now, PageHighMem() is used for two different cases. One is to check if there is a direct mapping for this page or not. The other is to check the zone of this page, that is, weather it is the highmem type zone or not. Now, we have separate functions, PageHighMem() and