From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.zytor.com (terminus.zytor.com [198.137.202.136]) (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 351C230FF33 for ; Mon, 23 Mar 2026 19:00:21 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.137.202.136 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774292436; cv=none; b=mO0X7vbiF5GzPrZyTweh9thlG/nJEZoZLfW0lKWX8Yb2a5g46bYhrctGEqEXH86lvF64qrBiL6bpXbEO7bDFKYkeMSjPjGfyRr2EtnhzhbaI8f+R7HyVE18byyDJW2tkKuZXv2CqpfGF3CBOMUE2tW6FdOQmZ6Wor/aegQ1cc0w= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774292436; c=relaxed/simple; bh=LjMLVv0MSYHNYWSCuoE6NNqH3bAfQaHw7UDNAcIjNSc=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=GYgHv59ESlUyPrC6jBwmM6uBjR9CbK+B3nxbtxw6RMZiAAlyOWFvVHv6cBWzh22ZnLvfRY6US8meGdV/ekeXScgHh/2Mfkzvwd/uMsFp2Xi9YSpXBrx2GJ4cVEeUFcDFofKZ9a7xTtObEMxRQS4inREZvh7bZFkgFwmZOekQbFg= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=zytor.com; spf=pass smtp.mailfrom=zytor.com; dkim=pass (2048-bit key) header.d=zytor.com header.i=@zytor.com header.b=NXGGQ06G; arc=none smtp.client-ip=198.137.202.136 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=zytor.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=zytor.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=zytor.com header.i=@zytor.com header.b="NXGGQ06G" Received: from [172.27.2.41] (c-76-133-66-138.hsd1.ca.comcast.net [76.133.66.138]) (authenticated bits=0) by mail.zytor.com (8.18.1/8.17.1) with ESMTPSA id 62NIhtOQ2965728 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Mon, 23 Mar 2026 11:43:55 -0700 DKIM-Filter: OpenDKIM Filter v2.11.0 mail.zytor.com 62NIhtOQ2965728 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zytor.com; s=2026022301; t=1774291436; bh=VP/d5D/vUkD/mrLMTsqddy9gKkvjmbg21v9KWIYUXXo=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=NXGGQ06GPayXExRAVUeObYUy1L00CP1S4mmyRz9RzDK9JLw9BTeQQ4o8BCQqXUtZn wDPUBJq6yXnuHbPYXnUd/+cNQopqohO56gcvaUV7ZaCuVSl7DIPCxL8RbucTlhpdVb btZo1Vvho8ykhXHCyjPnbJqYt9qcs2HvnnsI/0Hmo9dabdG4w2LVP9VDGQi4PGlMp/ Sw3Hvw/rKd2g+wmuzsj4y2Vnd1RHRVw4bffyyX+Urlv+TGdkdlQloaIFBW44Gme0+e 01zfSoEVXZSGrIri9dkz0YUvd4Of95I429segj5Hs91+/O7mV5nQcRT2bDsO38//vE mYTyLgoZDPmnQ== Message-ID: Date: Mon, 23 Mar 2026 11:43:50 -0700 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v11 3/4] x86/cpu: Do a sanity check on required feature bits To: Borislav Petkov , Maciej Wieczor-Retman Cc: 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, pawan.kumar.gupta@linux.intel.com, ak@linux.intel.com, darwi@linutronix.de, mingo@redhat.com, x86@kernel.org, linux-kernel@vger.kernel.org References: <7312c9f2feab8aea4612ed9a1841e8c22f5f69b1.1774008873.git.m.wieczorretman@pm.me> <20260323163145.GGacFq8WW0t2uqZm91@fat_crate.local> <20260323175552.GJacF-qCRDyAuQvDVO@fat_crate.local> Content-Language: en-US, sv-SE From: "H. Peter Anvin" In-Reply-To: <20260323175552.GJacF-qCRDyAuQvDVO@fat_crate.local> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On 2026-03-23 10:55, Borislav Petkov wrote: > > I don't understand. > > We call verify_cpu() in startup_64 in kernel proper too. > > So if anything's missing, it should be added there instead of adding yet > another let's verify features thing... > See my response elsewhere in this thread. -hpa