tools/perf/pmu-events/arch/arm64/nvidia/t410/bus.json
Source file repositories/reference/linux-study-clean/tools/perf/pmu-events/arch/arm64/nvidia/t410/bus.json
File Facts
- System
- Linux kernel
- Corpus path
tools/perf/pmu-events/arch/arm64/nvidia/t410/bus.json- Extension
.json- Size
- 2105 bytes
- Lines
- 49
- 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": "BUS_ACCESS",
"PublicDescription": "This event counts the number of data-beat accesses between the CPU and the external bus. This count includes accesses due to read, write, and snoop. Each beat of data is counted individually."
},
{
"ArchStdEvent": "BUS_CYCLES",
"PublicDescription": "This event counts bus cycles in the CPU. Bus cycles represent a clock cycle in which a transaction could be sent or received on the interface from the CPU to the external bus. Since that interface is driven at the same clock speed as the CPU, this event increments at the rate of CPU clock. Regardless of the WFE/WFI state of the PE, this event increments on each processor clock."
},
{
"ArchStdEvent": "BUS_ACCESS_RD",
"PublicDescription": "This event counts memory Read transactions seen on the external bus. Each beat of data is counted individually."
},
{
"ArchStdEvent": "BUS_ACCESS_WR",
"PublicDescription": "This event counts memory Write transactions seen on the external bus. Each beat of data is counted individually."
},
{
"EventCode": "0x0154",
"EventName": "BUS_REQUEST_REQ",
"PublicDescription": "Bus request, request."
},
{
"EventCode": "0x0155",
"EventName": "BUS_REQUEST_RETRY",
"PublicDescription": "Bus request, retry."
},
{
"EventCode": "0x0198",
"EventName": "L2_CHI_CBUSY0",
"PublicDescription": "Number of RXDAT or RXRSP response received width CBusy of 0."
},
{
"EventCode": "0x0199",
"EventName": "L2_CHI_CBUSY1",
"PublicDescription": "Number of RXDAT or RXRSP response received width CBusy of 1."
},
{
"EventCode": "0x019a",
"EventName": "L2_CHI_CBUSY2",
"PublicDescription": "Number of RXDAT or RXRSP response received width CBusy of 2."
},
{
"EventCode": "0x019b",
"EventName": "L2_CHI_CBUSY3",
"PublicDescription": "Number of RXDAT or RXRSP response received width CBusy of 3."
}
]
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.