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 ; 15 Oct 2019 08:01:42 -0000 Received: from p5b06da22.dip0.t-ipconnect.de ([91.6.218.34] helo=nanos) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1iKHm1-0002tV-LL for speck@linutronix.de; Tue, 15 Oct 2019 10:01:41 +0200 Date: Tue, 15 Oct 2019 10:01:40 +0200 (CEST) From: Thomas Gleixner Subject: Re: [PATCH v5 08/11] TAAv5 8 In-Reply-To: Message-ID: References: <20191009131251.GD6616@dhcp22.suse.cz> <20191014210458.GF4957@zn.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: speck@linutronix.de List-ID: On Mon, 14 Oct 2019, speck for Jiri Kosina wrote: > 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." I feared that :) > > 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). The config option is fine. Thanks, tglx