Re: [PATCHv5 18/19] x86/mm: Handle encrypted memory in page_to_virt() and __pa()

On Thu, Jul 26, 2018 at 10:26:23AM -0700, Dave Hansen wrote: > On 07/23/2018 03:12 AM, Kirill A. Shutemov wrote: > > page_to_virt() definition overwrites default macros provided by > > . We only overwrite the macros if MTKME is enabled > > compile-time. > > Can you remind me why we need this in pa

Re: [PATCHv5 18/19] x86/mm: Handle encrypted memory in page_to_virt() and __pa()

On 07/23/2018 03:12 AM, Kirill A. Shutemov wrote: > page_to_virt() definition overwrites default macros provided by > . We only overwrite the macros if MTKME is enabled > compile-time. Can you remind me why we need this in page_to_virt() as opposed to in the kmap() code? Is it because we have lot

Re: [PATCHv5 18/19] x86/mm: Handle encrypted memory in page_to_virt() and __pa()

On Thu, Jul 19, 2018 at 12:21:44AM +0200, Thomas Gleixner wrote: > On Tue, 17 Jul 2018, Kirill A. Shutemov wrote: > > > Per-KeyID direct mappings require changes into how we find the right > > virtual address for a page and virt-to-phys address translations. > > > > page_to_virt() definition over

Re: [PATCHv5 18/19] x86/mm: Handle encrypted memory in page_to_virt() and __pa()

On Tue, 17 Jul 2018, Kirill A. Shutemov wrote: > Per-KeyID direct mappings require changes into how we find the right > virtual address for a page and virt-to-phys address translations. > > page_to_virt() definition overwrites default macros provided by > . We only overwrite the macros if MTKME i

[PATCHv5 18/19] x86/mm: Handle encrypted memory in page_to_virt() and __pa()

Per-KeyID direct mappings require changes into how we find the right virtual address for a page and virt-to-phys address translations. page_to_virt() definition overwrites default macros provided by . We only overwrite the macros if MTKME is enabled compile-time. Signed-off-by: Kirill A. Shutemov