tools/perf/pmu-events/arch/arm64/fujitsu/monaka/trace.json

File Facts

System

Linux kernel

Corpus path

tools/perf/pmu-events/arch/arm64/fujitsu/monaka/trace.json

Extension

.json

Size

720 bytes

Lines

19

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": "TRB_WRAP",
        "BriefDescription": "This event counts the event generated each time the current write pointer is wrapped to the base pointer."
    },
    {
        "ArchStdEvent": "TRB_TRIG",
        "BriefDescription": "This event counts the event generated when a Trace Buffer Extension Trigger Event occurs."
    },
    {
        "ArchStdEvent": "TRCEXTOUT0",
        "BriefDescription": "This event counts the event generated each time an event is signaled by the trace unit external event 0."
    },
    {
        "ArchStdEvent": "CTI_TRIGOUT4",
        "BriefDescription": "This event counts the event generated each time an event is signaled on CTI output trigger 4."
    }
]

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.