lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 13 Jun 2018 11:30:02 -0700
From:   Dave Hansen <>
To:     "Kirill A. Shutemov" <>,
        Ingo Molnar <>,,
        Thomas Gleixner <>,
        "H. Peter Anvin" <>,
        Tom Lendacky <>
Cc:     Kai Huang <>,
        Jacob Pan <>,,
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