Gentoo Archives: gentoo-dev

From: hasufell <hasufell@g.o>
To: gentoo-dev@l.g.o, Mike Frysinger <vapier@g.o>
Subject: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: sys-apps/microcode-ctl/
Date: Tue, 11 Aug 2015 11:17:25
Message-Id: 55C9D9B6.2080805@gentoo.org
On 08/11/2015 08:34 AM, Mike Frysinger wrote:
> commit: 719cc5ef240b766953ddbe1e7a6593f8091eed12 > Author: Mike Frysinger <vapier <AT> gentoo <DOT> org> > AuthorDate: Tue Aug 11 06:28:16 2015 +0000 > Commit: Mike Frysinger <vapier <AT> gentoo <DOT> org> > CommitDate: Tue Aug 11 06:34:22 2015 +0000 > URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=719cc5ef > > microcode-ctl: stop installing the init script > > Updating microcode on the fly is dangerous as it can modify the set of > valid instructions. An active example of this is Intel's TSX insns -- > the latest microcode push disables the insn on newer CPUs and causes > SIGILL when you try to use it. But if you test for the insn before the > microcode is updated, it will execute fine. For daemons that launched > before the update, they'll find the flag works, and then crash later on > when the insn no longer exists. > > Thus the only safe way to update microcode is at boot time via a builtin > initramfs. Details on this operation can be found in #528712#41. >
I've already asked you twice on the ML why you keep ignoring the standard we set for the commit message summary and pretty much everyone is following except you. Do you ignore us on purpose?

Replies