3 Jan
2018
3 Jan
'18
20:19
On 03/01/18 19:31, Christopher Myers wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > > > On Wed, 2018-01-03 at 19:45 +0100, Carlos E. R. wrote: >> > On 2018-01-03 17:48, Linda Walsh wrote: >> > >>> > > >>> > > * For good measure, similar software protections will be included >>> > > on 64-bit ARM kernels as well; While AMD chips aren't affected >>> > > by this bug, it's hard to see an update physically-splitting >>> > > (instead of just virtually-splitting) all kernel & user code, >>> > > only being applied against Intel and ARM (i.e. AMD chip-based >>> > > systems >>> > > may likely be affected by the slowdown due to the fix being >>> > > applied >>> > > across 64-bit kernels. >> > >> > AMD has asked the measure not be applied to their processors. >> > > - From AMD's perspective, it would definitely be exasperating to have > your hardware penalized when you didn't screw stuff up... Surely > there's got to be some way to selectively enable the "protections" > based off of CPU model, like there is with other features? You mean, like, compile your own kernels? Actually, from what I've picked up there is a command-line kernel boot option that will disable it even if compiled in. But surely (I've never done it on S(uU)SE), you must be able to download the kernel source package, disable it, and recompile? Cheers, Wol -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org