aboutsummaryrefslogtreecommitdiff
path: root/scripts/gdb/linux/vfs.py
diff options
context:
space:
mode:
authorBorislav Petkov (AMD) <bp@alien8.de>2023-11-15 22:02:12 +0100
committerBorislav Petkov (AMD) <bp@alien8.de>2023-11-21 16:35:48 +0100
commit080990aa3344123673f686cda2df0d1b0deee046 (patch)
treeba025c197fbeed39126c33f188921ee4da1aaf1c /scripts/gdb/linux/vfs.py
parent2e569ada424c40ce27c99bfab4f9780619061c83 (diff)
x86/microcode: Rework early revisions reporting
The AMD side of the loader issues the microcode revision for each logical thread on the system, which can become really noisy on huge machines. And doing that doesn't make a whole lot of sense - the microcode revision is already in /proc/cpuinfo. So in case one is interested in the theoretical support of mixed silicon steppings on AMD, one can check there. What is also missing on the AMD side - something which people have requested before - is showing the microcode revision the CPU had *before* the early update. So abstract that up in the main code and have the BSP on each vendor provide those revision numbers. Then, dump them only once on driver init. On Intel, do not dump the patch date - it is not needed. Reported-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de> Reviewed-by: Thomas Gleixner <tglx@linutronix.de> Link: https://lore.kernel.org/r/CAHk-=wg=%2B8rceshMkB4VnKxmRccVLtBLPBawnewZuuqyx5U=3A@mail.gmail.com
Diffstat (limited to 'scripts/gdb/linux/vfs.py')
0 files changed, 0 insertions, 0 deletions