The Linux Kernel
5.11.0-rc4
  • The Linux kernel user’s and administrator’s guide
  • Kernel Build System
  • The Linux kernel firmware guide
  • Open Firmware and Device Tree
  • The Linux kernel user-space API guide
  • Working with the kernel development community
  • Development tools for the kernel
  • How to write kernel documentation
  • Kernel Hacking Guides
  • Linux Tracing Technologies
    • Function Tracer Design
    • Notes on Analysing Behaviour Using Events and Tracepoints
    • ftrace - Function Tracer
    • Using ftrace to hook to functions
    • Kernel Probes (Kprobes)
    • Kprobe-based Event Tracing
    • Uprobe-tracer: Uprobe-based Event Tracing
    • Using the Linux Kernel Tracepoints
    • Event Tracing
    • Subsystem Trace Points: kmem
    • Subsystem Trace Points: power
    • NMI Trace Events
    • MSR Trace Events
    • In-kernel memory-mapped I/O tracing
    • Event Histograms
    • Histogram Design Notes
    • Boot-time tracing
    • Hardware Latency Detector
    • Intel(R) Trace Hub (TH)
    • Lockless Ring Buffer Design
    • System Trace Module
    • MIPI SyS-T over STP
    • CoreSight - ARM Hardware Trace
      • Coresight - HW Assisted Tracing on ARM
      • Coresight CPU Debug Module
      • CoreSight Embedded Cross Trigger (CTI & CTM).
      • ETMv4 sysfs linux driver programming reference.
  • Kernel Maintainer Handbook
  • fault-injection
  • Kernel Livepatching
  • The Linux driver implementer’s API guide
  • Core API Documentation
  • locking
  • Accounting
  • Block
  • cdrom
  • Linux CPUFreq - CPU frequency and voltage scaling code in the Linux(TM) kernel
  • Integrated Drive Electronics (IDE)
  • Frame Buffer
  • fpga
  • Human Interface Devices (HID)
  • I2C/SMBus Subsystem
  • Industrial I/O
  • ISDN
  • InfiniBand
  • LEDs
  • NetLabel
  • Linux Networking Documentation
  • pcmcia
  • Power Management
  • TCM Virtual Device
  • timers
  • Serial Peripheral Interface (SPI)
  • 1-Wire Subsystem
  • Linux Watchdog Support
  • Linux Virtualization Support
  • The Linux Input Documentation
  • Linux Hardware Monitoring
  • Linux GPU Driver Developer’s Guide
  • Security Documentation
  • Linux Sound Subsystem Documentation
  • Linux Kernel Crypto API
  • Filesystems in the Linux kernel
  • Linux Memory Management Documentation
  • BPF Documentation
  • USB support
  • Linux PCI Bus Subsystem
  • Linux SCSI Subsystem
  • Assorted Miscellaneous Devices Documentation
  • Linux Scheduler
  • MHI
  • Assembler Annotations
  • ARM Architecture
  • ARM64 Architecture
  • IA-64 Architecture
  • m68k Architecture
  • MIPS-specific Documentation
  • Nios II Specific Documentation
  • OpenRISC Architecture
  • PA-RISC Architecture
  • powerpc
  • RISC-V architecture
  • s390 Architecture
  • SuperH Interfaces Guide
  • Sparc Architecture
  • x86-specific Documentation
  • Xtensa Architecture
  • ext4 Data Structures and Algorithms
  • Unsorted Documentation
  • Atomic Types
  • Atomic bitops
  • Memory Barriers
  • General notification mechanism
  • Translations
The Linux Kernel
  • Docs »
  • Linux Tracing Technologies »
  • CoreSight - ARM Hardware Trace
  • View page source

CoreSight - ARM Hardware Trace¶

  • Coresight - HW Assisted Tracing on ARM
    • Introduction
    • Acronyms and Classification
    • Device Tree Bindings
    • Framework and implementation
    • Device Naming scheme
    • Topology Representation
    • How to use the tracer modules
    • Generating coverage files for Feedback Directed Optimization: AutoFDO
    • How to use the STM module
    • The CTI & CTM Modules
  • Coresight CPU Debug Module
    • Introduction
    • Implementation
    • Clock and power domain
    • Device Tree Bindings
    • How to use the module
    • Output format
  • CoreSight Embedded Cross Trigger (CTI & CTM).
    • Hardware Description
    • Sysfs files and directories
  • ETMv4 sysfs linux driver programming reference.
    • Sysfs files and directories
    • The ‘mode’ sysfs parameter.
Next Previous

© Copyright The kernel development community

Built with Sphinx using a theme provided by Read the Docs.