__ __ __ __ _____ _ _ _____ _ _ _ | \/ | \ \ / / | __ \ (_) | | / ____| | | | | | \ / |_ __\ V / | |__) | __ ___ ____ _| |_ ___ | (___ | |__ ___| | | | |\/| | '__|> < | ___/ '__| \ \ / / _` | __/ _ \ \___ \| '_ \ / _ \ | | | | | | |_ / . \ | | | | | |\ V / (_| | || __/ ____) | | | | __/ | | |_| |_|_(_)_/ \_\ |_| |_| |_| \_/ \__,_|\__\___| |_____/|_| |_|\___V 2.1 if you need WebShell for Seo everyday contact me on Telegram Telegram Address : @jackleetFor_More_Tools:
<!DOCTYPE html>
<html lang="en" data-content_root="../../">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" /><meta name="viewport" content="width=device-width, initial-scale=1" />
<title>31. In-Field Scan — The Linux Kernel documentation</title>
<link rel="stylesheet" type="text/css" href="../../_static/pygments.css?v=fa44fd50" />
<link rel="stylesheet" type="text/css" href="../../_static/alabaster.css?v=3918102e" />
<script src="../../_static/documentation_options.js?v=5929fcd5"></script>
<script src="../../_static/doctools.js?v=9bcbadda"></script>
<script src="../../_static/sphinx_highlight.js?v=dc90522c"></script>
<link rel="index" title="Index" href="../../genindex.html" />
<link rel="search" title="Search" href="../../search.html" />
<link rel="next" title="32. Shared Virtual Addressing (SVA) with ENQCMD" href="sva.html" />
<link rel="prev" title="30.8. Flexible Return and Event Delivery (FRED)" href="x86_64/fred.html" />
<link rel="stylesheet" href="../../_static/custom.css" type="text/css" />
</head><body>
<div class="document">
<div class="sphinxsidebar" role="navigation" aria-label="Main">
<div class="sphinxsidebarwrapper">
<p class="logo"><a href="../../index.html">
<img class="logo" src="../../_static/logo.svg" alt="Logo of The Linux Kernel"/>
</a></p>
<h1 class="logo"><a href="../../index.html">The Linux Kernel</a></h1>
<p class="blurb">6.18.50</p>
<search id="searchbox" style="display: none" role="search">
<h3 id="searchlabel">Quick search</h3>
<div class="searchformwrapper">
<form class="search" action="../../search.html" method="get">
<input type="text" name="q" aria-labelledby="searchlabel" autocomplete="off" autocorrect="off" autocapitalize="off" spellcheck="false"/>
<input type="submit" value="Go" />
</form>
</div>
</search>
<script>document.getElementById('searchbox').style.display = "block"</script>
<p>
<h3 class="kernel-toc-contents">Contents</h3>
<input type="checkbox" class="kernel-toc-toggle" id = "kernel-toc-toggle" checked>
<label class="kernel-toc-title" for="kernel-toc-toggle"></label>
<div class="kerneltoc" id="kerneltoc">
<ul>
<li class="toctree-l1"><a class="reference internal" href="../../process/development-process.html">Development process</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../process/submitting-patches.html">Submitting patches</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../process/code-of-conduct.html">Code of conduct</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../maintainer/index.html">Maintainer handbook</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../process/index.html">All development-process docs</a></li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../../core-api/index.html">Core API</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../driver-api/index.html">Driver APIs</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../subsystem-apis.html">Subsystems</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../locking/index.html">Locking</a></li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../../process/license-rules.html">Licensing rules</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../doc-guide/index.html">Writing documentation</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../dev-tools/index.html">Development tools</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../dev-tools/testing-overview.html">Testing guide</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../kernel-hacking/index.html">Hacking guide</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../trace/index.html">Tracing</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../fault-injection/index.html">Fault injection</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../livepatch/index.html">Livepatching</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../rust/index.html">Rust</a></li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../../admin-guide/index.html">Administration</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../kbuild/index.html">Build system</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../admin-guide/reporting-issues.html">Reporting issues</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../tools/index.html">Userspace tools</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../userspace-api/index.html">Userspace API</a></li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../../firmware-guide/index.html">Firmware</a></li>
<li class="toctree-l1"><a class="reference internal" href="../../devicetree/index.html">Firmware and Devicetree</a></li>
</ul>
<ul class="current">
<li class="toctree-l1 current"><a class="reference internal" href="../index.html">CPU architectures</a><ul class="current">
<li class="toctree-l2"><a class="reference internal" href="../arc/index.html">ARC architecture</a></li>
<li class="toctree-l2"><a class="reference internal" href="../arm/index.html">ARM Architecture</a></li>
<li class="toctree-l2"><a class="reference internal" href="../arm64/index.html">ARM64 Architecture</a></li>
<li class="toctree-l2"><a class="reference internal" href="../loongarch/index.html">LoongArch Architecture</a></li>
<li class="toctree-l2"><a class="reference internal" href="../m68k/index.html">m68k Architecture</a></li>
<li class="toctree-l2"><a class="reference internal" href="../mips/index.html">MIPS-specific Documentation</a></li>
<li class="toctree-l2"><a class="reference internal" href="../nios2/index.html">Nios II Specific Documentation</a></li>
<li class="toctree-l2"><a class="reference internal" href="../openrisc/index.html">OpenRISC Architecture</a></li>
<li class="toctree-l2"><a class="reference internal" href="../parisc/index.html">PA-RISC Architecture</a></li>
<li class="toctree-l2"><a class="reference internal" href="../powerpc/index.html">powerpc</a></li>
<li class="toctree-l2"><a class="reference internal" href="../riscv/index.html">RISC-V architecture</a></li>
<li class="toctree-l2"><a class="reference internal" href="../s390/index.html">s390 Architecture</a></li>
<li class="toctree-l2"><a class="reference internal" href="../sh/index.html">SuperH Interfaces Guide</a></li>
<li class="toctree-l2"><a class="reference internal" href="../sparc/index.html">Sparc Architecture</a></li>
<li class="toctree-l2 current"><a class="reference internal" href="index.html">x86-specific Documentation</a><ul class="current">
<li class="toctree-l3"><a class="reference internal" href="boot.html">1. The Linux/x86 Boot Protocol</a></li>
<li class="toctree-l3"><a class="reference internal" href="booting-dt.html">2. DeviceTree Booting</a></li>
<li class="toctree-l3"><a class="reference internal" href="cpuinfo.html">3. x86 Feature Flags</a></li>
<li class="toctree-l3"><a class="reference internal" href="topology.html">4. x86 Topology</a></li>
<li class="toctree-l3"><a class="reference internal" href="exception-tables.html">5. Kernel level exception handling</a></li>
<li class="toctree-l3"><a class="reference internal" href="kernel-stacks.html">6. Kernel Stacks</a></li>
<li class="toctree-l3"><a class="reference internal" href="entry_64.html">7. Kernel Entries</a></li>
<li class="toctree-l3"><a class="reference internal" href="earlyprintk.html">8. Early Printk</a></li>
<li class="toctree-l3"><a class="reference internal" href="orc-unwinder.html">9. ORC unwinder</a></li>
<li class="toctree-l3"><a class="reference internal" href="zero-page.html">10. Zero Page</a></li>
<li class="toctree-l3"><a class="reference internal" href="tlb.html">11. The TLB</a></li>
<li class="toctree-l3"><a class="reference internal" href="mtrr.html">12. MTRR (Memory Type Range Register) control</a></li>
<li class="toctree-l3"><a class="reference internal" href="pat.html">13. PAT (Page Attribute Table)</a></li>
<li class="toctree-l3"><a class="reference internal" href="intel-hfi.html">14. Hardware-Feedback Interface for scheduling on Intel Hardware</a></li>
<li class="toctree-l3"><a class="reference internal" href="shstk.html">15. Control-flow Enforcement Technology (CET) Shadow Stack</a></li>
<li class="toctree-l3"><a class="reference internal" href="iommu.html">16. x86 IOMMU Support</a></li>
<li class="toctree-l3"><a class="reference internal" href="intel_txt.html">17. Intel(R) TXT Overview</a></li>
<li class="toctree-l3"><a class="reference internal" href="amd-debugging.html">18. Debugging AMD Zen systems</a></li>
<li class="toctree-l3"><a class="reference internal" href="amd-memory-encryption.html">19. AMD Memory Encryption</a></li>
<li class="toctree-l3"><a class="reference internal" href="amd_hsmp.html">20. AMD HSMP interface</a></li>
<li class="toctree-l3"><a class="reference internal" href="amd-hfi.html">21. Hardware Feedback Interface For Hetero Core Scheduling On AMD Platform</a></li>
<li class="toctree-l3"><a class="reference internal" href="tdx.html">22. Intel Trust Domain Extensions (TDX)</a></li>
<li class="toctree-l3"><a class="reference internal" href="pti.html">23. Page Table Isolation (PTI)</a></li>
<li class="toctree-l3"><a class="reference internal" href="mds.html">24. Microarchitectural Data Sampling (MDS) mitigation</a></li>
<li class="toctree-l3"><a class="reference internal" href="microcode.html">25. The Linux Microcode Loader</a></li>
<li class="toctree-l3"><a class="reference internal" href="tsx_async_abort.html">26. TSX Async Abort (TAA) mitigation</a></li>
<li class="toctree-l3"><a class="reference internal" href="buslock.html">27. Bus lock detection and handling</a></li>
<li class="toctree-l3"><a class="reference internal" href="usb-legacy-support.html">28. USB Legacy support</a></li>
<li class="toctree-l3"><a class="reference internal" href="i386/index.html">29. i386 Support</a></li>
<li class="toctree-l3"><a class="reference internal" href="x86_64/index.html">30. x86_64 Support</a></li>
<li class="toctree-l3 current"><a class="current reference internal" href="#">31. In-Field Scan</a></li>
<li class="toctree-l3"><a class="reference internal" href="sva.html">32. Shared Virtual Addressing (SVA) with ENQCMD</a></li>
<li class="toctree-l3"><a class="reference internal" href="sgx.html">33. Software Guard eXtensions (SGX)</a></li>
<li class="toctree-l3"><a class="reference internal" href="features.html">34. Feature status on x86 architecture</a></li>
<li class="toctree-l3"><a class="reference internal" href="elf_auxvec.html">35. x86-specific ELF Auxiliary Vectors</a></li>
<li class="toctree-l3"><a class="reference internal" href="xstate.html">36. Using XSTATE features in user space applications</a></li>
</ul>
</li>
<li class="toctree-l2"><a class="reference internal" href="../xtensa/index.html">Xtensa Architecture</a></li>
</ul>
</li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../../staging/index.html">Unsorted documentation</a></li>
</ul>
<ul>
<li class="toctree-l1"><a class="reference internal" href="../../translations/index.html">Translations</a></li>
</ul>
</div>
<script type="text/javascript"> <!--
var sbar = document.getElementsByClassName("sphinxsidebar")[0];
let currents = document.getElementsByClassName("current")
if (currents.length) {
sbar.scrollTop = currents[currents.length - 1].offsetTop;
}
--> </script>
<div role="note" aria-label="source link">
<h3>This Page</h3>
<ul class="this-page-menu">
<li><a href="../../_sources/arch/x86/ifs.rst.txt"
rel="nofollow">Show Source</a></li>
</ul>
</div>
</div>
</div>
<div class="documentwrapper">
<div class="bodywrapper">
<div class="body" role="main">
<p id="in-field-scan"><strong>In-Field Scan</strong></p>
<section id="id1">
<h1><span class="section-number">31. </span>In-Field Scan<a class="headerlink" href="#id1" title="Link to this heading">¶</a></h1>
<section id="introduction">
<h2><span class="section-number">31.1. </span>Introduction<a class="headerlink" href="#introduction" title="Link to this heading">¶</a></h2>
<p>In Field Scan (IFS) is a hardware feature to run circuit level tests on
a CPU core to detect problems that are not caught by parity or ECC checks.
Future CPUs will support more than one type of test which will show up
with a new platform-device instance-id.</p>
</section>
<section id="ifs-image">
<h2><span class="section-number">31.2. </span>IFS Image<a class="headerlink" href="#ifs-image" title="Link to this heading">¶</a></h2>
<p>Intel provides firmware files containing the scan tests via the webpage <a class="footnote-reference brackets" href="#f1" id="id2" role="doc-noteref"><span class="fn-bracket">[</span>1<span class="fn-bracket">]</span></a>.
Look under “In-Field Scan Test Images Download” section towards the
end of the page. Similar to microcode, there are separate files for each
family-model-stepping. IFS Images are not applicable for some test types.
Wherever applicable the sysfs directory would provide a “current_batch” file
(see below) for loading the image.</p>
<aside class="footnote-list brackets">
<aside class="footnote brackets" id="f1" role="doc-footnote">
<span class="label"><span class="fn-bracket">[</span><a role="doc-backlink" href="#id2">1</a><span class="fn-bracket">]</span></span>
<p><a class="reference external" href="https://intel.com/InFieldScan">https://intel.com/InFieldScan</a></p>
</aside>
</aside>
</section>
<section id="ifs-image-loading">
<h2><span class="section-number">31.3. </span>IFS Image Loading<a class="headerlink" href="#ifs-image-loading" title="Link to this heading">¶</a></h2>
<p>The driver loads the tests into memory reserved BIOS local to each CPU
socket in a two step process using writes to MSRs to first load the
SHA hashes for the test. Then the tests themselves. Status MSRs provide
feedback on the success/failure of these steps.</p>
<p>The test files are kept in a fixed location: /lib/firmware/intel/ifs_<n>/
For e.g if there are 3 test files, they would be named in the following
fashion:
ff-mm-ss-01.scan
ff-mm-ss-02.scan
ff-mm-ss-03.scan
(where ff refers to family, mm indicates model and ss indicates stepping)</p>
<p>A different test file can be loaded by writing the numerical portion
(e.g 1, 2 or 3 in the above scenario) into the curent_batch file.
To load ff-mm-ss-02.scan, the following command can be used:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span># echo 2 > /sys/devices/virtual/misc/intel_ifs_<n>/current_batch
</pre></div>
</div>
<p>The above file can also be read to know the currently loaded image.</p>
</section>
<section id="running-tests">
<h2><span class="section-number">31.4. </span>Running tests<a class="headerlink" href="#running-tests" title="Link to this heading">¶</a></h2>
<p>Tests are run by the driver synchronizing execution of all threads on a
core and then writing to the ACTIVATE_SCAN MSR on all threads. Instruction
execution continues when:</p>
<ol class="arabic simple">
<li><p>All tests have completed.</p></li>
<li><p>Execution was interrupted.</p></li>
<li><p>A test detected a problem.</p></li>
</ol>
<p>Note that ALL THREADS ON THE CORE ARE EFFECTIVELY OFFLINE FOR THE
DURATION OF THE TEST. This can be up to 200 milliseconds. If the system
is running latency sensitive applications that cannot tolerate an
interruption of this magnitude, the system administrator must arrange
to migrate those applications to other cores before running a core test.
It may also be necessary to redirect interrupts to other CPUs.</p>
<p>In all cases reading the corresponding test’s STATUS MSR provides details on what
happened. The driver makes the value of this MSR visible to applications
via the “details” file (see below). Interrupted tests may be restarted.</p>
<p>The IFS driver provides sysfs interfaces via /sys/devices/virtual/misc/intel_ifs_<n>/
to control execution:</p>
<p>Test a specific core:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span># echo <cpu#> > /sys/devices/virtual/misc/intel_ifs_<n>/run_test
</pre></div>
</div>
<p>when HT is enabled any of the sibling cpu# can be specified to test
its corresponding physical core. Since the tests are per physical core,
the result of testing any thread is same. All siblings must be online
to run a core test. It is only necessary to test one thread.</p>
<p>For e.g. to test core corresponding to cpu5</p>
<blockquote>
<div><p># echo 5 > /sys/devices/virtual/misc/intel_ifs_<n>/run_test</p>
</div></blockquote>
<p>Results of the last test is provided in /sys:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>$ cat /sys/devices/virtual/misc/intel_ifs_<n>/status
pass
</pre></div>
</div>
<p>Status can be one of pass, fail, untested</p>
<p>Additional details of the last test is provided by the details file:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>$ cat /sys/devices/virtual/misc/intel_ifs_<n>/details
0x8081
</pre></div>
</div>
<p>The details file reports the hex value of the test specific status MSR.
Hardware defined error codes are documented in volume 4 of the Intel
Software Developer’s Manual but the error_code field may contain one of
the following driver defined software codes:</p>
<table class="docutils align-default">
<tbody>
<tr class="row-odd"><td><p>0xFD</p></td>
<td><p>Software timeout</p></td>
</tr>
<tr class="row-even"><td><p>0xFE</p></td>
<td><p>Partial completion</p></td>
</tr>
</tbody>
</table>
</section>
<section id="driver-design-choices">
<h2><span class="section-number">31.5. </span>Driver design choices<a class="headerlink" href="#driver-design-choices" title="Link to this heading">¶</a></h2>
<p>1) The ACTIVATE_SCAN MSR allows for running any consecutive subrange of
available tests. But the driver always tries to run all tests and only
uses the subrange feature to restart an interrupted test.</p>
<p>2) Hardware allows for some number of cores to be tested in parallel.
The driver does not make use of this, it only tests one core at a time.</p>
</section>
<section id="structural-based-functional-test-at-field-sbaf">
<h2><span class="section-number">31.6. </span>Structural Based Functional Test at Field (SBAF):<a class="headerlink" href="#structural-based-functional-test-at-field-sbaf" title="Link to this heading">¶</a></h2>
<p>SBAF is a new type of testing that provides comprehensive core test
coverage complementing Scan at Field (SAF) testing. SBAF mimics the
manufacturing screening environment and leverages the same test suite.
It makes use of Design For Test (DFT) observation sites and features
to maximize coverage in minimum time.</p>
<p>Similar to the SAF test, SBAF isolates the core under test from the
rest of the system during execution. Upon completion, the core
seamlessly resets to its pre-test state and resumes normal operation.
Any machine checks or hangs encountered during the test are confined to
the isolated core, preventing disruption to the overall system.</p>
<p>Like the SAF test, the SBAF test is also divided into multiple batches,
and each batch test can take hundreds of milliseconds (100-200 ms) to
complete. If such a lengthy interruption is undesirable, it is
recommended to relocate the time-sensitive applications to other cores.</p>
<dl class="c struct">
<dt class="sig sig-object c" id="c.ifs_test_msrs">
<span class="k"><span class="pre">struct</span></span><span class="w"> </span><span class="sig-name descname"><span class="n"><span class="pre">ifs_test_msrs</span></span></span><a class="headerlink" href="#c.ifs_test_msrs" title="Link to this definition">¶</a><br /></dt>
<dd><p>MSRs used in IFS tests</p>
</dd></dl>
<div class="kernelindent docutils container">
<p><strong>Definition</strong>:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>struct ifs_test_msrs {
u32 copy_hashes;
u32 copy_hashes_status;
u32 copy_chunks;
u32 copy_chunks_status;
u32 test_ctrl;
};
</pre></div>
</div>
<p><strong>Members</strong></p>
<dl class="simple">
<dt><code class="docutils literal notranslate"><span class="pre">copy_hashes</span></code></dt><dd><p>Copy test hash data</p>
</dd>
<dt><code class="docutils literal notranslate"><span class="pre">copy_hashes_status</span></code></dt><dd><p>Status of copied test hash data</p>
</dd>
<dt><code class="docutils literal notranslate"><span class="pre">copy_chunks</span></code></dt><dd><p>Copy chunks of the test data</p>
</dd>
<dt><code class="docutils literal notranslate"><span class="pre">copy_chunks_status</span></code></dt><dd><p>Status of the copied test data chunks</p>
</dd>
<dt><code class="docutils literal notranslate"><span class="pre">test_ctrl</span></code></dt><dd><p>Control the test attributes</p>
</dd>
</dl>
</div>
<dl class="c struct">
<dt class="sig sig-object c" id="c.ifs_data">
<span class="k"><span class="pre">struct</span></span><span class="w"> </span><span class="sig-name descname"><span class="n"><span class="pre">ifs_data</span></span></span><a class="headerlink" href="#c.ifs_data" title="Link to this definition">¶</a><br /></dt>
<dd><p>attributes related to intel IFS driver</p>
</dd></dl>
<div class="kernelindent docutils container">
<p><strong>Definition</strong>:</p>
<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>struct ifs_data {
int loaded_version;
bool loaded;
bool loading_error;
int valid_chunks;
int status;
u64 scan_details;
u32 cur_batch;
u32 generation;
u32 chunk_size;
u32 array_gen;
u32 max_bundle;
};
</pre></div>
</div>
<p><strong>Members</strong></p>
<dl class="simple">
<dt><code class="docutils literal notranslate"><span class="pre">loaded_version</span></code></dt><dd><p>stores the currently loaded ifs image version.</p>
</dd>
<dt><code class="docutils literal notranslate"><span class="pre">loaded</span></code></dt><dd><p>If a valid test binary has been loaded into the memory</p>
</dd>
<dt><code class="docutils literal notranslate"><span class="pre">loading_error</span></code></dt><dd><p>Error occurred on another CPU while loading image</p>
</dd>
<dt><code class="docutils literal notranslate"><span class="pre">valid_chunks</span></code></dt><dd><p>number of chunks which could be validated.</p>
</dd>
<dt><code class="docutils literal notranslate"><span class="pre">status</span></code></dt><dd><p>it holds simple status pass/fail/untested</p>
</dd>
<dt><code class="docutils literal notranslate"><span class="pre">scan_details</span></code></dt><dd><p>opaque scan status code from h/w</p>
</dd>
<dt><code class="docutils literal notranslate"><span class="pre">cur_batch</span></code></dt><dd><p>number indicating the currently loaded test file</p>
</dd>
<dt><code class="docutils literal notranslate"><span class="pre">generation</span></code></dt><dd><p>IFS test generation enumerated by hardware</p>
</dd>
<dt><code class="docutils literal notranslate"><span class="pre">chunk_size</span></code></dt><dd><p>size of a test chunk</p>
</dd>
<dt><code class="docutils literal notranslate"><span class="pre">array_gen</span></code></dt><dd><p>test generation of array test</p>
</dd>
<dt><code class="docutils literal notranslate"><span class="pre">max_bundle</span></code></dt><dd><p>maximum bundle index</p>
</dd>
</dl>
</div>
</section>
</section>
</div>
</div>
</div>
<div class="clearer"></div>
</div>
<div class="footer">
©The kernel development community.
|
Powered by <a href="https://www.sphinx-doc.org/">Sphinx 8.1.3</a>
& <a href="https://alabaster.readthedocs.io">Alabaster 0.7.16</a>
|
<a href="../../_sources/arch/x86/ifs.rst.txt"
rel="nofollow">Page source</a>
</div>
</body>
</html>| Name | Type | Size | Permission | Actions |
|---|---|---|---|---|
| i386 | Folder | 0755 |
|
|
| x86_64 | Folder | 0755 |
|
|
| amd-debugging.html | File | 37.71 KB | 0644 |
|
| amd-hfi.html | File | 23.59 KB | 0644 |
|
| amd-memory-encryption.html | File | 26.71 KB | 0644 |
|
| amd_hsmp.html | File | 22.25 KB | 0644 |
|
| boot.html | File | 90.24 KB | 0644 |
|
| booting-dt.html | File | 13.53 KB | 0644 |
|
| buslock.html | File | 19.47 KB | 0644 |
|
| cpuinfo.html | File | 25.13 KB | 0644 |
|
| earlyprintk.html | File | 20.49 KB | 0644 |
|
| elf_auxvec.html | File | 14.44 KB | 0644 |
|
| entry_64.html | File | 17.44 KB | 0644 |
|
| exception-tables.html | File | 32.18 KB | 0644 |
|
| features.html | File | 21.74 KB | 0644 |
|
| ifs.html | File | 23.92 KB | 0644 |
|
| index.html | File | 37.18 KB | 0644 |
|
| intel-hfi.html | File | 17.6 KB | 0644 |
|
| intel_txt.html | File | 24.6 KB | 0644 |
|
| iommu.html | File | 20.98 KB | 0644 |
|
| kernel-stacks.html | File | 20.27 KB | 0644 |
|
| mds.html | File | 23.86 KB | 0644 |
|
| microcode.html | File | 23.17 KB | 0644 |
|
| mtrr.html | File | 27.58 KB | 0644 |
|
| orc-unwinder.html | File | 23.04 KB | 0644 |
|
| pat.html | File | 27.75 KB | 0644 |
|
| pti.html | File | 24.03 KB | 0644 |
|
| sgx.html | File | 52.06 KB | 0644 |
|
| shstk.html | File | 22.05 KB | 0644 |
|
| sva.html | File | 28.77 KB | 0644 |
|
| tdx.html | File | 37.07 KB | 0644 |
|
| tlb.html | File | 17.19 KB | 0644 |
|
| topology.html | File | 32.47 KB | 0644 |
|
| tsx_async_abort.html | File | 21.14 KB | 0644 |
|
| usb-legacy-support.html | File | 14.32 KB | 0644 |
|
| xstate.html | File | 20.64 KB | 0644 |
|
| zero-page.html | File | 18.08 KB | 0644 |
|