Re: [PATCHv4 15/18] x86/mm: Calculate direct mapping size

2018-07-09 Thread Konrad Rzeszutek Wilk
On Tue, Jun 26, 2018 at 05:22:42PM +0300, Kirill A. Shutemov wrote: > The kernel needs to have a way to access encrypted memory. We have two > option on how approach it: > > - Create temporary mappings every time kernel needs access to encrypted >memory. That's basically brings highmem and

Re: [PATCHv4 15/18] x86/mm: Calculate direct mapping size

2018-07-09 Thread Konrad Rzeszutek Wilk
On Tue, Jun 26, 2018 at 05:22:42PM +0300, Kirill A. Shutemov wrote: > The kernel needs to have a way to access encrypted memory. We have two > option on how approach it: > > - Create temporary mappings every time kernel needs access to encrypted >memory. That's basically brings highmem and

[PATCHv4 15/18] x86/mm: Calculate direct mapping size

2018-06-26 Thread Kirill A. Shutemov
The kernel needs to have a way to access encrypted memory. We have two option on how approach it: - Create temporary mappings every time kernel needs access to encrypted memory. That's basically brings highmem and its overhead back. - Create multiple direct mappings, one per-KeyID. In this

[PATCHv4 15/18] x86/mm: Calculate direct mapping size

2018-06-26 Thread Kirill A. Shutemov
The kernel needs to have a way to access encrypted memory. We have two option on how approach it: - Create temporary mappings every time kernel needs access to encrypted memory. That's basically brings highmem and its overhead back. - Create multiple direct mappings, one per-KeyID. In this