diff options
author | Borislav Petkov <[email protected]> | 2017-10-12 13:23:16 +0200 |
---|---|---|
committer | Ingo Molnar <[email protected]> | 2017-10-14 12:55:40 +0200 |
commit | 1f161f67a272cc4f29f27934dd3f74cb657eb5c4 (patch) | |
tree | 96b6ed193be5696b37ed9f012aa275155681713c /tools/perf/scripts/python/export-to-postgresql.py | |
parent | b956575bed91ecfb136a8300742ecbbf451471ab (diff) |
x86/microcode: Do the family check first
On CPUs like AMD's Geode, for example, we shouldn't even try to load
microcode because they do not support the modern microcode loading
interface.
However, we do the family check *after* the other checks whether the
loader has been disabled on the command line or whether we're running in
a guest.
So move the family checks first in order to exit early if we're being
loaded on an unsupported family.
Reported-and-tested-by: Sven Glodowski <[email protected]>
Signed-off-by: Borislav Petkov <[email protected]>
Cc: <[email protected]> # 4.11..
Cc: Linus Torvalds <[email protected]>
Cc: Peter Zijlstra <[email protected]>
Cc: Thomas Gleixner <[email protected]>
Link: http://bugzilla.suse.com/show_bug.cgi?id=1061396
Link: http://lkml.kernel.org/r/[email protected]
Signed-off-by: Ingo Molnar <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions