Return-Path: Received: from mail.linutronix.de (146.0.238.70:993) by crypto-ml.lab.linutronix.de with IMAP4-SSL for ; 15 Feb 2019 13:06:08 -0000 Received: from mga09.intel.com ([134.134.136.24]) by Galois.linutronix.de with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1gudBu-0004z3-03 for speck@linutronix.de; Fri, 15 Feb 2019 14:06:06 +0100 Date: Fri, 15 Feb 2019 05:06:01 -0800 From: Andi Kleen Subject: [MODERATED] Re: [PATCH v5 00/27] MDSv5 19 Message-ID: <20190215130601.GB16922@tassilo.jf.intel.com> References: <20190213223332.GL4516@lindsey> <20190214165355.GM16922@tassilo.jf.intel.com> <20190214180021.GB11103@kroah.com> <20190214183359.GT16922@tassilo.jf.intel.com> <20190214185242.GB19664@kroah.com> <20190214195041.GX16922@tassilo.jf.intel.com> <20190215070613.GF14473@kroah.com> MIME-Version: 1.0 In-Reply-To: <20190215070613.GF14473@kroah.com> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: speck@linutronix.de List-ID: > Slowing the whole kernel down for an ill-defined problem is not ok. You > know that What do you mean by ill defined problem? Are you unclear on the group 4 vulnerabilities? I assume you've seen the disclosures, or is that not correct? Have you read Documentation/clearcpu.txt? There will be some slow down for group 4 mitigations. It's inevitable. These changes don't come for free. We've been spending a lot of work to minimize it, but it won't be zero. -Andi