From patchwork Thu Sep 8 10:43:33 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Lukas Bulwahn X-Patchwork-Id: 12969919 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 09B8FECAAD5 for ; Thu, 8 Sep 2022 10:43:53 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 77B396B0074; Thu, 8 Sep 2022 06:43:52 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 72C298D0002; Thu, 8 Sep 2022 06:43:52 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 57DF06B0078; Thu, 8 Sep 2022 06:43:52 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0010.hostedemail.com [216.40.44.10]) by kanga.kvack.org (Postfix) with ESMTP id 4B1406B0074 for ; Thu, 8 Sep 2022 06:43:52 -0400 (EDT) Received: from smtpin13.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay09.hostedemail.com (Postfix) with ESMTP id 226F1819EB for ; Thu, 8 Sep 2022 10:43:52 +0000 (UTC) X-FDA: 79888582704.13.4470C47 Received: from mail-wm1-f42.google.com (mail-wm1-f42.google.com [209.85.128.42]) by imf07.hostedemail.com (Postfix) with ESMTP id C593140066 for ; Thu, 8 Sep 2022 10:43:51 +0000 (UTC) Received: by mail-wm1-f42.google.com with SMTP id c2-20020a1c3502000000b003b2973dafb7so1368116wma.2 for ; Thu, 08 Sep 2022 03:43:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=references:in-reply-to:message-id:date:subject:cc:to:from:from:to :cc:subject:date; bh=YcRQWeHsNHudXowYxhzrFSu3g61QameARaQdQJb5lU8=; b=g3G7qs40MLQJX14/onOdc/vwEuCiGg3qlXRS98ERCemYZhBI59bvkmMyGLr09yHXS/ yFosfFbqEKXH3p/CfgCOl/rnQhKEtFaDJTjdwAl2E9NoJNZ8YIVubxdleDB/f0g4+3oo JIeGMlGuo3uFUW4fDwCEy9M1RHT2k/t4jVo48Ln/eFseeN1oVe9bh0vMtHB5XTVOMXlQ BfukHii/KG8jzkRD5yeoihVnAl+O4D3cCY+SL/5O/X6oM9T0JNIC31tvygvv5sDkdBMp C81T8fKmjXFOmCxs6csbtglXCTBnAX8JxPtOwKgLbEgviTauwuYqLNDYQ4p+gnFdpP+i HV8g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=references:in-reply-to:message-id:date:subject:cc:to:from :x-gm-message-state:from:to:cc:subject:date; bh=YcRQWeHsNHudXowYxhzrFSu3g61QameARaQdQJb5lU8=; b=ZOFl7E90CfeIzcQHtJThIthAI8JoQk94Xbj6jSj4w2t5+/VPwXXyf64aXsQ3LbU4On FzB8qHim6BDouu2SDIhYXJeGexUu1EMuR5Ia/fKnUZuZ6rhs5iSjqLI5OCzz2LXkdjcT hSfBbZBISiZqazZTq3quYtdjSzv2nrI9ZQNR7YwqrB1LbariGNDWcaN2qZzaskGHkA+1 p7vmGbBmfJznQ5p2QNstLtj2o2wjRAmHGC89+x/7mRICaJZz6Z7oj0X3mvrOHOTLT2Pr m5YegvLN6eXYoqv6XIDOYCqLfSlCpKXfWBdftW3nAr9a1eOyin0G4e5+xwEu7zm7AvbD EItg== X-Gm-Message-State: ACgBeo1HUxH5EW4KU+KzCpzEdGzP3EUCRjUWfPrfkmdvbsztv14+ieBJ Ux2pDymEEpL0Cx/Srkkpxho= X-Google-Smtp-Source: AA6agR6ynOlAaxihPYz+CdT04VP+VpGksNMzS5VFetSq0N8fvehilNxf41zef99BhDZbNdGwjrNtVg== X-Received: by 2002:a05:600c:4f10:b0:3a5:f8c8:a5b5 with SMTP id l16-20020a05600c4f1000b003a5f8c8a5b5mr1835323wmq.34.1662633830474; Thu, 08 Sep 2022 03:43:50 -0700 (PDT) Received: from felia.fritz.box (200116b826f77600d0640cc051af4288.dip.versatel-1u1.de. [2001:16b8:26f7:7600:d064:cc0:51af:4288]) by smtp.gmail.com with ESMTPSA id bu3-20020a056000078300b0022863395912sm17227486wrb.53.2022.09.08.03.43.49 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 08 Sep 2022 03:43:50 -0700 (PDT) From: Lukas Bulwahn To: Russell King , linux-arm-kernel@lists.infradead.org, Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , x86@kernel.org, Mauro Carvalho Chehab , linux-media@vger.kernel.org, Peter Chen , Greg Kroah-Hartman , linux-usb@vger.kernel.org, Andrew Morton , Mike Rapoport , linux-mm@kvack.org, Masahiro Yamada , linux-kbuild@vger.kernel.org Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org, Lukas Bulwahn Subject: [PATCH 2/6] x86: make config X86_FEATURE_NAMES visible with EXPERT Date: Thu, 8 Sep 2022 12:43:33 +0200 Message-Id: <20220908104337.11940-3-lukas.bulwahn@gmail.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20220908104337.11940-1-lukas.bulwahn@gmail.com> References: <20220908104337.11940-1-lukas.bulwahn@gmail.com> ARC-Authentication-Results: i=1; imf07.hostedemail.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=g3G7qs40; spf=pass (imf07.hostedemail.com: domain of lukas.bulwahn@gmail.com designates 209.85.128.42 as permitted sender) smtp.mailfrom=lukas.bulwahn@gmail.com; dmarc=pass (policy=none) header.from=gmail.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1662633831; a=rsa-sha256; cv=none; b=IAtdiYcokRVCb3YKH055AC+PE7cl36QgHiFudAclFVh7EsvmoA1EFARPWAsI4ZTVLT1fZ0 IGUdJkpzibXF9sEI9NO4PdVS9mG+7bJR51g/BbAwCqUt5weRVJECkd4L9v0eGr72m7Rfpg woZrKsb+4DFavlluJtu70YC5UnABsz8= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1662633831; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:content-type: content-transfer-encoding:in-reply-to:in-reply-to: references:references:dkim-signature; bh=YcRQWeHsNHudXowYxhzrFSu3g61QameARaQdQJb5lU8=; b=OhAGJdUYF92cAshsUB+zj7a/hMK5smN6asEN+7+qde/ilC5yj9/FVZmtf0fW8kcnn4oONv kmWxpEFCJitLY7PUzTfArpd2adx/EF890docAiTDk2zcI1ZA+8GPUMq3uvl46wxcelXtCL tmw2VdAWeubZTxEg93x70fGyqfuONaA= X-Rspamd-Server: rspam08 X-Rspamd-Queue-Id: C593140066 Authentication-Results: imf07.hostedemail.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=g3G7qs40; spf=pass (imf07.hostedemail.com: domain of lukas.bulwahn@gmail.com designates 209.85.128.42 as permitted sender) smtp.mailfrom=lukas.bulwahn@gmail.com; dmarc=pass (policy=none) header.from=gmail.com X-Stat-Signature: umdeouukzf7axc4rx5kbgcqo6jsetjo9 X-Rspam-User: X-HE-Tag: 1662633831-903090 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: Commit 6a108a14fa35 ("kconfig: rename CONFIG_EMBEDDED to CONFIG_EXPERT") introduces CONFIG_EXPERT to carry the previous intent of CONFIG_EMBEDDED and just gives that intent a much better name. That has been clearly a good and long overdue renaming, and it is clearly an improvement to the kernel build configuration that has shown to help managing the kernel build configuration in the last decade. However, rather than bravely and radically just deleting CONFIG_EMBEDDED, this commit gives CONFIG_EMBEDDED a new intended semantics, but keeps it open for future contributors to implement that intended semantics: A new CONFIG_EMBEDDED option is added that automatically selects CONFIG_EXPERT when enabled and can be used in the future to isolate options that should only be considered for embedded systems (RISC architectures, SLOB, etc). Since then, this CONFIG_EMBEDDED implicitly had two purposes: - It can make even more options visible beyond what CONFIG_EXPERT makes visible. In other words, it may introduce another level of enabling the visibility of configuration options: always visible, visible with CONFIG_EXPERT and visible with CONFIG_EMBEDDED. - Set certain default values of some configurations differently, following the assumption that configuring a kernel build for an embedded system generally starts with a different set of default values compared to kernel builds for all other kind of systems. Considering the first purpose, at the point in time where CONFIG_EMBEDDED was renamed to CONFIG_EXPERT, CONFIG_EXPERT already made 130 more options become visible throughout all different menus for the kernel configuration. Over the last decade, this has gradually increased, so that currently, with CONFIG_EXPERT, roughly 170 more options become visible throughout all different menus for the kernel configuration. In comparison, currently with CONFIG_EMBEDDED enabled, just seven more options are visible, one in x86, one in arm, and five for the ChipIdea Highspeed Dual Role Controller. As the numbers suggest, these two levels of enabling the visibility of even more configuration options---beyond what CONFIG_EXPERT enables---never evolved to a good solution in the last decade. In other words, this additional level of visibility of configuration option with CONFIG_EMBEDDED compared to CONFIG_EXPERT has since its introduction never become really valuable. It requires quite some investigation to actually understand what is additionally visible and it does not differ significantly in complexity compared to just enabling CONFIG_EXPERT. This CONFIG_EMBEDDED---or any other config to show more detailed options beyond CONFIG_EXPERT---is unlikely to be valuable unless somebody puts significant effort in identifying how such visibility options can be properly split and creating clear criteria, when some config option is visible with CONFIG_EXPERT and when some config option is visible only with some further option enabled beyond CONFIG_EXPERT, such as CONFIG_EMBEDDED attempted to do. For now, it is much more reasonable to simply make those additional seven options that visible with CONFIG_EMBEDDED, visible with CONFIG_EXPERT, and then remove CONFIG_EMBEDDED. If anyone spends significant effort in structuring the visibility of config options, they may re-introduce suitable new config options simply as they see fit. Make the config X86_FEATURE_NAMES visible when CONFIG_EXPERT is enabled. Signed-off-by: Lukas Bulwahn Reviewed-by: Masahiro Yamada --- arch/x86/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig index 2ec0b1eabe86..7807eb1c8df8 100644 --- a/arch/x86/Kconfig +++ b/arch/x86/Kconfig @@ -438,7 +438,7 @@ config SMP If you don't know what to do here, say N. config X86_FEATURE_NAMES - bool "Processor feature human-readable names" if EMBEDDED + bool "Processor feature human-readable names" if EXPERT default y help This option compiles in a table of x86 feature bits and corresponding