LTTNG-IRQSTATS(1)

💖 LTTNG-IRQSTATS 💖

okay bestie, listen up — this is the lttng-irqstats page from the LTTng Analyses manual (section 1, User Commands, iykyk). she analyses IRQ statistics and she is thriving. no cap.

✨ NAME ✨

lttng-irqstats — LTTng analyses IRQ statistics 🎀

🌸 DESCRIPTION 🌸

okay so basically the vibe is: you hand her a trace, she does IRQ statistics on it. that's the whole gig. here's exactly how you call her:

usage: lttng-irqstats [-h] [-r REFRESH] [--gmt] [--skip-validation]

[--begin BEGIN] [--end END] [--period PERIOD]
       [--period-captures PERIOD_CAPTURES] [--period-begin PERIOD_BEGIN]
       [--period-end PERIOD_END] [--period-begin-key PERIOD_BEGIN_KEY]
       [--period-end-key PERIOD_END_KEY] [--period-key-value
       PERIOD_KEY_VALUE] [--cpu CPU] [--timerange TIMERANGE]
       [--progress-use-size] [--no-intersection] [-V] [--debug]
       [--no-color] [--no-progress] [--min MIN] [--max MAX] [--freq]
       [--freq-resolution FREQ_RESOLUTION] [--freq-uniform]
       [--freq-series] [--log] [--stats] [--irq IRQ] [--softirq SOFTIRQ]
       <path/to/trace>

The irq command. 💅

🫶 positional arguments:

• <path/to/trace> — the trace path, literally where your trace lives bestie

🦋 optional arguments:

• -h, --help — show this help message and exit (the classic, she's always there for you)
• -r REFRESH, --refresh REFRESH — refresh period, with optional units suffix (default units: s)
• --gmt — manipulate timestamps based on GMT instead of local time 🌍
• --skip-validation — skip the trace validation (living dangerously, love that for you)
• --begin BEGIN — start time: hh:mm:ss[.nnnnnnnnn]
• --end END — end time: hh:mm:ss[.nnnnnnnnn]
• --period PERIOD — period definition
• --period-captures PERIOD_CAPTURES — period captures definition
• --period-begin PERIOD_BEGIN — analysis period start marker event name
• --period-end PERIOD_END — analysis period end marker event name (requires --period-begin)
• --period-begin-key PERIOD_BEGIN_KEY — optional, list of event field names used to match period markers (default: cpu_id)
• --period-end-key PERIOD_END_KEY — optional, list of event field names used to match period marker. If none specified, use the same --period-begin-key
• --period-key-value PERIOD_KEY_VALUE — optional, define a fixed key value to which a period must correspond to be considered.
• --cpu CPU — filter the results only for this list of CPU IDs
• --timerange TIMERANGE — time range: [begin,end]
• --progress-use-size — use trace size to approximate progress
• --no-intersection — disable stream intersection mode
• -V, --version — show program's version number and exit
• --debug — enable debug mode (or set LTTNG_ANALYSES_DEBUG environment variable)
• --no-color — disable colored output 🙈 (tragic, but valid)
• --no-progress — don't display the progress bar
• --min MIN — filter out durations shorter than min usec
• --max MAX — filter out durations longer than max usec
• --freq — output the frequency distribution of handler durations
• --freq-resolution FREQ_RESOLUTION — frequency distribution resolution (default 20)
• --freq-uniform — use a uniform resolution across distributions
• --freq-series — consolidate frequency distribution histogram as a single one
• --log — output the IRQs in chronological order ⏳
• --stats — output IRQ statistics
• --irq IRQ — output results only for the list of IRQ
• --softirq SOFTIRQ — output results only for the list of SoftIRQ

🌈 reminder bestie: that LTTNG_ANALYSES_DEBUG environment variable is real, and --period-end genuinely requires --period-begin. read the fine print, she wrote it for a reason.

kisses, bye!! this page is from <strong>LTTng Analyses v0.6.0</strong>, dated <strong>January 2017</strong>, and it lives in section 1 of the manual. 🎀✨💖