From owner-freebsd-arch@freebsd.org  Fri Jul 13 23:05:32 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 870E31029989
 for <freebsd-arch@mailman.ysv.freebsd.org>;
 Fri, 13 Jul 2018 23:05:32 +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 24C2F7CC5C;
 Fri, 13 Jul 2018 23:05:32 +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 5909B14816;
 Fri, 13 Jul 2018 23:05:31 +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 w6DN5VMH002747
 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
 Fri, 13 Jul 2018 23:05:31 GMT (envelope-from phk@critter.freebsd.dk)
Received: (from phk@localhost)
 by critter.freebsd.dk (8.15.2/8.15.2/Submit) id w6DN5Upf002746;
 Fri, 13 Jul 2018 23:05:30 GMT (envelope-from phk)
To: Mark Johnston <markj@freebsd.org>
cc: freebsd-arch@freebsd.org
Subject: Re: early x86 microcode loading
In-reply-to: <20180712224631.GF15892@raichu>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
References: <20180712183116.GB15892@raichu>
 <50839.1531428749@critter.freebsd.dk> <20180712224631.GF15892@raichu>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2744.1531523130.1@critter.freebsd.dk>
Date: Fri, 13 Jul 2018 23:05:30 +0000
Message-ID: <2745.1531523130@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: Fri, 13 Jul 2018 23:05:32 -0000

--------
In message <20180712224631.GF15892@raichu>, Mark Johnston writes:

>I can think of three ways to address this case:
>
>1a) Always load all of the updates as a single file, and select the
>    correct update during boot.  As I pointed out, this wastes some
>    memory (a couple of megabytes currently).  On at least amd64 it
>    doesn't look very practical to release the pages backing the
>    update file back to the VM.  That is, I don't think we can easily
>    "shed" the preloaded file data once the correct update has been
>    selected and saved.

Then we should fix that problem, rather than build an elaborate
workaround for in each and every subsystem which runs into this.

Isn't this the same issue with the splash-screen for instance ?

-- 
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.