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 5A3A8C433F5 for ; Wed, 16 Feb 2022 10:30:37 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230401AbiBPKar (ORCPT ); Wed, 16 Feb 2022 05:30:47 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:42724 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230226AbiBPKal (ORCPT ); Wed, 16 Feb 2022 05:30:41 -0500 Received: from mail.skyhub.de (mail.skyhub.de [5.9.137.197]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E99F7222DCE; Wed, 16 Feb 2022 02:30:29 -0800 (PST) Received: from zn.tnic (dslb-088-067-221-104.088.067.pools.vodafone-ip.de [88.67.221.104]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id 5E6C21EC0559; Wed, 16 Feb 2022 11:30:24 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1645007424; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:in-reply-to:in-reply-to: references:references; bh=RnL64jfeuVmEdZEgr3UxSieZSpJyBFpyNCKeJ6KeSjU=; b=j4S8EKR0qVMW6cXab2z1nhlQiSJjKZAar+jxjOt9ZdU2xBlf2z/XVGH4WPK9mGNY+P49hg 64oWlF+u8RJEYfoz7m59p3XTv59vUE479bfonOpd+MaMq4eLN4umdrixUCWMAAXPm8d+2z WfGfcyehvXVKG5bSr4iMZmX0+oNHz6g= Date: Wed, 16 Feb 2022 11:30:31 +0100 From: Borislav Petkov To: Pawan Gupta Cc: Andrew Cooper , Thomas Gleixner , Ingo Molnar , Dave Hansen , "x86@kernel.org" , "H. Peter Anvin" , Andi Kleen , Tony Luck , "linux-kernel@vger.kernel.org" , "antonio.gomez.iglesias@linux.intel.com" , "neelima.krishnan@intel.com" , "stable@vger.kernel.org" Subject: Re: [PATCH] x86/tsx: Use MSR_TSX_CTRL to clear CPUID bits Message-ID: References: <20220215002014.mb7g4y3hfefmyozx@guptapa-mobl1.amr.corp.intel.com> <20220215121103.vhb2lpoygxn3xywy@guptapa-mobl1.amr.corp.intel.com> <20220215181931.wxfsn2a3npg7xmi2@guptapa-mobl1.amr.corp.intel.com> <20220216003950.5jxecuf773g2kuwl@guptapa-mobl1.amr.corp.intel.com> <6724088f-c7cf-da92-e894-d8970f13bf1e@citrix.com> <20220216012841.vxlnugre2j4pczp7@guptapa-mobl1.amr.corp.intel.com> <20220216060826.dwki2jk6kzft4f7c@guptapa-mobl1.amr.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20220216060826.dwki2jk6kzft4f7c@guptapa-mobl1.amr.corp.intel.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Feb 15, 2022 at 10:08:26PM -0800, Pawan Gupta wrote: > Alternatively, we can reset RTM_ALLOW, I'd vote for that. Considering how plagued TSX is, I'm sceptical anyone would be interested in doing development with it so we can reset it for now and allow enabling it later if there's an actual use case for it... Thx. -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette