From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mx2.suse.de ([195.135.220.15]) by Galois.linutronix.de with esmtps (TLS1.0:DHE_RSA_CAMELLIA_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1fCt3I-00038S-M2 for speck@linutronix.de; Sun, 29 Apr 2018 22:36:11 +0200 Received: from relay2.suse.de (charybdis-ext.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 98370AE90 for ; Sun, 29 Apr 2018 20:36:02 +0000 (UTC) Date: Sun, 29 Apr 2018 22:35:42 +0200 From: Borislav Petkov Subject: [MODERATED] Re: [patch V7 00/15] SBB 0 Message-ID: <20180429203542.GC19814@pd.tnic> References: <20180429193045.711908246@linutronix.de> MIME-Version: 1.0 In-Reply-To: <20180429193045.711908246@linutronix.de> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable To: speck@linutronix.de List-ID: On Sun, Apr 29, 2018 at 09:30:45PM +0200, speck for Thomas Gleixner wrote: > This is an update based on Konrads V6 series. The major changes are: >=20 > - Distangle the mitigation control from the AMD/Intel cpu init code and > keep it confined to bugs.c. That's cleaner and required to make the > prctl mode work properly on both AMD and Intel >=20 > - Avoid parsing the command line when RDS is not supported at all. >=20 > - Make all the spec ctrl msr related variables __ro_after_init instead of > read_mostly. Nothing can fiddle with them after boot. >=20 > - Integrate the PRCTL: Ok, now that we have this "fancy" contraption I haz a question: how are programs supposed to use it which are closed source? Or such which can't be recompiled? Are people supposed to do wrappers or are we saying, tough luck to those who can't change their applications? Thx. --=20 Regards/Gruss, Boris. SUSE Linux GmbH, GF: Felix Imend=C3=B6rffer, Jane Smithard, Graham Norton, HR= B 21284 (AG N=C3=BCrnberg) --=20