summaryrefslogtreecommitdiffstats
path: root/arch/x86/um
diff options
context:
space:
mode:
authorYury Norov <yury.norov@gmail.com>2021-08-14 14:17:00 -0700
committerYury Norov <yury.norov@gmail.com>2022-01-15 08:47:31 -0800
commitc126a53c276048125b4a950072bab37ad0fea120 (patch)
treea6afa48b9c781a8558ff7cfec59c2f617fd43991 /arch/x86/um
parent47d8c15615c0a2046d2d90b04cb80b81ddf31fb1 (diff)
downloadlinux-stable-c126a53c276048125b4a950072bab37ad0fea120.tar.gz
linux-stable-c126a53c276048125b4a950072bab37ad0fea120.tar.bz2
linux-stable-c126a53c276048125b4a950072bab37ad0fea120.zip
arch: remove GENERIC_FIND_FIRST_BIT entirely
In 5.12 cycle we enabled GENERIC_FIND_FIRST_BIT config option for ARM64 and MIPS. It increased performance and shrunk .text size; and so far I didn't receive any negative feedback on the change. https://lore.kernel.org/linux-arch/20210225135700.1381396-1-yury.norov@gmail.com/ Now I think it's a good time to switch all architectures to use find_{first,last}_bit() unconditionally, and so remove corresponding config option. The patch does't introduce functioal changes for arc, arm, arm64, mips, m68k, s390 and x86, for other architectures I expect improvement both in performance and .text size. Signed-off-by: Yury Norov <yury.norov@gmail.com> Tested-by: Alexander Lobakin <alobakin@pm.me> (mips) Reviewed-by: Alexander Lobakin <alobakin@pm.me> (mips) Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> Acked-by: Will Deacon <will@kernel.org> Tested-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Diffstat (limited to 'arch/x86/um')
-rw-r--r--arch/x86/um/Kconfig1
1 files changed, 0 insertions, 1 deletions
diff --git a/arch/x86/um/Kconfig b/arch/x86/um/Kconfig
index 95d26a69088b..40d6a06e41c8 100644
--- a/arch/x86/um/Kconfig
+++ b/arch/x86/um/Kconfig
@@ -8,7 +8,6 @@ endmenu
config UML_X86
def_bool y
- select GENERIC_FIND_FIRST_BIT
config 64BIT
bool "64-bit kernel" if "$(SUBARCH)" = "x86"