tools/perf/pmu-events/arch/x86/arrowlake/uncore-cache.json

Source file repositories/reference/linux-study-clean/tools/perf/pmu-events/arch/x86/arrowlake/uncore-cache.json

File Facts

System: Linux kernel
Corpus path: tools/perf/pmu-events/arch/x86/arrowlake/uncore-cache.json
Extension: .json
Size: 592 bytes
Lines: 21
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

[
    {
        "BriefDescription": "Number of all entries allocated. Includes also retries.",
        "Counter": "0,1",
        "EventCode": "0x35",
        "EventName": "UNC_HAC_CBO_TOR_ALLOCATION.ALL",
        "PerPkg": "1",
        "UMask": "0x8",
        "Unit": "HAC_CBO"
    },
    {
        "BriefDescription": "Asserted on coherent DRD + DRdPref  allocations into the queue. Cacheable only",
        "Counter": "0,1",
        "EventCode": "0x35",
        "EventName": "UNC_HAC_CBO_TOR_ALLOCATION.DRD",
        "PerPkg": "1",
        "UMask": "0x1",
        "Unit": "HAC_CBO"
    }
]

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.