tools/perf/pmu-events/arch/arm64/arm/neoverse-n3/spec_operation.json
Source file repositories/reference/linux-study-clean/tools/perf/pmu-events/arch/arm64/arm/neoverse-n3/spec_operation.json
File Facts
- System
- Linux kernel
- Corpus path
tools/perf/pmu-events/arch/arm64/arm/neoverse-n3/spec_operation.json- Extension
.json- Size
- 3960 bytes
- Lines
- 91
- 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": "BR_MIS_PRED",
"PublicDescription": "Counts branches which are speculatively executed and mispredicted."
},
{
"ArchStdEvent": "BR_PRED",
"PublicDescription": "Counts all speculatively executed branches."
},
{
"ArchStdEvent": "INST_SPEC",
"PublicDescription": "Counts operations that have been speculatively executed."
},
{
"ArchStdEvent": "OP_SPEC",
"PublicDescription": "Counts micro-operations speculatively executed. This is the count of the number of micro-operations dispatched in a cycle."
},
{
"ArchStdEvent": "STREX_FAIL_SPEC",
"PublicDescription": "Counts store-exclusive operations that have been speculatively executed and have not successfully completed the store operation."
},
{
"ArchStdEvent": "STREX_SPEC",
"PublicDescription": "Counts store-exclusive operations that have been speculatively executed."
},
{
"ArchStdEvent": "LD_SPEC",
"PublicDescription": "Counts speculatively executed load operations including Single Instruction Multiple Data (SIMD) load operations."
},
{
"ArchStdEvent": "ST_SPEC",
"PublicDescription": "Counts speculatively executed store operations including Single Instruction Multiple Data (SIMD) store operations."
},
{
"ArchStdEvent": "DP_SPEC",
"PublicDescription": "Counts speculatively executed logical or arithmetic instructions such as MOV/MVN operations."
},
{
"ArchStdEvent": "ASE_SPEC",
"PublicDescription": "Counts speculatively executed Advanced SIMD operations excluding load, store and move micro-operations that move data to or from SIMD (vector) registers."
},
{
"ArchStdEvent": "VFP_SPEC",
"PublicDescription": "Counts speculatively executed floating point operations. This event does not count operations that move data to or from floating point (vector) registers."
},
{
"ArchStdEvent": "PC_WRITE_SPEC",
"PublicDescription": "Counts speculatively executed operations which cause software changes of the PC. Those operations include all taken branch operations."
},
{
"ArchStdEvent": "CRYPTO_SPEC",
"PublicDescription": "Counts speculatively executed cryptographic operations except for PMULL and VMULL operations."
},
{
"ArchStdEvent": "ISB_SPEC",
"PublicDescription": "Counts ISB operations that are executed."
},
{
"ArchStdEvent": "DSB_SPEC",
"PublicDescription": "Counts DSB operations that are speculatively issued to Load/Store unit in the CPU."
},
{
"ArchStdEvent": "DMB_SPEC",
"PublicDescription": "Counts DMB operations that are speculatively issued to the Load/Store unit in the CPU. This event does not count implied barriers from load acquire/store release operations."
},
{
"ArchStdEvent": "RC_LD_SPEC",
"PublicDescription": "Counts any load acquire operations that are speculatively executed. For example: LDAR, LDARH, LDARB"
},
{
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.