From owner-freebsd-arch@freebsd.org  Thu Jul 12 20:52:39 2018
Return-Path: <owner-freebsd-arch@freebsd.org>
Delivered-To: freebsd-arch@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0B7421044E93
 for <freebsd-arch@mailman.ysv.freebsd.org>;
 Thu, 12 Jul 2018 20:52:39 +0000 (UTC)
 (envelope-from phk@critter.freebsd.dk)
Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222])
 by mx1.freebsd.org (Postfix) with ESMTP id 9550D7FDE3;
 Thu, 12 Jul 2018 20:52:38 +0000 (UTC)
 (envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (unknown [192.168.55.3])
 by phk.freebsd.dk (Postfix) with ESMTP id 92C0A14836;
 Thu, 12 Jul 2018 20:52:30 +0000 (UTC)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
 by critter.freebsd.dk (8.15.2/8.15.2) with ESMTPS id w6CKqUgK050841
 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
 Thu, 12 Jul 2018 20:52:30 GMT (envelope-from phk@critter.freebsd.dk)
Received: (from phk@localhost)
 by critter.freebsd.dk (8.15.2/8.15.2/Submit) id w6CKqTTk050840;
 Thu, 12 Jul 2018 20:52:29 GMT (envelope-from phk)
To: Mark Johnston <markj@freebsd.org>
cc: freebsd-arch@freebsd.org
Subject: Re: early x86 microcode loading
In-reply-to: <20180712183116.GB15892@raichu>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
References: <20180712183116.GB15892@raichu>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <50838.1531428749.1@critter.freebsd.dk>
Date: Thu, 12 Jul 2018 20:52:29 +0000
Message-ID: <50839.1531428749@critter.freebsd.dk>
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-arch>,
 <mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch/>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
 <mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jul 2018 20:52:39 -0000

--------
In message <20180712183116.GB15892@raichu>, Mark Johnston writes:

>My plan is to extend cpucontrol(8) to determine the
>correct microcode update for the running system, and have the devcpu-data
>port install the corresponding file to /boot/firmware.

This is problematic when a diskimage is migrated to a different CPU,
only on the second reboot on the new hardware are you certain to
have the correct microcode.

For images which are resurrected on demand on whatever hardware is
available this really problematic.

NB: before anybody misunderstands:  This is not a problem for
guest systems under virtualization - they don't need microcode updates.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.