tools/perf/pmu-events/arch/x86/amdzen1/floating-point.json

Source file repositories/reference/linux-study-clean/tools/perf/pmu-events/arch/x86/amdzen1/floating-point.json

File Facts

System
Linux kernel
Corpus path
tools/perf/pmu-events/arch/x86/amdzen1/floating-point.json
Extension
.json
Size
15115 bytes
Lines
225
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.

Dependency Surface

Detected Declarations

Annotated Snippet

[
  {
    "EventName": "fpu_pipe_assignment.dual",
    "EventCode": "0x00",
    "BriefDescription": "Total number multi-pipe uOps assigned to all pipes.",
    "PublicDescription": "The number of operations (uOps) and dual-pipe uOps dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipelines are and may be used for workload characterization. This includes all operations performed by x87, MMX, and SSE instructions, including moves. Each increment represents a one- cycle dispatch event. This event is a speculative event. Since this event includes non-numeric operations it is not suitable for measuring MFLOPS. Total number multi-pipe uOps assigned to all pipes.",
    "UMask": "0xf0"
  },
  {
    "EventName": "fpu_pipe_assignment.dual3",
    "EventCode": "0x00",
    "BriefDescription": "Total number multi-pipe uOps assigned to pipe 3.",
    "PublicDescription": "The number of operations (uOps) and dual-pipe uOps dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipelines are and may be used for workload characterization. This includes all operations performed by x87, MMX, and SSE instructions, including moves. Each increment represents a one- cycle dispatch event. This event is a speculative event. Since this event includes non-numeric operations it is not suitable for measuring MFLOPS. Total number multi-pipe uOps assigned to pipe 3.",
    "UMask": "0x80"
  },
  {
    "EventName": "fpu_pipe_assignment.dual2",
    "EventCode": "0x00",
    "BriefDescription": "Total number multi-pipe uOps assigned to pipe 2.",
    "PublicDescription": "The number of operations (uOps) and dual-pipe uOps dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipelines are and may be used for workload characterization. This includes all operations performed by x87, MMX, and SSE instructions, including moves. Each increment represents a one- cycle dispatch event. This event is a speculative event. Since this event includes non-numeric operations it is not suitable for measuring MFLOPS. Total number multi-pipe uOps assigned to pipe 2.",
    "UMask": "0x40"
  },
  {
    "EventName": "fpu_pipe_assignment.dual1",
    "EventCode": "0x00",
    "BriefDescription": "Total number multi-pipe uOps assigned to pipe 1.",
    "PublicDescription": "The number of operations (uOps) and dual-pipe uOps dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipelines are and may be used for workload characterization. This includes all operations performed by x87, MMX, and SSE instructions, including moves. Each increment represents a one- cycle dispatch event. This event is a speculative event. Since this event includes non-numeric operations it is not suitable for measuring MFLOPS. Total number multi-pipe uOps assigned to pipe 1.",
    "UMask": "0x20"
  },
  {
    "EventName": "fpu_pipe_assignment.dual0",
    "EventCode": "0x00",
    "BriefDescription": "Total number multi-pipe uOps assigned to pipe 0.",
    "PublicDescription": "The number of operations (uOps) and dual-pipe uOps dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipelines are and may be used for workload characterization. This includes all operations performed by x87, MMX, and SSE instructions, including moves. Each increment represents a one- cycle dispatch event. This event is a speculative event. Since this event includes non-numeric operations it is not suitable for measuring MFLOPS. Total number multi-pipe uOps assigned to pipe 0.",
    "UMask": "0x10"
  },
  {
    "EventName": "fpu_pipe_assignment.total",
    "EventCode": "0x00",
    "BriefDescription": "Total number uOps assigned to all fpu pipes.",
    "PublicDescription": "The number of operations (uOps) and dual-pipe uOps dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipelines are and may be used for workload characterization. This includes all operations performed by x87, MMX, and SSE instructions, including moves. Each increment represents a one- cycle dispatch event. This event is a speculative event. Since this event includes non-numeric operations it is not suitable for measuring MFLOPS. Total number uOps assigned to all pipes.",
    "UMask": "0x0f"
  },
  {
    "EventName": "fpu_pipe_assignment.total3",
    "EventCode": "0x00",
    "BriefDescription": "Total number of fp uOps on pipe 3.",
    "PublicDescription": "The number of operations (uOps) dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipelines are and may be used for workload characterization. This includes all operations performed by x87, MMX, and SSE instructions, including moves. Each increment represents a one-cycle dispatch event. This event is a speculative event. Since this event includes non-numeric operations it is not suitable for measuring MFLOPS. Total number uOps assigned to pipe 3.",
    "UMask": "0x08"
  },
  {
    "EventName": "fpu_pipe_assignment.total2",
    "EventCode": "0x00",
    "BriefDescription": "Total number of fp uOps on pipe 2.",
    "PublicDescription": "The number of operations (uOps) dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipelines are and may be used for workload characterization. This includes all operations performed by x87, MMX, and SSE instructions, including moves. Each increment represents a one- cycle dispatch event. This event is a speculative event. Since this event includes non-numeric operations it is not suitable for measuring MFLOPS. Total number uOps assigned to pipe 2.",
    "UMask": "0x04"
  },
  {
    "EventName": "fpu_pipe_assignment.total1",
    "EventCode": "0x00",
    "BriefDescription": "Total number of fp uOps on pipe 1.",
    "PublicDescription": "The number of operations (uOps) dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipelines are and may be used for workload characterization. This includes all operations performed by x87, MMX, and SSE instructions, including moves. Each increment represents a one- cycle dispatch event. This event is a speculative event. Since this event includes non-numeric operations it is not suitable for measuring MFLOPS. Total number uOps assigned to pipe 1.",
    "UMask": "0x02"
  },
  {
    "EventName": "fpu_pipe_assignment.total0",
    "EventCode": "0x00",
    "BriefDescription": "Total number of fp uOps  on pipe 0.",
    "PublicDescription": "The number of operations (uOps) dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipelines are and may be used for workload characterization. This includes all operations performed by x87, MMX, and SSE instructions, including moves. Each increment represents a one- cycle dispatch event. This event is a speculative event. Since this event includes non-numeric operations it is not suitable for measuring MFLOPS. Total number uOps assigned to pipe 0.",
    "UMask": "0x01"

Annotation

Implementation Notes