Date: Fri, 13 Jul 2018 23:05:30 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Mark Johnston <markj@freebsd.org> Cc: freebsd-arch@freebsd.org Subject: Re: early x86 microcode loading Message-ID: <2745.1531523130@critter.freebsd.dk> In-Reply-To: <20180712224631.GF15892@raichu> References: <20180712183116.GB15892@raichu> <50839.1531428749@critter.freebsd.dk> <20180712224631.GF15892@raichu>
next in thread | previous in thread | raw e-mail | index | archive | help
-------- 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2745.1531523130>