Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp4386308ybl; Mon, 13 Jan 2020 12:47:26 -0800 (PST) X-Google-Smtp-Source: APXvYqwgXX4J0Lo4gMAyaDLQWAbLDIpBrIJC6EGf+6YY2VNYeF/4MyFy52bo9RnsvD2RZK/iTdxo X-Received: by 2002:a05:6808:1c5:: with SMTP id x5mr14697464oic.57.1578948446104; Mon, 13 Jan 2020 12:47:26 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1578948446; cv=none; d=google.com; s=arc-20160816; b=KbuM42ga0WLkzLO7EbI2lAc6C7i0cuUUuIW8z89tb6q0qx6kWim11DJTjVrBujaolU V3dU8rMc/nulq+Q8Cty57UfdwHHZ/NHZKcka/6yM/58PgwzSiByhoqQlJJPWRWNZ1B6Y T8oTNJqUOxnlNLibnwUA5gTkTaeRo+U1mFP5711Dn1prkOAnjDFUVaBzvToXX2z+tfBw xhEppRhe99tyFNjNLZr3rh4OQkt7Ogg/PYQfDY6GCXuG5OvzFZjZQ0BJ2xyG53ahyy1z UeKqw2miyeW94qI4PdaLnJ5CFiWWNHrd2R1FZB7r/BWMJuA4Fy04i7lIc8tW57k9jDQ8 MOGQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=dW6ZKQ6DQh5kTanDhU2IOHJ1t4Hr6XOG3diwIIiq8mo=; b=rLpr+mchJOOGpbs7Mavx69QGsbWVe1EP7pg0bRSJu7ji0kP3zw6x0BIcs6rX0ZjZ3f J/81E+Rwt23jdsV92id0Dsy2BAj1TsU+r3qKXmqF1VfV6Lk8AIumbGRqv/wAMCRVIqfH dJw/5Q6H+7f1mFLbrKjITpFoU9/eTVypDHmR6tL/cVoF1aV7jNQYkRLuTaTmPbQWBXk3 KNUYH8Lh1bHZxhsex7fguZi0yywa93hGh492fcBnJtMhQkyjZHrHvR793bdO00kUVk0i Mt7r4v1XuSrmSDFG0WxlJELSO+ctJoSfNU++IMmdrgk78rm9kdLn0odeIM0c1MUpH5Eo G6AA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@alien8.de header.s=dkim header.b=a+xBrkWd; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=alien8.de Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w131si5522906oie.47.2020.01.13.12.47.12; Mon, 13 Jan 2020 12:47:26 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@alien8.de header.s=dkim header.b=a+xBrkWd; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=alien8.de Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728641AbgAMUqU (ORCPT + 99 others); Mon, 13 Jan 2020 15:46:20 -0500 Received: from mail.skyhub.de ([5.9.137.197]:49028 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726778AbgAMUqU (ORCPT ); Mon, 13 Jan 2020 15:46:20 -0500 Received: from zn.tnic (p200300EC2F05D300358610FD1FF8C6B9.dip0.t-ipconnect.de [IPv6:2003:ec:2f05:d300:3586:10fd:1ff8:c6b9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id 0B09D1EC0C98; Mon, 13 Jan 2020 21:46:18 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1578948378; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:in-reply-to:in-reply-to: references:references; bh=dW6ZKQ6DQh5kTanDhU2IOHJ1t4Hr6XOG3diwIIiq8mo=; b=a+xBrkWd/Ok0phsODwK9yJv2tgak87EEbk8f2uKdTXwvSMQZV7I00LwmBBwV0ViWpfY6s5 x6xrgiFDXpGp7jH9BYJY9G7zAvw/aVWyXoBHjnJ/PwoHibXXx1MtzPqx26L3SCdbhkv7mQ 0e36SEMCBWjaOLrS8zJhiI+0sDhAI3Y= Date: Mon, 13 Jan 2020 21:46:11 +0100 From: Borislav Petkov To: Jari Ruusu Cc: Luis Chamberlain , Fenghua Yu , Linus Torvalds , johannes.berg@intel.com, linux-kernel@vger.kernel.org, stable@vger.kernel.org Subject: Re: Fix built-in early-load Intel microcode alignment Message-ID: <20200113204611.GS13310@zn.tnic> References: <20200113154739.GB11244@42.do-not-panic.com> <20200113200832.GR13310@zn.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jan 13, 2020 at 10:30:13PM +0200, Jari Ruusu wrote: > On 1/13/20, Borislav Petkov wrote: > > Btw, just out of curiosity: why are you using built-in microcode and not > > the initrd method? > > Initrd method is better when it is a kernel intended to be booted > on many different computers. Built-in microcode method kernel is > tuned for one computer only. It is less hassle that way. Oh well, you only need to do an initrd which is not that big of a deal. The built-in method requires you to rebuild the kernel when there's new microcode but new microcode is a relatively seldom occurrence in practice. The last two years putting my statistics completely out-of-whack. But they should be coming back to normal because there should simply be no more room for microcode patches anymore in the most x86 CPUs out there. :) So if you're building kernels often, it doesn't really matter if you do initrd or builtin microcode. -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette