[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180727134941.mljg2biwughv2yhr@kshutemo-mobl1>
Date: Fri, 27 Jul 2018 16:49:41 +0300
From: "Kirill A. Shutemov" <kirill@...temov.name>
To: Dave Hansen <dave.hansen@...el.com>
Cc: Thomas Gleixner <tglx@...utronix.de>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Ingo Molnar <mingo@...hat.com>, x86@...nel.org,
"H. Peter Anvin" <hpa@...or.com>,
Tom Lendacky <thomas.lendacky@....com>,
Kai Huang <kai.huang@...ux.intel.com>,
Jacob Pan <jacob.jun.pan@...ux.intel.com>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: 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
> > <linux/mm.h>. 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 lots of 64-bit code that doesn't
> use kmap() or something?
I just found it most suitable. It should cover all cases, even if kmap()
is not used.
--
Kirill A. Shutemov
Powered by blists - more mailing lists