tools/perf/pmu-events/arch/x86/emeraldrapids/uncore-io.json

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

File Facts

System: Linux kernel
Corpus path: tools/perf/pmu-events/arch/x86/emeraldrapids/uncore-io.json
Extension: .json
Size: 190834 bytes
Lines: 4292
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.
Touches IRQ or DMA behavior; this matters for the representative real-device path.

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": "Free running counter that increments for every 32 bytes of data sent from the IO agent to the SOC",
        "Counter": "1",
        "EventCode": "0xff",
        "EventName": "UNC_IIO_BANDWIDTH_IN.PART0_FREERUN",
        "Experimental": "1",
        "PerPkg": "1",
        "UMask": "0x20",
        "Unit": "iio_free_running"
    },
    {
        "BriefDescription": "Free running counter that increments for every 32 bytes of data sent from the IO agent to the SOC",
        "Counter": "2",
        "EventCode": "0xff",
        "EventName": "UNC_IIO_BANDWIDTH_IN.PART1_FREERUN",
        "Experimental": "1",
        "PerPkg": "1",
        "UMask": "0x21",
        "Unit": "iio_free_running"
    },
    {
        "BriefDescription": "Free running counter that increments for every 32 bytes of data sent from the IO agent to the SOC",
        "Counter": "3",
        "EventCode": "0xff",
        "EventName": "UNC_IIO_BANDWIDTH_IN.PART2_FREERUN",
        "Experimental": "1",
        "PerPkg": "1",
        "UMask": "0x22",
        "Unit": "iio_free_running"
    },
    {
        "BriefDescription": "Free running counter that increments for every 32 bytes of data sent from the IO agent to the SOC",
        "Counter": "4",
        "EventCode": "0xff",
        "EventName": "UNC_IIO_BANDWIDTH_IN.PART3_FREERUN",
        "Experimental": "1",
        "PerPkg": "1",
        "UMask": "0x23",
        "Unit": "iio_free_running"
    },
    {
        "BriefDescription": "Free running counter that increments for every 32 bytes of data sent from the IO agent to the SOC",
        "Counter": "5",
        "EventCode": "0xff",
        "EventName": "UNC_IIO_BANDWIDTH_IN.PART4_FREERUN",
        "Experimental": "1",
        "PerPkg": "1",
        "UMask": "0x24",
        "Unit": "iio_free_running"
    },
    {
        "BriefDescription": "Free running counter that increments for every 32 bytes of data sent from the IO agent to the SOC",
        "Counter": "6",
        "EventCode": "0xff",
        "EventName": "UNC_IIO_BANDWIDTH_IN.PART5_FREERUN",
        "Experimental": "1",
        "PerPkg": "1",
        "UMask": "0x25",
        "Unit": "iio_free_running"
    },
    {
        "BriefDescription": "Free running counter that increments for every 32 bytes of data sent from the IO agent to the SOC",
        "Counter": "7",
        "EventCode": "0xff",
        "EventName": "UNC_IIO_BANDWIDTH_IN.PART6_FREERUN",
        "Experimental": "1",
        "PerPkg": "1",
        "UMask": "0x26",
        "Unit": "iio_free_running"

Annotation

Atlas domain: Support Tooling And Documentation / tools.
Implementation status: atlas-only.
IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.