linux-kernel - Re: [PATCH 0/6] x86/microcode: Support for Intel Staging Feature

lists.openwall.net		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 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250228222715.3306015-1-colinmitchell@google.com>
Date: Fri, 28 Feb 2025 14:27:15 -0800
From: Colin Mitchell <colinmitchell@...gle.com>
To: chang.seok.bae@...el.com
Cc: bp@...en8.de, dave.hansen@...ux.intel.com, linux-kernel@...r.kernel.org, 
	mingo@...hat.com, tglx@...utronix.de, x86@...nel.org
Subject: Re: [PATCH 0/6] x86/microcode: Support for Intel Staging Feature

As a potential user, I'd advocate for an option to disable legacy
loading if staging is supported.

The difference in quiesce time between staging and legacy loading
can be significant. Since late loading is more of an explicit active
action, I would believe allowing the initiating process freedom of a retry
loop or handling any errors from staging makes sense.

Presumably load_late_locked could return an error on failure
to stage leading to an appropriate print.