From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751406AbdGRHmb (ORCPT ); Tue, 18 Jul 2017 03:42:31 -0400 Received: from mail.skyhub.de ([5.9.137.197]:43100 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751336AbdGRHma (ORCPT ); Tue, 18 Jul 2017 03:42:30 -0400 Date: Tue, 18 Jul 2017 09:42:17 +0200 From: Borislav Petkov To: Dominik Brodowski Cc: X86 ML , LKML Subject: Re: [PATCH] x86/microcode: Document the three loading methods Message-ID: <20170718074217.GA8372@nazgul.tnic> References: <20170717094328.29966-1-bp@alien8.de> <20170718062754.GA12057@isilmar-4.linta.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20170718062754.GA12057@isilmar-4.linta.de> User-Agent: Mutt/1.6.0 (2016-04-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jul 18, 2017 at 08:27:54AM +0200, Dominik Brodowski wrote: > What about: "... microcode in (uncompressed) cpio format followed by the > (possibly compressed) initrd image", to clarify this distinction? Meh. > What about something more fancy, such as > iucode_tool -v /lib/firmware/intel-ucode/ -S $DSTDIR/GenuineIntel.bin > ? Why, because fancy is better? And simple is not good enough? The less we rely on special tools for kernel stuff, the better. > Maybe specify here that this works using the firmware infrastructure, > therefore the microcode will be loaded from /lib/firmware/ ? Basically the > same terms apply for this method as for the builtin microcode you describe > next. The distro package already installs it into /lib/firmware but ok, I'll note the path explicitly. Thx. -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply. --