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 ; 03 Oct 2019 11:50:35 -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 1iFzcu-0000NQ-UM for speck@linutronix.de; Thu, 03 Oct 2019 13:50:34 +0200 Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 60E5CAF7B for ; Thu, 3 Oct 2019 11:50:26 +0000 (UTC) Date: Thu, 3 Oct 2019 13:50:00 +0200 (CEST) From: Jiri Kosina Subject: [MODERATED] Re: ***UNCHECKED*** ucode packaging In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: speck@linutronix.de List-ID: On Thu, 3 Oct 2019, speck for Andrew Cooper wrote: > Anyway, customers and management have expressed concerns about the ease > of rolling back microcode versions in the field, to stabilise impacted > systems. As most (all?) distros are shipping intel-ucode as a standard package that can be easily downgraded, is there really any value in trying to solve this outside of standard distro package management system? Thanks, -- Jiri Kosina SUSE Labs