tools/perf/pmu-events/arch/arm64/arm/cortex-a53/cache.json

File Facts

System

Linux kernel

Corpus path

tools/perf/pmu-events/arch/arm64/arm/cortex-a53/cache.json

Extension

.json

Size

701 bytes

Lines

28

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

[
  {
        "EventCode": "0xC2",
        "EventName": "PREFETCH_LINEFILL",
        "BriefDescription": "Linefill because of prefetch"
  },
  {
        "EventCode": "0xC3",
        "EventName": "PREFETCH_LINEFILL_DROP",
        "BriefDescription": "Instruction Cache Throttle occurred"
  },
  {
        "EventCode": "0xC4",
        "EventName": "READ_ALLOC_ENTER",
        "BriefDescription": "Entering read allocate mode"
  },
  {
        "EventCode": "0xC5",
        "EventName": "READ_ALLOC",
        "BriefDescription": "Read allocate mode"
  },
  {
        "EventCode": "0xC8",
        "EventName": "EXT_SNOOP",
        "BriefDescription": "SCU Snooped data from another CPU for this CPU"
  }
]

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.