On Sun, Sep 28, 2014 at 8:17 PM, Reindl Harald <h.reindl@xxxxxxxxxxxxx> wrote: > > Am 28.09.2014 um 20:13 schrieb Carlos O'Donell: >> On 09/28/2014 01:24 PM, drago01 wrote: >>> On Sun, Sep 28, 2014 at 6:49 PM, Carlos O'Donell <carlos@xxxxxxxxxx> wrote: >>>> On 09/26/2014 02:34 PM, Carlos O'Donell wrote: >>>>> Developers. >>>>> >>>>> Testers wanted immediately for: >>>>> >>>>> https://admin.fedoraproject.org/updates/glibc-2.18-16.fc20 >>>>> >>>>> and >>>>> >>>>> https://admin.fedoraproject.org/updates/glibc-2.20-4.fc21 >>>> >>>> For FC21 was missed a case where TSX was being used and had >>>> to push one more update -5 to cover this case. >>> >>> Does that update still make sense given that the kernel / dracut >>> update enables early microcode loading? >> >> What about the case where the user runs a custom kernel? > > then he needs to build it right > > don't get me wrong but you can't seriously disable TSX > completly because a *possible* out-of-distribution kernel Well the microcode update *does* disable TSX (so that only applies to new yet to be introduced cpus) ... but yeah if you build your own kernel you should try to be as close to possible to the distro config. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
