LTTNG-IRQFREQ-MI(1)
β¨ LTTNG-IRQFREQ-MI β¨
okay bestie, welcome to lttng-irqfreq-mi, a User Commands girlie from the LTTng analyses family π she's the IRQ frequency machine interface β like, the version of the tool that talks to other programs instead of to your eyeballs. no cap.
π NAME π
lttng-irqfreq-mi β LTTng analyses IRQ frequency machine interface
π¦ DESCRIPTION π¦
the vibe here is literally just: the irq command. that's the whole thing she does. β¨
and here's exactly how you call her:
usage: lttng-irqfreq-mi [-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. periodt. π
πΈ positional arguments πΈ
<path/to/trace>β the trace path, bestie. point her at your trace and she'll do her thing π«Ά
π optional arguments π
-h,--helpβ shows this help message and dips. iconic behaviour honestly.-r REFRESH,--refresh REFRESHβ refresh period, and yes you can slap a units suffix on it (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 (it's right there in the flag, no commentary needed) π--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) β οΈ like, she literally will not accept this one on its own--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 setLTTNG_ANALYSES_DEBUGenvironment variable) π--no-colorβ Disable colored output. (sad, I know, but some terminals are cowards π)--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 (default20)--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:--period-endneeds--period-begin. don't come for me when it yells at you, I warned you.
okay that's the whole page, mwah π LTTng Analyses v0.6.0, dated January 2017 β yeah she's a little vintage, but she ate and she's still serving. go read your traces, main character ππ
π¦ where this page comes from
- debian bookworm: python3-lttnganalyses 0.6.1-3 Β· MIT
- ubuntu jammy: python3-lttnganalyses 0.6.1-2 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms