Re: [PATCH, RFC 05/62] mm/page_alloc: Handle allocation for encrypted memory

2019-05-29 Thread Kirill A. Shutemov
On Wed, May 29, 2019 at 10:21:25AM +0300, Mike Rapoport wrote: > Shouldn't it be EXPORT_SYMBOL? We don't have callers outside core-mm at the moment. I'll add kerneldoc in the next submission. -- Kirill A. Shutemov

Re: [PATCH, RFC 05/62] mm/page_alloc: Handle allocation for encrypted memory

2019-05-29 Thread Mike Rapoport
On Wed, May 08, 2019 at 05:43:25PM +0300, Kirill A. Shutemov wrote: > For encrypted memory, we need to allocate pages for a specific > encryption KeyID. > > There are two cases when we need to allocate a page for encryption: > > - Allocation for an encrypted VMA; > > - Allocation for

[PATCH, RFC 05/62] mm/page_alloc: Handle allocation for encrypted memory

2019-05-08 Thread Kirill A. Shutemov
For encrypted memory, we need to allocate pages for a specific encryption KeyID. There are two cases when we need to allocate a page for encryption: - Allocation for an encrypted VMA; - Allocation for migration of encrypted page; The first case can be covered within alloc_page_vma(). We know