From: Jakub Kicinski <kuba@kernel.org>
To: pbonzini@redhat.com
Cc: seanjc@google.com, workflows@vger.kernel.org,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Jakub Kicinski <kuba@kernel.org>
Subject: [PATCH] KVM: deprecate KVM_WERROR in favor of general WERROR
Date: Fri, 6 Oct 2023 13:54:15 -0700 [thread overview]
Message-ID: <20231006205415.3501535-1-kuba@kernel.org> (raw)
Setting WERROR for random subsystems make life really hard
for subsystems which want to build-test their stuff with W=1.
WERROR for the entire kernel now exists and can be used
instead. W=1 people probably know how to deal with the global
W=1 already, tracking all per-subsystem WERRORs is too much...
Link: https://lore.kernel.org/all/0da9874b6e9fcbaaa5edeb345d7e2a7c859fc818.1696271334.git.thomas.lendacky@amd.com/
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
---
Documentation/process/maintainer-kvm-x86.rst | 2 +-
arch/x86/kvm/Kconfig | 14 --------------
arch/x86/kvm/Makefile | 1 -
3 files changed, 1 insertion(+), 16 deletions(-)
diff --git a/Documentation/process/maintainer-kvm-x86.rst b/Documentation/process/maintainer-kvm-x86.rst
index 9183bd449762..cd70c0351108 100644
--- a/Documentation/process/maintainer-kvm-x86.rst
+++ b/Documentation/process/maintainer-kvm-x86.rst
@@ -243,7 +243,7 @@ context and disambiguate the reference.
Testing
-------
At a bare minimum, *all* patches in a series must build cleanly for KVM_INTEL=m
-KVM_AMD=m, and KVM_WERROR=y. Building every possible combination of Kconfigs
+KVM_AMD=m, and WERROR=y. Building every possible combination of Kconfigs
isn't feasible, but the more the merrier. KVM_SMM, KVM_XEN, PROVE_LOCKING, and
X86_64 are particularly interesting knobs to turn.
diff --git a/arch/x86/kvm/Kconfig b/arch/x86/kvm/Kconfig
index ed90f148140d..12929324ac3e 100644
--- a/arch/x86/kvm/Kconfig
+++ b/arch/x86/kvm/Kconfig
@@ -63,20 +63,6 @@ config KVM
If unsure, say N.
-config KVM_WERROR
- bool "Compile KVM with -Werror"
- # KASAN may cause the build to fail due to larger frames
- default y if X86_64 && !KASAN
- # We use the dependency on !COMPILE_TEST to not be enabled
- # blindly in allmodconfig or allyesconfig configurations
- depends on KVM
- depends on (X86_64 && !KASAN) || !COMPILE_TEST
- depends on EXPERT
- help
- Add -Werror to the build flags for KVM.
-
- If in doubt, say "N".
-
config KVM_INTEL
tristate "KVM for Intel (and compatible) processors support"
depends on KVM && IA32_FEAT_CTL
diff --git a/arch/x86/kvm/Makefile b/arch/x86/kvm/Makefile
index 80e3fe184d17..8e6afde7c680 100644
--- a/arch/x86/kvm/Makefile
+++ b/arch/x86/kvm/Makefile
@@ -1,7 +1,6 @@
# SPDX-License-Identifier: GPL-2.0
ccflags-y += -I $(srctree)/arch/x86/kvm
-ccflags-$(CONFIG_KVM_WERROR) += -Werror
ifeq ($(CONFIG_FRAME_POINTER),y)
OBJECT_FILES_NON_STANDARD_vmenter.o := y
--
2.41.0
next reply other threads:[~2023-10-06 20:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 20:54 Jakub Kicinski [this message]
2023-10-09 17:18 ` [PATCH] KVM: deprecate KVM_WERROR in favor of general WERROR Kees Cook
2023-10-09 17:43 ` Sean Christopherson
2023-10-09 18:06 ` Jakub Kicinski
2023-10-09 19:33 ` Sean Christopherson
2023-10-09 21:49 ` Jakub Kicinski
2023-10-10 8:04 ` Jani Nikula
2023-10-10 14:23 ` Jakub Kicinski
2023-10-10 23:46 ` Sean Christopherson
2023-10-12 15:17 ` Paolo Bonzini
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=20231006205415.3501535-1-kuba@kernel.org \
--to=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=workflows@vger.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 read-only IMAP folder(s) and NNTP newsgroup(s).