tools/perf/pmu-events/arch/arm64/arm/neoverse-v1/l1i_cache.json

File Facts

System

Linux kernel

Corpus path

tools/perf/pmu-events/arch/arm64/arm/neoverse-v1/l1i_cache.json

Extension

.json

Size

725 bytes

Lines

15

Domain

Support Tooling And Documentation

Bucket

tools

Inferred role

Support Tooling And Documentation: configuration, schema, or hardware description

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

[
    {
        "ArchStdEvent": "L1I_CACHE_REFILL",
        "PublicDescription": "Counts cache line refills in the level 1 instruction cache caused by a missed instruction fetch. Instruction fetches may include accessing multiple instructions, but the single cache line allocation is counted once."
    },
    {
        "ArchStdEvent": "L1I_CACHE",
        "PublicDescription": "Counts instruction fetches which access the level 1 instruction cache. Instruction cache accesses caused by cache maintenance operations are not counted."
    },
    {
        "ArchStdEvent": "L1I_CACHE_LMISS",
        "PublicDescription": "Counts cache line refills into the level 1 instruction cache, that incurred additional latency."
    }
]

Annotation

• Atlas domain: Support Tooling And Documentation / tools.
• 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.