From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-106118.protonmail.ch (mail-106118.protonmail.ch [79.135.106.118]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 0F88436606C for ; Fri, 20 Mar 2026 12:50:17 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=79.135.106.118 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774011020; cv=none; b=J6QEup2GN89J0Gvo08nrXXTS94HDDYWTjsHppT3Sfds7Dxqu494FL/tog4gG+kTu7wWhL7OG7mzGWobBH6DQ59BqWAQFblmPlVGWAIMk3EJkAJYy92hQBmE2sz2w7oXLKTwhy9uunCDN5/+lDszmNUJXRy9bCUH+FvT9N3ZX1ow= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774011020; c=relaxed/simple; bh=dZwOByJm4bmSNWTgQ0RSvb9nq7wmTs4iFFPZ7SK98pI=; h=Date:To:From:Cc:Subject:Message-ID:MIME-Version:Content-Type; b=FLlkU9UtlbGXcOkmxqD1XiTKpUwmxGvuXGnxl7x+ifpbYL3h1oISuKuKfdtEaNFMqvCVsBZf0dTo4KQgmNxqVwYOxvqVvayGfn271+tpAO1Pi/0pUy+IGNiojwW9n/xGTGEfavENU5nV7v9VLior+fYZMHjY0DzPVIX0RXL6cng= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=pm.me; spf=pass smtp.mailfrom=pm.me; dkim=pass (2048-bit key) header.d=pm.me header.i=@pm.me header.b=CBPsHrLN; arc=none smtp.client-ip=79.135.106.118 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=pm.me Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=pm.me Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=pm.me header.i=@pm.me header.b="CBPsHrLN" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pm.me; s=protonmail3; t=1774011015; x=1774270215; bh=KIRwwGwI/S7qW5Dzvci7x8n4TRqMAfcttPA4mky/Jo0=; h=Date:To:From:Cc:Subject:Message-ID:Feedback-ID:From:To:Cc:Date: Subject:Reply-To:Feedback-ID:Message-ID:BIMI-Selector; b=CBPsHrLNhoRxqEpMMfjI7luF68CuypU650vCvAp7lAvrEE7pUE4g0v59LAMUxr7Kf T8tPo5iTEdWxTIJFLhIxgkn9G4eKhVMwmV0FeAeVnrqudgVP/kkQyKd2mv1lKyqHXV SUiP5XAJxRQdNMlBNqzXi+Go8uSNbBxHxa+GMHXiwwaSYICo6x0nI5JW1c1uPQIIsa AzYdOF/Arh77LXnJFwrhV+SvlMcuVbZLZ4X393qBjo3yOtJaN0R8wNyfYTqvje7JHo GprBsxe0gkC9frT/X5OCo5ZkfBexZew9Uu9nkQF3yGxyIK39MIHYvl4FIcMcYdKRug OJJwgPMY2G5ag== Date: Fri, 20 Mar 2026 12:50:08 +0000 To: tglx@kernel.org, peterz@infradead.org, xin@zytor.com, maciej.wieczor-retman@intel.com, babu.moger@amd.com, chang.seok.bae@intel.com, sohil.mehta@intel.com, dave.hansen@linux.intel.com, jpoimboe@kernel.org, elena.reshetova@intel.com, hpa@zytor.com, pawan.kumar.gupta@linux.intel.com, ak@linux.intel.com, darwi@linutronix.de, bp@alien8.de, mingo@redhat.com From: Maciej Wieczor-Retman Cc: x86@kernel.org, linux-kernel@vger.kernel.org, m.wieczorretman@pm.me Subject: [PATCH v11 0/4] x86: Capability bits fix and required bits sanity check Message-ID: Feedback-ID: 164464600:user:proton X-Pm-Message-ID: dc5cefb8cd30c4d5aa073d3f792b2a0f73ea47c7 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Series aims to fix the inconsistency between the cpuinfo behavior and the documentation. Specifically the features that are not compiled are still present in the cpuinfo bitmasks as enabled. This is not in line with the documentation which specifies that not-compiled features are not present in /proc/cpuinfo. Along adding the disabled feature bitmask initializer array, the complementary required bitmask initializer is also added. It can be used to provide a sanity check, after the cpu identification is finished, to make sure every required bit is set in the final bitmask. A warning with the cpu number and all required bits that were not set is emitted in case of the sanity check failure. Before adding the sanity check a small cleanup can be done. Three places open code an operation that retrieves either a feature string or, if the string is not present, the feature number in word:bit format. One of these places also doesn't check whether the string is actually there or not. The cleanup patch fixes that and simplifies the other two instances. Patches are based on v7.0-rc4 Previous patchset versions: v10: https://lore.kernel.org/all/cover.1773771353.git.m.wieczorretman@pm.me= / v9: https://lore.kernel.org/all/cover.1773165421.git.m.wieczorretman@pm.me= / v8: https://lore.kernel.org/all/cover.1772453012.git.m.wieczorretman@pm.me= / v7: https://lore.kernel.org/all/cover.1771936214.git.m.wieczorretman@pm.me= / v6: https://lore.kernel.org/all/cover.1771590895.git.m.wieczorretman@pm.me= / v5: https://lore.kernel.org/all/cover.1770908783.git.m.wieczorretman@pm.me= / v4: https://lore.kernel.org/all/20250724125346.2792543-1-maciej.wieczor-re= tman@intel.com/ v3: https://lore.kernel.org/all/20250724094554.2153919-1-maciej.wieczor-re= tman@intel.com/ v2: https://lore.kernel.org/all/20250723092250.3411923-1-maciej.wieczor-re= tman@intel.com/ v1: https://lore.kernel.org/all/20250722074439.4069992-1-maciej.wieczor-re= tman@intel.com/ Maciej Wieczor-Retman (4): x86/cpu: Clear feature bits disabled at compile-time x86/cpu: Check if feature string is non-zero x86/cpu: Do a sanity check on required feature bits x86/cpu: Clear feature bits whose dependencies were cleared arch/x86/include/asm/cpufeature.h | 4 ++ arch/x86/kernel/cpu/common.c | 69 +++++++++++++++++++++++++++--- arch/x86/kernel/cpu/cpuid-deps.c | 31 ++++++-------- arch/x86/tools/cpufeaturemasks.awk | 6 +++ 4 files changed, 86 insertions(+), 24 deletions(-) --=20 2.53.0