From: Borislav Petkov <bp@alien8.de>
To: X86 ML <x86@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/3] x86, CPU: Some more cleanups and rearrangements
Date: Tue, 24 Jun 2014 13:25:02 +0200 [thread overview]
Message-ID: <1403609105-8332-1-git-send-email-bp@alien8.de> (raw)
From: Borislav Petkov <bp@suse.de>
Hi,
some more stuff from recently:
01 adds "bugs : " line to /proc/cpuinfo to show for which hw bugs of the
current CPU the kernel knows and possibly applies a workaround.
02 is a bit big but it is basically reorganizing code around and doing
small changes like replacing cpu_has_mp with the dynamic cpu_has call so
that we can remove the former.
03 does that.
Tested on a bunch of AMD and Intel machines.
Borislav Petkov (3):
x86, CPU: Add bug flags to /proc/cpuinfo
x86, AMD: Cleanup init_amd
x86, CPU: Kill cpu_has_mp
arch/x86/include/asm/cpufeature.h | 14 +-
arch/x86/kernel/cpu/amd.c | 339 ++++++++++++++++++--------------------
arch/x86/kernel/cpu/mkcapflags.sh | 51 ++++--
arch/x86/kernel/cpu/proc.c | 8 +
4 files changed, 214 insertions(+), 198 deletions(-)
--
2.0.0
next reply other threads:[~2014-06-24 11:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 11:25 Borislav Petkov [this message]
2014-06-24 11:25 ` [PATCH 1/3] x86, CPU: Add bug flags to /proc/cpuinfo Borislav Petkov
2014-07-14 19:24 ` [tip:x86/cpufeature] x86/cpufeature: Add bug flags to /proc/ cpuinfo tip-bot for Borislav Petkov
2014-06-24 11:25 ` [PATCH 2/3] x86, AMD: Cleanup init_amd Borislav Petkov
2014-07-14 19:24 ` [tip:x86/cpufeature] x86, amd: " tip-bot for Borislav Petkov
2014-06-24 11:25 ` [PATCH 3/3] x86, CPU: Kill cpu_has_mp Borislav Petkov
2014-07-14 19:24 ` [tip:x86/cpufeature] x86, cpu: " tip-bot for Borislav Petkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1403609105-8332-1-git-send-email-bp@alien8.de \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).