5 ms·
I've heard back from AMD.... At least this PR person is saying: . “Disabling branch prediction” is definitely not an accurate description and we are working to
by taspeotis 9y ago
I've heard back from AMD.... At least this PR person is saying: . “Disabling branch prediction” is definitely not an accurate description and we are working to address with SUSE now.
https://www.phoronix.com/forums/forum/phoronix/general-discussion/999103-more-linux-kernel-gcc-patches-come-out-in-the-wake-of-spectre-meltdown/page4 https://www.phoronix.com/forums/forum/phoronix/general-discu...
- seriouslydoode 9y agoHere's the openSUSE/kernel-source/commit in question: https://github.com/openSUSE/kernel-source/commit/14b04164b2ff91035a9a8f4672f4d86b929697ce https://github.com/openSUSE/kernel-source/commit/14b04164b2f... Search for amd.com for AMD related changes.
- taspeotis 9y ago114 changed files with 12,403 additions and 23 deletions. That's a pretty big patch (although some of those lines are .patch file pre- and post-amble). I feel bad for the people that had to develop/qa/signoff all of that in such a short timeframe. There's got to be at least one mistake in there somewhere.
- azernik 9y agoAlmost all of this commit is .patch files. Going through them, it seems to be about 10 from AMD, a few from IBM (for S390 processors), a bunch from Intel, and a few from kernel core maintainers. It's a giant workload, but seems to have been distributed pretty widely.
- oneweekwonder 9y agoAm I seeing this right. They called the entry points paranoid* as in "unreasonably or obsessively anxious, suspicious, or mistrustful"? Funny,