Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933332AbeAOJ7t (ORCPT + 1 other); Mon, 15 Jan 2018 04:59:49 -0500 Received: from mail.skyhub.de ([5.9.137.197]:42238 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933218AbeAOJ7s (ORCPT ); Mon, 15 Jan 2018 04:59:48 -0500 Date: Mon, 15 Jan 2018 10:59:43 +0100 From: Borislav Petkov To: Jia Zhang Cc: tony.luck@intel.com, mingo@redhat.com, hpa@zytor.com, tglx@linutronix.de, x86@kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/2] x86/microcode/intel: Extend BDW late-loading with platform id and LLC check Message-ID: <20180115095943.mzd3bagx2vqapm34@pd.tnic> References: <1515995003-113069-1-git-send-email-zhang.jia@linux.alibaba.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <1515995003-113069-1-git-send-email-zhang.jia@linux.alibaba.com> User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On Mon, Jan 15, 2018 at 01:43:21PM +0800, Jia Zhang wrote: > The fix further reduces the impact for the BDW model which has to launch > a machine reset in order to run microcode update in BIOS. This point is > important for some vendors without the concern about machine reboot in > order to fix up Spectre v2. That's a ridiculous excuse - those vendors need to reboot to get these fixes first. So what is the real reason? Why can't they simply move to early loading like the rest of the world? So srsly, how many times are we going to fix this erratum? Are you going to come up with yet another fix *after* this one? -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.