From: torvic9@mailbox.org
To: "tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>
Subject: [PATCH] arch/x86: Makefile: Move CPU-specific tuning for x86_64 to Makefile.cpu
Date: Wed, 17 Aug 2022 10:40:59 +0200 (CEST) [thread overview]
Message-ID: <300453780.239457.1660725659957@office.mailbox.org> (raw)
The Makefile has a 'FIXME', according to which the CPU-specific tuning
options for 64-bit CPUs should be integrated into a separate file.
Move these cflags to a new file named Makefile.cpu in the same way as for
the 32-bit cflags.
There should be no functional change.
Signed-off-by: Tor Vic <torvic9@mailbox.org>
---
arch/x86/Makefile | 8 ++------
arch/x86/Makefile.cpu | 8 ++++++++
2 files changed, 10 insertions(+), 6 deletions(-)
create mode 100644 arch/x86/Makefile.cpu
diff --git a/arch/x86/Makefile b/arch/x86/Makefile
index 7854685c5f25..c0b4db692544 100644
--- a/arch/x86/Makefile
+++ b/arch/x86/Makefile
@@ -147,12 +147,8 @@ else
# Use -mskip-rax-setup if supported.
KBUILD_CFLAGS += $(call cc-option,-mskip-rax-setup)
- # FIXME - should be integrated in Makefile.cpu (Makefile_32.cpu)
- cflags-$(CONFIG_MK8) += -march=k8
- cflags-$(CONFIG_MPSC) += -march=nocona
- cflags-$(CONFIG_MCORE2) += -march=core2
- cflags-$(CONFIG_MATOM) += -march=atom
- cflags-$(CONFIG_GENERIC_CPU) += -mtune=generic
+ # CPU-specific tuning for x86_64
+ include $(srctree)/arch/x86/Makefile.cpu
KBUILD_CFLAGS += $(cflags-y)
KBUILD_CFLAGS += -mno-red-zone
diff --git a/arch/x86/Makefile.cpu b/arch/x86/Makefile.cpu
new file mode 100644
index 000000000000..6995353f87e8
--- /dev/null
+++ b/arch/x86/Makefile.cpu
@@ -0,0 +1,8 @@
+# SPDX-License-Identifier: GPL-2.0
+# CPU tuning section for x86_64
+
+cflags-$(CONFIG_MK8) += -march=k8
+cflags-$(CONFIG_MPSC) += -march=nocona
+cflags-$(CONFIG_MCORE2) += -march=core2
+cflags-$(CONFIG_MATOM) += -march=atom
+cflags-$(CONFIG_GENERIC_CPU) += -mtune=generic
--
2.37.2
reply other threads:[~2022-08-17 8:41 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=300453780.239457.1660725659957@office.mailbox.org \
--to=torvic9@mailbox.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®