Return-Path: Received: from mail.linutronix.de (146.0.238.70:993) by crypto-ml.lab.linutronix.de with IMAP4-SSL for ; 14 Feb 2019 19:50:46 -0000 Received: from mga04.intel.com ([192.55.52.120]) by Galois.linutronix.de with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1guN1x-0000QS-Ce for speck@linutronix.de; Thu, 14 Feb 2019 20:50:45 +0100 Date: Thu, 14 Feb 2019 11:50:41 -0800 From: Andi Kleen Subject: [MODERATED] Re: [PATCH v5 00/27] MDSv5 19 Message-ID: <20190214195041.GX16922@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> MIME-Version: 1.0 In-Reply-To: <20190214185242.GB19664@kroah.com> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: speck@linutronix.de List-ID: > Of course that's not ok. Okay. That's easy to say. No regression anywhere, not even for any ISA driver. But then of course that turned the still relatively simple patchkit into a gigantic boondoggle of all tree driver audits and constant maintenance and education of all driver maintainers. And all to handle lots of drivers which likely nobody uses anyways, or if they use it the device is already so slow that the extra overhead of a CPU flush is in the noise (e.g. cpu flush overhead << PIO access) That's somehow ok. Anyways it's water down the bridge at this point. We already wasted the time doing all of this. But of course it's still to be figured out if any of this can be actually practically backported or be maintained long term. My suspicion is that practical backports will need some form of white listing anyways. -Andi