LTTNG-IRQLOG(1)
β¨ LTTNG-IRQLOG β¨
okay so bestie, this is lttng-irqlog β the LTTng analyses IRQ log tool π
it lives in the LTTng Analyses family of user commands and it's literally here to make your IRQ trace data make sense. no cap. π«Ά
πΈ NAME πΈ
lttng-irqlog β LTTng analyses IRQ log π
π¦ DESCRIPTION π¦
the vibe is: you point it at a trace, it does irq stuff. here's the whole usage, exactly as it goes down:
usage: lttng-irqlog [-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. that's where your trace lives. π
π optional arguments π
-h,--helpβ show this help message and exit. the classic. the icon. π-r REFRESH,--refresh REFRESHβ refresh period, with an optional units suffix (default units:s). tick tock β°--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 setLTTNG_ANALYSES_DEBUGenvironment variable) π--no-colorβ disable colored output (sad, but okay π₯²)--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
bestie reminder:--period-endwill not work without--period-begin, and--period-end-keywill silently just borrow--period-begin-keyif you don't give it one. ikyk. π
that's the whole page, bestie, you ate it. π
β¨ this one's from LTTng Analyses v0.6.0, dated January 2017 β shoutout to the og manual page, still iconic after all these years. mwah π π¦ π«Ά
π¦ 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