linux-kernel - Re: [patch V3 00/66] x86/fpu: Spring cleaning and PKRU sanitizing

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87wnqme06c.ffs@nanos.tec.linutronix.de>
Date:   Tue, 22 Jun 2021 11:08:43 +0200
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Oliver Sang <oliver.sang@...el.com>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Andy Lutomirski <luto@...nel.org>,
        Dave Hansen <dave.hansen@...ux.intel.com>,
        "Yu\, Fenghua" <fenghua.yu@...el.com>,
        "Luck\, Tony" <tony.luck@...el.com>,
        "Yu\, Yu-cheng" <yu-cheng.yu@...el.com>,
        Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
        Borislav Petkov <bp@...e.de>,
        Peter Zijlstra <peterz@...radead.org>,
        Kan Liang <kan.liang@...ux.intel.com>,
        "Li\, Aubrey" <aubrey.li@...el.com>,
        "Xing\, Zhengjun" <zhengjun.xing@...ux.intel.com>,
        "Tang\, Feng" <feng.tang@...el.com>,
        "Liu\, Yujie" <yujie.liu@...el.com>,
        "Si\, Beibei" <beibei.si@...el.com>,
        "Li\, Philip" <philip.li@...el.com>,
        "Du\, Julie" <julie.du@...el.com>
Subject: Re: [patch V3 00/66] x86/fpu: Spring cleaning and PKRU sanitizing

Oliver,

On Tue, Jun 22 2021 at 09:59, Oliver Sang wrote:
> On Fri, Jun 18, 2021 at 10:18:23PM +0800, Thomas Gleixner wrote:
>>   git://git.kernel.org/pub/scm/linux/kernel/git/tglx/devel.git x86/fpu
>
> 0-Day kernel CI tested this branch from performance view,
> choosing some sub-tests from will-it-scale (detail as below), since we
> thought if the branch has the impact of fpu ops, will-it-scale should be
> able to catch it.
> we also plan to add stress-ng for new round test.
> could you suggest if any other suitable test suites? and what's the most
> proper sub-tests in will-it-scale and stress-ng?

Hard to tell. Anything scheduling heavy will exercise these code paths.

Thanks,

        tglx