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: <f0a2e1fab35a440ebf136862e8584cf0@intel.com>
Date:   Fri, 4 Mar 2022 16:51:04 +0000
From:   "Luck, Tony" <tony.luck@...el.com>
To:     "Williams, Dan J" <dan.j.williams@...el.com>,
        "hdegoede@...hat.com" <hdegoede@...hat.com>,
        "markgross@...nel.org" <markgross@...nel.org>,
        "Joseph, Jithu" <jithu.joseph@...el.com>
CC:     "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>,
        "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
        "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

> Dynamic creation of sysfs attributes sometime after the driver loads is
> not friendly for something that likely only needs the module loaded for
> a test run and then unloaded again. I think this effort would be better
> served by building a sysfs topology registered underneath an ifs
> platform device.

Ah. Another gap in the Documentation/x86/ifs.rst that I need to fix.

Expected use case isn't just "run this test once to check your system
for signs of silicon aging". It is load this and run the tests at regular
intervals to catch developing problems as soon as possible.

I'll see if I can get the architects of the feature to give some input
on what they expect to be a "regular interval" to be included in
the documentation.

Note that even if a user only plans to run infrequently, there isn't
much benefit from unloading the module. The kernel memory used
by this driver is dwarfed by the memory reserved by BIOS to hold
the validated copies of the scan tests. Reloading the tests from the
file takes longer than a single run of the tests (though perhaps
that can be avoided if reading the MSRs can confirm that the
tests already loaded in reserved memory).

-Tony