Commit bfdd5a67 authored by Borislav Petkov's avatar Borislav Petkov
Browse files

x86/asm: Clarify static_cpu_has()'s intended use



Clarify when one should use static_cpu_has() and when one should use
boot_cpu_has().

Requested-by: default avatarNadav Amit <nadav.amit@gmail.com>
Signed-off-by: default avatarBorislav Petkov <bp@suse.de>
Cc: x86@kernel.org
Link: https://lkml.kernel.org/r/20190330112022.28888-2-bp@alien8.de
parent a6cbfbe6
Loading
Loading
Loading
Loading
+6 −3
Original line number Diff line number Diff line
@@ -155,9 +155,12 @@ extern void clear_cpu_cap(struct cpuinfo_x86 *c, unsigned int bit);
#else

/*
 * Static testing of CPU features.  Used the same as boot_cpu_has().
 * These will statically patch the target code for additional
 * performance.
 * Static testing of CPU features. Used the same as boot_cpu_has(). It
 * statically patches the target code for additional performance. Use
 * static_cpu_has() only in fast paths, where every cycle counts. Which
 * means that the boot_cpu_has() variant is already fast enough for the
 * majority of cases and you should stick to using it as it is generally
 * only two instructions: a RIP-relative MOV and a TEST.
 */
static __always_inline bool _static_cpu_has(u16 bit)
{