From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.linutronix.de (193.142.43.55:993) by crypto-ml.lab.linutronix.de with IMAP4-SSL for ; 14 Oct 2019 21:31:43 -0000 Received: from mx2.suse.de ([195.135.220.15] helo=mx1.suse.de) by Galois.linutronix.de with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1iK7wL-0007lk-Bb for speck@linutronix.de; Mon, 14 Oct 2019 23:31:42 +0200 Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id B2282B383 for ; Mon, 14 Oct 2019 21:31:35 +0000 (UTC) Date: Mon, 14 Oct 2019 23:31:32 +0200 (CEST) From: Jiri Kosina Subject: [MODERATED] Re: Re: [PATCH v5 08/11] TAAv5 8 In-Reply-To: <20191014210458.GF4957@zn.tnic> Message-ID: References: <20191009131251.GD6616@dhcp22.suse.cz> <20191014210458.GF4957@zn.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: speck@linutronix.de List-ID: On Mon, 14 Oct 2019, speck for Borislav Petkov wrote: > > not everybody (by far) is reading those. If this regressess on a=20 > > handful of platforms, we (together with the OS vendor) could=20 > > probably handle the followup reports, but if it happens all across=20 > > the board, it'd surely be overwhelming, to put it mildly. It'll" > > basically promptly escalate to a support disaster." > > Ok, how about we make it a config option: CONFIG_TSX_DEFAULT_ON > > and we - distro kernels - enable it. Mainline leaves it off. > > Problem solved. > > Hmmm? If noone would strongly object to that config option, I'll happily send a followup patch on top of Pawan's series that'd be adding it (defaulting to 'n', as that appears to be the common consensus for upstream for totally understandable reasons). Otherwise, some distros might just have to flip the default in the sources by non-upstream patch, I am afraid (even though we haven't made it to the point where are are making that decision yet). Thanks, -- Jiri Kosina SUSE Labs