From: Rene Rebe <rene@exactcode.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] add missing MPSC to X86_INTEL_USERCOPY and _USE_PPRO_CHECKSUM
Date: Wed, 27 Jan 2021 19:08:23 +0100 (CET) [thread overview]
Message-ID: <20210127.190823.1013816968702108983.rene@exactcode.com> (raw)
Debugging some bizare memory corruption in certain kernel configs on
some machines, I noticed MPSC (1st gen Intel X64 Nocona) is missing in
selecting X86_INTEL_USERCOPY and X86_USE_PPRO_CHECKSUM. Unless someone
has a good reason not to, I think MPSC should select the two, and
maybe MATOM should also made select X86_INTEL_USERCOPY?
Signed-of-by: René Rebe <rene@exactcode.de>
--- linux-5.10/arch/x86/Kconfig.cpu.vanilla 2021-01-27 16:09:20.163930078 +0100
+++ linux-5.10/arch/x86/Kconfig.cpu 2021-01-27 16:36:35.064014421 +0100
@@ -336,11 +336,11 @@
config X86_INTEL_USERCOPY
def_bool y
- depends on MPENTIUM4 || MPENTIUMM || MPENTIUMIII || MPENTIUMII || M586MMX || X86_GENERIC || MK8 || MK7 || MEFFICEON || MCORE2
+ depends on MPENTIUM4 || MPENTIUMM || MPENTIUMIII || MPENTIUMII || M586MMX || X86_GENERIC || MK8 || MK7 || MEFFICEON || MCORE2 || MPSC
config X86_USE_PPRO_CHECKSUM
def_bool y
- depends on MWINCHIP3D || MWINCHIPC6 || MCYRIXIII || MK7 || MK6 || MPENTIUM4 || MPENTIUMM || MPENTIUMIII || MPENTIUMII || M686 || MK8 || MVIAC3_2 || MVIAC7 || MEFFICEON || MGEODE_LX || MCORE2 || MATOM
+ depends on MWINCHIP3D || MWINCHIPC6 || MCYRIXIII || MK7 || MK6 || MPENTIUM4 || MPENTIUMM || MPENTIUMIII || MPENTIUMII || M686 || MK8 || MVIAC3_2 || MVIAC7 || MEFFICEON || MGEODE_LX || MCORE2 || MATOM || MPSC
config X86_USE_3DNOW
def_bool y
--
René Rebe, ExactCODE GmbH, Lietzenburger Str. 42, DE-10789 Berlin
https://exactcode.com | https://t2sde.org | https://rene.rebe.de
reply other threads:[~2021-01-27 18:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210127.190823.1013816968702108983.rene@exactcode.com \
--to=rene@exactcode.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).