Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp9717062rwd; Wed, 21 Jun 2023 10:51:58 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ4p3uXjqcMWkkbIqrBm8QJVx5FtWBiWVHtaScgOyASuxnthfra1iyZanWEnA6gt7u2zHEsB X-Received: by 2002:a17:90a:8a81:b0:25b:cde2:d9ea with SMTP id x1-20020a17090a8a8100b0025bcde2d9eamr9955329pjn.19.1687369917560; Wed, 21 Jun 2023 10:51:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1687369917; cv=none; d=google.com; s=arc-20160816; b=o3Hb9gPDq4lynlU4Qz7upFFsBqPXKyvSWTDJ9zOG0b62qhAEA90BvZfmC7PDRuB2jo gz/7dNWPXQ3LIoz+a/kcr1aBn//LdYecpg4OwmvKdJHFmRxxmBfwe9WdyzLoCSY/oN0Q ksuDckJh4V6Z6uBHEZrEdTSKgU8he/zGpdYOnZyEWvns0WA7PMj1nTPgJuNU7UWH48SZ 0ctmyM9lVxiJLjqauad54uyvP7z1DjeVBpFtNTxIl5HkM0AwZvidHEZvtAFx7VemI0nK QMX1LXqg4qExCMcsMp/F3xtV3mVywG+JTmXLSoVKX4fS6w042VfHdW3DofsU/HnetI8M g3dw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=M8E3amSdijYLfNtQhTJN/YYkVIR004FzTze3XTiB0WU=; b=l3yI2IQCaCZvf0JXjnLYsgMu7lhO0Cfng6vzeNKRSLcUBwGUNjAI+hEj0vPDDGpLtu Z8Sn0Rf8EK1ww/K4Lm/YN4V53uz3BcR0ocZoIg4lmEG0GSPluvzQNpVCSgR0nDe87cMu nGxkUFn/1HI1w9BVNt43HDfVaBwm9mUcoRk98Wr8glmUUKSyg/1l3SCPc1BjMJMhci2n N2Y5+hxGJuO6xjnFXuZpbt79evtsMqm/CaLm2mjtS0uxwCf2GjhHyp7jAdV+amGIx1sL gQR6ETm6cZVUjt4Rn3MgUVQFA8XPpbFgy4gi+cmDuH6Pru+K+GYnkrwcsq5e7PcmhK6y cn+A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=D0wbsUAW; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id b14-20020a63340e000000b0054fb9698c4esi1919038pga.499.2023.06.21.10.51.45; Wed, 21 Jun 2023 10:51:57 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=D0wbsUAW; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231167AbjFURbq (ORCPT + 99 others); Wed, 21 Jun 2023 13:31:46 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37090 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229448AbjFURbo (ORCPT ); Wed, 21 Jun 2023 13:31:44 -0400 Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8618DE2 for ; Wed, 21 Jun 2023 10:31:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1687368703; x=1718904703; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=kMqvQECyIomaYC4b1lIKJwFmPlmJ/wDvy/xkGjZXTa0=; b=D0wbsUAWVzF7sGkoaaamWRvSGbHfCv/JMymPav2KCE5I504t06zlnD0K TmtgvGgwPnCfphrx8NnRu30U+p1NIEXlgpQlZDBTwD8q2tbTF5lwbvCiE J7KeuPqLWlE/aytIMcpydwmQfHdXCRWDmSB6k68Kc8RC1mXylA24JI4rw ZO5HP4XGGMk59pMvhFgklYO70ajeukK3zlQrLV8UdwJ+mZevJaK+kW5By a+dYFx8oyS9oCKimSOAf696a5E7EWhmui9NyUpUqiW64gfZOzryGdYA+I iHj/wT4xRd9GEWgG22czh5IKG94ANyY23FlEXmDUdZNllAzASsTKoJiyX w==; X-IronPort-AV: E=McAfee;i="6600,9927,10748"; a="357749579" X-IronPort-AV: E=Sophos;i="6.00,261,1681196400"; d="scan'208";a="357749579" Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Jun 2023 10:31:42 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10748"; a="961281789" X-IronPort-AV: E=Sophos;i="6.00,261,1681196400"; d="scan'208";a="961281789" Received: from absteel-mobl1.amr.corp.intel.com (HELO desk) ([10.212.231.126]) by fmsmga006-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Jun 2023 10:31:41 -0700 Date: Wed, 21 Jun 2023 10:31:35 -0700 From: Pawan Gupta To: Breno Leitao Cc: Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , x86@kernel.org, "H. Peter Anvin" , Peter Zijlstra , Josh Poimboeuf , leit@fb.com, "open list:X86 ARCHITECTURE (32-BIT AND 64-BIT)" Subject: Re: [PATCH v2] x86/bugs: Break down mitigations configurations Message-ID: <20230621173135.wiprtgzslhw5z5or@desk> References: <20230616164851.2559415-1-leitao@debian.org> <20230621001327.qdyebewnx7r5aiy3@desk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-4.3 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_NONE, SPF_NONE,T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jun 21, 2023 at 08:54:17AM -0700, Breno Leitao wrote: > On Tue, Jun 20, 2023 at 05:13:27PM -0700, Pawan Gupta wrote: > > On Fri, Jun 16, 2023 at 09:48:50AM -0700, Breno Leitao wrote: > > > There is no way to disable MDS, TAA, MMIO Stale data mitigation today at > > > compilation time. These mitigations are enabled even if > > > CONFIG_SPECULATION_MITIGATIONS is unset. > > > > > > Create a new KCONFIG option for each mitigation under > > > CONFIG_SPECULATION_MITIGATIONS that allows these > > > mitigations to be disabled by default at compilation time. > > > > I don't think all mitigations are still controllable at build-time e.g. > > spectre_v2 eIBRS mitigation will still be deployed irrespective of the > > config. > > Right. This patchset only cares about MDS, TAA and MMIO. I am more than > happy to send a new patch to also disable spectre_v2 eIBRS. What about Retbleed, L1TF, SRBDS etc? I thought the goal is to control all speculation mitigations? To be consistent CONFIG_SPECULATION_MITIGATIONS should control all speculation mitigations.