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

On Mon, May 04, 2020 at 09:03:56AM -0500, Eric W. Biederman wrote: > > I have added in the kexec mailling list. > > Looking at the patch we are discussing it appears that the kexec code > could be doing much better in highmem situations today but is not. Sound great! > > > Joonsoo Kim

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

I have added in the kexec mailling list. Looking at the patch we are discussing it appears that the kexec code could be doing much better in highmem situations today but is not. Joonsoo Kim writes: > 2020년 5월 1일 (금) 오후 11:06, Eric W. Biederman 님이 작성: >> >> js1...@gmail.com writes: >> >> >

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

2020년 5월 1일 (금) 오후 11:06, Eric W. Biederman 님이 작성: > > js1...@gmail.com writes: > > > 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

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

js1...@gmail.com writes: > 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

[PATCH v2 03/10] kexec: separate PageHighMem() and PageHighMemZone() use case

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