From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 274CAEB64D7 for ; Wed, 21 Jun 2023 22:58:21 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229595AbjFUW6U (ORCPT ); Wed, 21 Jun 2023 18:58:20 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49674 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229521AbjFUW6S (ORCPT ); Wed, 21 Jun 2023 18:58:18 -0400 Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 595D219AC for ; Wed, 21 Jun 2023 15:58:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1687388297; x=1718924297; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=XyZi0tLe5yLvTI2TlFkR3CvZQjJ1rTFfCx4cp0H2vh8=; b=d1XiKGBVlnE+YZCw2iTCVzpBEeN1+gx+RGBmfveH3vcFoJPimFhYzDBV d3xs9IJZVbrC8WR4qpo63XgSkZJo+TkF1CMKqbtdV4GQRogqcQkt/7dvY sVJAuMB1+HxjTEKhjhdfPdQP1tVQBrJ4FAj6814jTqpB+sT2qI80pwHoH ppAIfdJp08ShgQejIOeGg9/gRsR1y12TMhFP+SdbEg1x2ZxJKetqnR+y7 zuyjG1RJoagAIQ1ftVTV3pBYvHDMKUIxDMhtss0Jn6OFhgtcfUy9vfEFJ r3MmRUCXhsR9E0hz5Ybp9UZxBxf9k/erJB971SeNYrcZ3XVKIACVdyUxI g==; X-IronPort-AV: E=McAfee;i="6600,9927,10748"; a="357825278" X-IronPort-AV: E=Sophos;i="6.00,261,1681196400"; d="scan'208";a="357825278" Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Jun 2023 15:58:16 -0700 X-IronPort-AV: E=McAfee;i="6600,9927,10748"; a="748916643" X-IronPort-AV: E=Sophos;i="6.00,261,1681196400"; d="scan'208";a="748916643" Received: from rmathew-mobl2.amr.corp.intel.com (HELO [10.212.134.235]) ([10.212.134.235]) by orsmga001-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Jun 2023 15:58:10 -0700 Message-ID: <0c908258-2b03-ebb3-bc7d-af5ea66479d4@intel.com> Date: Wed, 21 Jun 2023 15:58:10 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: [PATCH v2] x86/bugs: Break down mitigations configurations Content-Language: en-US To: Breno Leitao Cc: Pawan Gupta , 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)" References: <20230616164851.2559415-1-leitao@debian.org> <20230621001327.qdyebewnx7r5aiy3@desk> <20230621173135.wiprtgzslhw5z5or@desk> <20230621194101.bmwesljror2yqjxx@desk> From: Dave Hansen In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 6/21/23 15:52, Breno Leitao wrote: > On Wed, Jun 21, 2023 at 03:35:45PM -0700, Dave Hansen wrote: >> On 6/21/23 12:41, Pawan Gupta wrote: >>> Yes, a single series (or a patch) that adds config for each mitigation >>> would be good. >> Do people _really_ want per-mitigation compile-time controls? That >> seems like kinda a pain. >> >> I Boris suggested it, but it seems like a _bit_ of overkill to me. >> >> Would a compile-time option that just defaulted _everything_ to >> mitigations=off behavior work instead? That way we don't end up with a >> billion new config options. > This is exactly what my original patch proposed. It solves the problem with > a few lines of changes. > > https://lore.kernel.org/lkml/20230203120615.1121272-1-leitao@debian.org/ Hey Boris, I like this simple thingy better. If for no other reason than it reduces the burden of what we have to do for every _new_ mitigation going forward. Do you like the direction this is going? Maybe I'm missing something.