| 1 |
On 08/11/2015 08:34 AM, Mike Frysinger wrote: |
| 2 |
> commit: 719cc5ef240b766953ddbe1e7a6593f8091eed12 |
| 3 |
> Author: Mike Frysinger <vapier <AT> gentoo <DOT> org> |
| 4 |
> AuthorDate: Tue Aug 11 06:28:16 2015 +0000 |
| 5 |
> Commit: Mike Frysinger <vapier <AT> gentoo <DOT> org> |
| 6 |
> CommitDate: Tue Aug 11 06:34:22 2015 +0000 |
| 7 |
> URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=719cc5ef |
| 8 |
> |
| 9 |
> microcode-ctl: stop installing the init script |
| 10 |
> |
| 11 |
> Updating microcode on the fly is dangerous as it can modify the set of |
| 12 |
> valid instructions. An active example of this is Intel's TSX insns -- |
| 13 |
> the latest microcode push disables the insn on newer CPUs and causes |
| 14 |
> SIGILL when you try to use it. But if you test for the insn before the |
| 15 |
> microcode is updated, it will execute fine. For daemons that launched |
| 16 |
> before the update, they'll find the flag works, and then crash later on |
| 17 |
> when the insn no longer exists. |
| 18 |
> |
| 19 |
> Thus the only safe way to update microcode is at boot time via a builtin |
| 20 |
> initramfs. Details on this operation can be found in #528712#41. |
| 21 |
> |
| 22 |
|
| 23 |
I've already asked you twice on the ML why you keep ignoring the |
| 24 |
standard we set for the commit message summary and pretty much everyone |
| 25 |
is following except you. |
| 26 |
|
| 27 |
Do you ignore us on purpose? |
Archives