• Dmitriy Vyukov's avatar
    runtime: do no lose CPU profiling signals · cc4e6aad
    Dmitriy Vyukov authored
    Currently we lose lots of profiling signals.
    Most notably, GC is not accounted at all.
    But stack splits, scheduler, syscalls, etc are lost as well.
    This creates seriously misleading profile.
    With this change all profiling signals are accounted.
    Now I see these additional entries that were previously absent:
    161  29.7%  29.7%      164  30.3% syscall.Syscall
     12   2.2%  50.9%       12   2.2% scanblock
     11   2.0%  55.0%       11   2.0% markonly
     10   1.8%  58.9%       10   1.8% sweepspan
      2   0.4%  85.8%        2   0.4% runtime.newstack
    It is still impossible to understand what causes stack splits,
    but at least it's clear how many time is spent on them.
    Update #2197.
    Update #5659.
    
    R=golang-dev, rsc
    CC=golang-dev
    https://golang.org/cl/12179043
    cc4e6aad
signal_arm.c 3.83 KB