linux-kernel - RE: [RFC 08/10] platform/x86/intel/ifs: Add IFS sysfs interface

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: <5129ec667d734f3da4043ce1b7df0439@intel.com>
Date:   Mon, 7 Mar 2022 21:33:46 +0000
From:   "Luck, Tony" <tony.luck@...el.com>
To:     "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
        "Joseph, Jithu" <jithu.joseph@...el.com>
CC:     "Williams, Dan J" <dan.j.williams@...el.com>,
        "hdegoede@...hat.com" <hdegoede@...hat.com>,
        "markgross@...nel.org" <markgross@...nel.org>,
        "corbet@....net" <corbet@....net>,
        "Raj, Ashok" <ashok.raj@...el.com>,
        "dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>,
        "patches@...ts.linux.dev" <patches@...ts.linux.dev>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "mingo@...hat.com" <mingo@...hat.com>,
        "rostedt@...dmis.org" <rostedt@...dmis.org>,
        "Shankar, Ravi V" <ravi.v.shankar@...el.com>,
        "tglx@...utronix.de" <tglx@...utronix.de>,
        "platform-driver-x86@...r.kernel.org" 
        <platform-driver-x86@...r.kernel.org>,
        "linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
        "hpa@...or.com" <hpa@...or.com>, "bp@...en8.de" <bp@...en8.de>,
        "andriy.shevchenko@...ux.intel.com" 
        <andriy.shevchenko@...ux.intel.com>,
        "x86@...nel.org" <x86@...nel.org>
Subject: RE: [RFC 08/10] platform/x86/intel/ifs: Add IFS sysfs interface

> > Also some context on test frequency: Hardware has  strict rate limiting of tests.
> > Every core can be tested only once in every 30 minutes. So it is pointless to test at high frequency.
>
> What limits this, the kernel?

Microcode enforces the per-core repeat rate on the first implementation.

But this limit isn't architectural. Future implementations may not have
the same, or perhaps any, limit.

-Tony