Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752022AbeAPUur (ORCPT + 1 other); Tue, 16 Jan 2018 15:50:47 -0500 Received: from mail.skyhub.de ([5.9.137.197]:55346 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751071AbeAPUun (ORCPT ); Tue, 16 Jan 2018 15:50:43 -0500 Date: Tue, 16 Jan 2018 21:50:37 +0100 From: Borislav Petkov To: "Luck, Tony" Cc: Jia Zhang , "hmh@hmh.eng.br" , "mingo@redhat.com" , "hpa@zytor.com" , "tglx@linutronix.de" , "x86@kernel.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH v2] x86/microcode/intel: Extend BDW late-loading with LLC size check Message-ID: <20180116205037.lzudhvyymyuxjccu@pd.tnic> References: <1516021917-48335-1-git-send-email-zhang.jia@linux.alibaba.com> <20180115184616.r6pypjegywyd7ncm@pd.tnic> <2ddaecd3-c121-cb37-219e-0e7b1d17c22e@linux.alibaba.com> <3908561D78D1C84285E8C5FCA982C28F7B333F37@FMSMSX154.amr.corp.intel.com> <20180116200149.zffwdbjwj53ba7oj@pd.tnic> <20180116201158.7mu6pj6ynqrfdxe4@agluck-desk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20180116201158.7mu6pj6ynqrfdxe4@agluck-desk> 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 Tue, Jan 16, 2018 at 12:11:58PM -0800, Luck, Tony wrote: > I think so. The erratum (see below) says the problem only occurs > on the large-cache SKUs. So we only need to avoid the update if > we are on a big cache SKU that is also running old microcode. ... and there's not a more reliable way to detect those like platform ID or so? Because if for anywhere, this is where one *should* use platform ID. Or perhaps some other bit somewhere instead of this cache size thing? -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.