{"id":469066,"date":"2026-05-31T11:20:08","date_gmt":"2026-05-31T11:20:08","guid":{"rendered":"https:\/\/www.newsbeep.com\/il\/469066\/"},"modified":"2026-05-31T11:20:08","modified_gmt":"2026-05-31T11:20:08","slug":"linux-7-1-rc6-to-hide-the-documentation-on-clearcpuid-feature","status":"publish","type":"post","link":"https:\/\/www.newsbeep.com\/il\/469066\/","title":{"rendered":"Linux 7.1-rc6 To Hide The Documentation On &#8220;clearcpuid&#8221; Feature"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" alt=\"LINUX KERNEL\" src=\"https:\/\/www.phoronix.com\/assets\/categories\/linuxkernel.webp\" width=\"100\" height=\"100\"\/><br \/>\nThe clearcpuid= kernel parameter can be used to disable specific CPUID features for the kernel by specifying the targeted bit numbers of the feature(s) to disable or their flags from the \/proc\/cpuinfo output. The clearcpuid parameter, for example, has been useful for <a href=\"https:\/\/www.phoronix.com\/review\/amd-strix-halo-avx512\" rel=\"nofollow noopener\" target=\"_blank\">carrying out AVX-512 comparison benchmarks<\/a> for apps that check for the presence of the AVX-512 extensions via \/proc\/cpuinfo. But moving forward the documentation on clearcpuid is being removed to discourage its use.<\/p>\n<p>The main problem with clearcpuid is that it only disables the CPUID feature for the kernel and that user-space applications calling CPUID directly or attempting to use the feature without any checks can still make use of any CPUID feature cleared by clearcpuid=. It&#8217;s also possible to get the Linux kernel to malfunction if trying to disable some critical CPU features.&#13;<\/p>\n<p align=\"center\"><img decoding=\"async\" src=\"https:\/\/www.newsbeep.com\/il\/wp-content\/uploads\/2026\/05\/1780226408_349_image.webp\" alt=\"CPUs\"\/><\/p>\n<p>So to avoid situations of users not taking into account these complications with clearcpuid=, the kernel documentation on it is being removed and replaced with:<br \/>\n<br \/>&#8220;DO NOT USE this cmdline option in production &#8211; it is meant to be used only as a quick&#8217;n&#8217;dirty debugging aid to rule out a feature-enabling code is the culprit. If you use it, it&#8217;ll taint the kernel.&#8221;<br \/>\n<br \/>Borislav Petkov of AMD further added in <a href=\"https:\/\/git.kernel.org\/pub\/scm\/linux\/kernel\/git\/tip\/tip.git\/commit\/?h=x86\/urgent&amp;id=80501dff814eeccebf44a59340c3fe3a205eb120\" rel=\"nofollow noopener\" target=\"_blank\">the documentation patch<\/a>:<br \/>\n<br \/>&#8220;Remove its documentation so that it doesn&#8217;t get used in production and people get silly ideas. It is meant strictly for debugging; and if a chicken bit for properly disabling a feature is warranted, then that would need proper enablement.&#8221;<br \/>\n<br \/>That documentation removal is slated to happen today in Linux Git with <a href=\"https:\/\/lore.kernel.org\/lkml\/ahvbGCYlJ_x3f8XQ@gmail.com\/\" rel=\"nofollow noopener\" target=\"_blank\">this pull request<\/a> ahead of the Linux 7.1-rc6 tagging. The clearcpuid= functionality is sticking around, you just won&#8217;t find it documented anymore.<\/p>\n","protected":false},"excerpt":{"rendered":"The clearcpuid= kernel parameter can be used to disable specific CPUID features for the kernel by specifying the&hellip;\n","protected":false},"author":2,"featured_media":469067,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[78437,85,46,78436,78434,78433,78440,78438,78435,78439,78432,78443,125,78441,78442],"class_list":["post-469066","post","type-post","status-publish","format-standard","has-post-thumbnail","category-technology","tag-desktop-linux","tag-il","tag-israel","tag-linux-benchmarking","tag-linux-hardware-benchmarks","tag-linux-hardware-reviews","tag-linux-how-to","tag-linux-performance","tag-linux-server-benchmarks","tag-open-source-graphics","tag-phoronix","tag-phoronix-test-suite","tag-technology","tag-ubuntu-benchmarks","tag-ubuntu-hardware"],"_links":{"self":[{"href":"https:\/\/www.newsbeep.com\/il\/wp-json\/wp\/v2\/posts\/469066","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.newsbeep.com\/il\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.newsbeep.com\/il\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/il\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/il\/wp-json\/wp\/v2\/comments?post=469066"}],"version-history":[{"count":0,"href":"https:\/\/www.newsbeep.com\/il\/wp-json\/wp\/v2\/posts\/469066\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/il\/wp-json\/wp\/v2\/media\/469067"}],"wp:attachment":[{"href":"https:\/\/www.newsbeep.com\/il\/wp-json\/wp\/v2\/media?parent=469066"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.newsbeep.com\/il\/wp-json\/wp\/v2\/categories?post=469066"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.newsbeep.com\/il\/wp-json\/wp\/v2\/tags?post=469066"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}