LTTNG-IRQLOG-MI(1)
π NAME π
lttng-irqlog-mi β the LTTng analyses IRQ log machine interface, bestie π
β¨ DESCRIPTION β¨
Okay so. This is the command-line tool that does the IRQ log thing through LTTng analyses' machine interface. She's a command, and here's exactly how you call her:
usage: lttng-irqlog-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. That's the whole vibe π¦
π positional arguments
<path/to/trace>β the path to your trace. that's it, that's the one thing she needs from you, no cap.
π optional arguments
-h,--helpβ shows this help message and dips. classic β¨-r REFRESH,--refresh REFRESHβ the refresh period, and you can tack a units suffix on there if you want (default units ares).--gmtβ do the timestamp math based on GMT instead of your local time. timezone girlies rise π«Ά--skip-validationβ skips validating the trace. yolo mode, but make it sanctioned.--begin BEGINβ start time, formatted likehh:mm:ss[.nnnnnnnnn].--end ENDβ end time, formatted likehh:mm:ss[.nnnnnnnnn].--period PERIODβ defines a period.--period-captures PERIOD_CAPTURESβ defines period captures.--period-begin PERIOD_BEGINβ the event name that marks the start of the analysis period.--period-end PERIOD_ENDβ the event name that marks the end of the analysis period. heads up bestie, this one requires--period-beginπ--period-begin-key PERIOD_BEGIN_KEYβ optional; a list of event field names used to match the period markers (default:cpu_id).--period-end-key PERIOD_END_KEYβ optional; a list of event field names used to match the period marker. if you don't specify any, it just uses whatever you gave to--period-begin-key.--period-key-value PERIOD_KEY_VALUEβ optional; pins down a fixed key value that a period has to correspond to in order to even be considered. picky, and honestly? valid.--cpu CPUβ filters the results so you only see this list of CPU IDs.--timerange TIMERANGEβ the time range, written as[begin,end].--progress-use-sizeβ approximates progress using the trace size.--no-intersectionβ turns off stream intersection mode.-V,--versionβ shows the program's version number and exits. main character exit π--debugβ enables debug mode (or you can just set theLTTNG_ANALYSES_DEBUGenvironment variable, whatever's easier).--no-colorβ kills the colored output. for the monochrome minimalists π€--no-progressβ doesn't display the progress bar.--min MINβ filters out any durations shorter than min usec.--max MAXβ filters out any durations longer than max usec.--freqβ outputs the frequency distribution of handler durations.--freq-resolution FREQ_RESOLUTIONβ the resolution for that frequency distribution (default20).--freq-uniformβ uses a uniform resolution across all the distributions.--freq-seriesβ consolidates the frequency distribution histogram down into a single one.--logβ outputs the IRQs in chronological order. timeline slay π₯--statsβ outputs IRQ statistics.--irq IRQβ outputs results only for this list of IRQ.--softirq SOFTIRQβ outputs results only for this list of SoftIRQ.
and that's the whole page, bestie, you ate it up πβ¨
this was LTTng Analyses v0.6.0, dated January 2017 β iconique, historic, we stan a legacy release ππ¦
π¦ 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