Documentation/ABI/testing/sysfs-devices-system-ibm-rtl

Source file repositories/reference/linux-study-clean/Documentation/ABI/testing/sysfs-devices-system-ibm-rtl

File Facts

System: Linux kernel
Corpus path: Documentation/ABI/testing/sysfs-devices-system-ibm-rtl
Extension: [no extension]
Size: 879 bytes
Lines: 25
Domain: Support Tooling And Documentation
Bucket: Documentation
Inferred role: Support Tooling And Documentation: Documentation
Status: atlas-only

Why This File Exists

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

Dependency Surface

No C-style include directives detected by the generator.

Detected Declarations

No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

What:           /sys/devices/system/ibm_rtl/state
Date:           Sep 2010
KernelVersion:  2.6.37
Contact:        Vernon Mauery <vernux@us.ibm.com>
Description:    The state file allows a means by which to change in and
                out of Premium Real-Time Mode (PRTM), as well as the
                ability to query the current state.

                    - 0 => PRTM off
                    - 1 => PRTM enabled

Users:          The ibm-prtm userspace daemon uses this interface.


What:           /sys/devices/system/ibm_rtl/version
Date:           Sep 2010
KernelVersion:  2.6.37
Contact:        Vernon Mauery <vernux@us.ibm.com>
Description:    The version file provides a means by which to query
                the RTL table version that lives in the Extended
                BIOS Data Area (EBDA).
Users:          The ibm-prtm userspace daemon uses this interface.

Annotation

Atlas domain: Support Tooling And Documentation / Documentation.
Implementation status: atlas-only.

Implementation Notes

This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.