[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <13ba89bb-9df3-6272-96ea-005200c3198f@intel.com>
Date: Wed, 13 Jun 2018 11:30:02 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Ingo Molnar <mingo@...hat.com>, x86@...nel.org,
Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>,
Tom Lendacky <thomas.lendacky@....com>
Cc: 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: [PATCHv3 12/17] x86/mm: Allow to disable MKTME after enumeration
On 06/12/2018 07:39 AM, Kirill A. Shutemov wrote:
> Separate MKTME enumaration from enabling. We need to postpone enabling
> until initialization is complete.
^ enumeration
> The new helper mktme_disable() allows to disable MKTME even if it's
s/to disable/disabling/
> enumerated successfully. MKTME initialization may fail and this
> functionallity allows system to boot regardless of the failure.
What can make it fail?
Powered by blists - more mailing lists