On Sep 28, 2014 12:25 PM, "Reindl Harald" <h.rei...@thelounge.net> wrote: > > > Am 28.09.2014 um 21:15 schrieb drago01: > > On Sun, Sep 28, 2014 at 8:17 PM, Reindl Harald <h.rei...@thelounge.net> 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 <car...@redhat.com> 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) ... > > that's the point of what i said: > > * you buy a new CPU in 2 months > * the microcode don't disable TSX there
What hypothetical CPU is this? I don't think Broadwell has TSX, so I think we're talking about Skylake here. > * if glibc now is built without TSX support you gain nothing from new hardware > * if kernel loads microcode early and you have hardware supporting > TSX and glibc also supports it -> fine you hav ethe feature > > it would be a big mistake to disable completly TSX forever and > if not forever how would someone decide when enable it - the only > sane way is to get microcode applid as early as possible and > after that use the CPU feautures which are enabled > > > but yeah if you build your own kernel you should try to be > > as close to possible to the distro config > > exactly what i said > > > -- > devel mailing list > devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
