Query
Print a report of the main attributes of each GPU, as an indented Key : Value listing:
identity, PCI link, clock throttle reasons, memory, utilization, temperatures, power and
clocks, and the processes using the device. Use Discovery
for static detail such as compute resources and firmware components, and --query-gpu
or Dump for any single metric. The report can be restricted to chosen sections, written as JSON,
repeated at an interval, or saved to a file.
Synopsis
xpu-smi query
xpu-smi query --display [sections] --device [deviceIds]
xpu-smi query --json
xpu-smi query --loop [seconds] --count [count]
xpu-smi query --file [filename]
Options
- -h, --help
Print this help message and exit.
- -j, --json
Print the report as JSON instead of text. See JSON Output.
- --verbose
Print every row, including those a device does not report, which are otherwise left out of the text and the JSON. A value the driver or OS says the device does not support reads
Not Supported.
- -d <deviceIds>, --device <deviceIds>, --id <deviceIds>
Device IDs or PCI BDF addresses to report on. Multiple IDs can be separated by a comma. Use
-1to select all devices. Without this option every device is reported.
- --display <sections>
Comma-separated list of sections to print, from the table below. Names are case-insensitive. Sections always print in the order of the full report, whatever order they are listed in. Without this option everything is printed.
- --loop <seconds>
Print the report again every
<seconds>seconds until interrupted with Ctrl+C. On a terminal the whole report is drawn once and then only the lines whose values changed are rewritten, so unchanged data stays on screen. A line wider than the window wraps onto the rows below it. This needs the whole report, wrapped lines included, to fit in the window. If it does not, the report is printed once and a notice explains why, and nothing more is printed until the window is made large enough, at which point live updates start. Making the window smaller again prints the report once more. Use--displayto select fewer sections if you want live updates in a smaller window. When output goes to a file or a pipe, each report is appended in full.
- --loop-ms <milliseconds>
Like
--loop, with the interval in milliseconds. Takes precedence over--loop.
- --count <count>
Number of reports to print. Without
--loopor--loop-msa--countabove 1 repeats once a second. A count of 1 prints a single report.
- -f <path>, --file <path>
Write the report to
<path>instead of the terminal. An existing file is overwritten.
Sections
--display accepts the names below. A field that belongs to a section is printed
wherever it sits in the report, so --display PCI prints the PCI address fields from the
PCI part of the report, and memory utilization appears under both MEMORY and
UTILIZATION. A section or heading with nothing to show is left out. Without
--display every section is printed except SUPPORTED_CLOCKS, which must be named
(or ALL given) because it lists every clock the frequency range can be set to.
Section |
Report content |
|---|---|
|
Product name and brand, stepping, index, DRM minor number, serial number, UUID, GFX firmware version, board part number, device state, whether the device is a physical or an SR-IOV virtual function, the recovery action it needs, and the PCI address |
|
Memory total, used and free, memory type, number of channels and bus width, and memory utilization |
|
GPU, memory, compute, render, media and copy engine utilization |
|
GPU core and memory temperatures and their configured shutdown and slowdown temperatures |
|
Power draw and the current power limit |
|
Current graphics, memory and media clocks, the graphics clock the driver requested (Applications Clocks), and the maximum graphics and media clocks |
|
PCI address fields, class code and IDs, the physical slot, link generation and width (maximum and current), and throughput |
|
Nothing in this report. Use |
|
The fan speed, on devices with fans |
|
Scheduler mode, and the number of tiles, slices, sub-slices per slice and EUs |
|
Whether each clock throttle reason is active, the time throttled, and the performance factors, where the driver reports them |
|
The GPU core clocks the minimum and maximum of |
|
Processes using the device |
|
Everything above, including |
Sample Output
From an Intel Arc B580 run by a non-root user.
==============XPU-SMI LOG==============
Timestamp : 2026-10-23T14:50:00Z
UMD Version : 1.17.39980
KMD Version : N/A
Level Zero Version : 1.33.1
Attached GPUs : 1
GPU 0000:03:00.0
Product Name : Intel(R) Arc(TM) B580 Graphics
Product Brand : Intel(R) Corporation
Stepping : A0
GPU IP Version : 0x05004000
Serial Number : unknown
GPU UUID : 00000000-0000-0003-0000-0000e20b8086
Device Index : 0
Minor Number : 0
GFX Firmware Version : N/A (requires read-write access to /dev/mei1)
Platform Info
Slot Number : N/A
Device State : normal
GPU Virtualization Mode
Virtualization Mode : physical
Enabled VFs : 0
GPU Recovery Action : None
PCI
Bus : 0x03
Device : 0x00
Domain : 0x0000
Base Classcode : 0x03
Sub Classcode : 0x00
Device Id : 0xE20B
Bus Id : 0000:03:00.0
Sub System Id : 0x1100
GPU Link Info
PCIe Generation
Max : N/A (requires CAP_SYS_ADMIN)
Current : N/A (requires CAP_SYS_ADMIN)
Host Max : 5
Link Width
Max : N/A (requires CAP_SYS_ADMIN)
Current : N/A (requires CAP_SYS_ADMIN)
Host Max : 16
Tx Throughput : 102 kB/s
Rx Throughput : 1623 kB/s
Clocks Event Reasons
Thermal Limit : Not Active
Average Power Cap : Not Active
Burst Power Cap : Not Active
Current Limit : Not Active
PSU Alert : Not Active
SW Range : Not Active
HW Range : Not Active
Voltage : Not Active
Thermal Alert : Not Active
Power Alert : Not Active
FB Memory Usage
Total : 12216 MiB
Reserved : 0 MiB
Used : 218.62 MiB
Free : 11997.38 MiB
BAR Memory
Total : 16384 MiB
Memory Info
Memory Type : GDDR6
Number of Memory Channels : 6
Memory Bus Width : 192
Scheduler Mode : timeslice
Compute Resources
Number of Tiles : 1
Number of Slices : 5
Number of Sub-slices per Slice : 4
Number of EUs : 160
Utilization
GPU : 0.00 %
Memory : 1.79 %
Compute : 0.00 %
Render : 0.00 %
Media : 0.00 %
Video : 0.00 %
Video Enhancement : 0.00 %
Copy : 0.00 %
Temperature
GPU Current Temp : 30.00 C
GPU Shutdown Temp : 130 C
GPU Slowdown Temp : 105 C
Memory Current Temp : 48.00 C
Memory Shutdown Temp : 100 C
Memory Slowdown Temp : 85 C
GPU Power Readings
Average Power Draw : 59.34 W
Instantaneous Power Draw : 68.62 W
GPU Domain Power Draw : 0.06 W
Current Power Limit : 380.00 W
Peak Power Limit : 380.00 W
Memory Power Draw : 8.38 W
Clocks
Graphics : 400 MHz
Memory : 9500 MHz
Media : 1200 MHz
Applications Clocks
Graphics : 400 MHz
Max Clocks
Graphics : 2850 MHz
Media : 1500 MHz
Processes
None
Fields
Every row the report can print. Row is the label path in the text report, with the path to
the value in --json output (under each entry of gpus) below it. Details gives the
--display section that selects the row, its unit, and its source: the --query-gpu field
that reads the same value, or the Discovery property it comes from. A row reads N/A
when the device, driver or platform cannot supply its value; Meaning says when that is
expected.
Report header
Printed once, above the devices. JSON keys are at the top level.
Row |
Details |
Meaning |
|---|---|---|
Timestamp
|
When sampling began, as ISO 8601 UTC. |
|
UMD Version
|
Source: |
Level Zero user-mode GPU driver version. |
KMD Version
|
Source: |
Kernel-mode driver version that the driver module declares; |
Level Zero Version
|
Source: Level Zero loader |
Version of the Level Zero loader. |
Attached GPUs
|
Number of devices in the report. |
|
GPU <address>
|
Source: |
Starts each device; the value is its PCI address. In JSON each device is an entry of |
Identity
Row |
Details |
Meaning |
|---|---|---|
Product Name
|
Section: Source: |
Device name the driver reports. |
Product Brand
|
Section: Source: discovery Vendor Name |
Brand the driver reports, e.g. |
Stepping
|
Section: Source: discovery Stepping |
Silicon stepping, e.g. |
GPU IP Version
|
Section: Source: |
Graphics IP version the driver reports, in hex ( |
Serial Number
|
Section: Source: |
Board serial number: from the AMC on a card that has one, otherwise the OEM serial number held by the GSC (root only). |
GPU UUID
|
Section: Source: |
Device UUID. |
Device Index
|
Section: Source: |
Index |
Minor Number
|
Section: Source: DRM device |
Number of the device’s DRM card node, e.g. |
GFX Firmware Version
|
Section: Source: |
Version of the GFX firmware the device runs, read from the GSC. Needs read-write access to the device’s |
Board Part Number
|
Section: Source: discovery Part Number |
Part number of the board, read from the AMC. Present only on a device with an AMC. |
Platform Info > Slot Number
|
Section: Source: discovery PCI Slot |
Physical slot the platform firmware names for the device, e.g. |
Device State
|
Section: Source: device |
|
GPU Virtualization Mode > Virtualization Mode
|
Section: Source: PCI function |
|
GPU Virtualization Mode > Enabled VFs
|
Section: Source: |
SR-IOV virtual functions enabled on the physical function. Left out where the device or driver does not support SR-IOV. |
GPU Recovery Action
|
Section: Source: |
What the driver says the device needs to keep working: |
Row |
Details |
Meaning |
PCI > Bus
|
Section: Source: |
Bus number of the PCI address, in hex. |
PCI > Device
|
Section: Source: |
Device number of the PCI address, in hex. |
PCI > Domain
|
Section: Source: |
Domain of the PCI address, in hex. |
PCI > Base Classcode
|
Section: Source: |
PCI base class, in hex: |
PCI > Sub Classcode
|
Section: Source: |
PCI subclass, in hex. |
PCI > Device Id
|
Section: Source: |
PCI device ID, in hex. |
PCI > Bus Id
|
Section: Source: |
Full PCI address, |
PCI > Sub System Id
|
Section: Source: |
PCI subsystem device ID, in hex. |
PCI > GPU Link Info > PCIe Generation > Max
|
Section: Source: |
Highest PCIe generation the link supports. The driver reads it from PCI configuration space, which needs |
PCI > GPU Link Info > PCIe Generation > Current
|
Section: Source: |
PCIe generation the link runs at now. Needs |
PCI > GPU Link Info > PCIe Generation > Host Max
|
Section: Source: |
Maximum PCIe generation of the root port the device is under, the CPU end of the path (Linux sysfs). A switch in between can limit the link further. |
PCI > GPU Link Info > Link Width > Max
|
Section: Source: |
Widest the link can be, in lanes. Needs |
PCI > GPU Link Info > Link Width > Current
|
Section: Source: |
Lanes the link uses now. |
PCI > GPU Link Info > Link Width > Host Max
|
Section: Source: |
Maximum PCIe link width of the root port the device is under (Linux sysfs). |
PCI > PCIe Errors > Correctable
|
Section: Source: |
PCIe correctable errors the device’s function reported since it was enumerated (AER, Linux). Left out where the function has no AER counters, as the B580 GPU function, whose switch ports carry them. |
PCI > PCIe Errors > Non-Fatal
|
Section: Source: |
PCIe uncorrectable non-fatal errors since enumeration (AER, Linux). |
PCI > PCIe Errors > Fatal
|
Section: Source: |
PCIe uncorrectable fatal errors since enumeration (AER, Linux). |
PCI > PCIe Errors > Replay Number Rollovers
|
Section: Source: |
Times the link’s REPLAY_NUM counter rolled over, a correctable link error (AER, Linux). |
PCI > PCIe Errors > Replay Timer Timeouts
|
Section: Source: |
Times the link’s replay timer expired, a correctable link error (AER, Linux). |
PCI > Tx Throughput
|
Section: Unit: kB/s Source: |
Data the device sent over PCIe, averaged over the sampling window. |
PCI > Rx Throughput
|
Section: Unit: kB/s Source: |
Data the device received over PCIe, as for Tx Throughput. |
PCI > Atomic Caps Inbound
|
Section: Source: |
PCIe AtomicOp requests the device completes, from Device Capabilities 2: e.g. |
PCI > Replays Since Reset
|
Section: Source: |
PCIe replays since the last reset, from Level Zero. Printed where the driver supplies it; |
PCI > Atomic Requests
|
Section: Source: |
Whether the device may send PCIe AtomicOp requests (Device Control 2): |
Clocks Event Reasons
Each row is Active when that reason holds the GPU clock back, otherwise Not Active. clocks.throttle.reason gives the active ones as a single list.
Row |
Details |
Meaning |
|---|---|---|
Fan Speed
|
Section: Unit: % Source: |
Fan speed, averaged across the device’s fans. Printed where the driver supplies it; |
Performance Factor > Compute
|
Section: Source: |
How the hardware trades frequency toward the compute engines, 0-100; 50 is balanced. Printed where the driver supplies it; |
Performance Factor > Media
|
Section: Source: |
The same for the media engines. Printed where the driver supplies it; |
PCI
Clocks Event Reasons > Thermal Limit
|
Section: Source: |
The thermal limit. |
|---|---|---|
Clocks Event Reasons > Average Power Cap
|
Section: Source: |
The average (sustained) power limit. |
Clocks Event Reasons > Burst Power Cap
|
Section: Source: |
The burst power limit. |
Clocks Event Reasons > Current Limit
|
Section: Source: |
The electrical current limit. |
Clocks Event Reasons > PSU Alert
|
Section: Source: |
A power supply alert. |
Clocks Event Reasons > SW Range
|
Section: Source: |
The frequency range set in software, e.g. with |
Clocks Event Reasons > HW Range
|
Section: Source: |
The frequency range the hardware allows. |
Clocks Event Reasons > Voltage
|
Section: Source: |
The voltage limit. |
Clocks Event Reasons > Thermal Alert
|
Section: Source: |
A thermal alert. |
Clocks Event Reasons > Power Alert
|
Section: Source: |
A power alert. |
Clocks Event Reasons Counters > Throttled Time
|
Section: Unit: us Source: |
Time the GPU clock has been held back by any throttle reason, accumulated by the driver. Printed where the driver supplies it; |
Memory and compute
Row |
Details |
Meaning |
|---|---|---|
FB Memory Usage > Total
|
Section: Unit: MiB Source: |
Device memory the driver manages. |
FB Memory Usage > Reserved
|
Section: Unit: MiB Source: |
Memory the driver keeps back: installed size minus Total. Used includes it, so Total is Used plus Free. |
FB Memory Usage > Used
|
Section: Unit: MiB Source: |
Device memory in use. |
FB Memory Usage > Free
|
Section: Unit: MiB Source: |
Device memory free. |
BAR Memory > Total
|
Section: Unit: MiB Source: |
Size of the device’s largest memory BAR, the window through which the host reaches its local memory. Nothing reports how much of it is in use. |
BAR Memory > Resizable BAR
|
Section: Source: |
Whether Resizable BAR is on for that BAR: |
Memory Info > Memory Type
|
Section: Source: discovery Memory Type |
Kind of device memory, e.g. |
Memory Info > Number of Memory Channels
|
Section: Source: discovery Number of Memory Channels |
Memory channels. |
Memory Info > Memory Bus Width
|
Section: Unit: bits Source: discovery Memory Bus Width |
Width of the memory bus. |
Scheduler Mode
|
Section: Source: |
How the device schedules work: |
Compute Resources > Number of Tiles
|
Section: Source: discovery Number of Tiles |
Tiles (sub-devices) on the device. |
Compute Resources > Number of Slices
|
Section: Source: discovery Number of Slices |
Slices in each tile. |
Compute Resources > Number of Sub-slices per Slice
|
Section: Source: discovery Number of Sub-slices per Slice |
Sub-slices in each slice. |
Compute Resources > Number of EUs
|
Section: Source: discovery Number of EUs |
Execution units on the device. |
Utilization
Measured over the sampling window. Engine utilization needs CAP_PERFMON; without it the values come from the processes’ DRM file statistics where the kernel provides them.
Row |
Details |
Meaning |
|---|---|---|
Utilization > GPU
|
Section: Unit: % Source: |
Share of the window the busiest engine was busy: from the engine counters, otherwise from the per-process engine times in fdinfo. Never from the EU array, whose metric stream is slow to open; |
Utilization > Memory
|
Section: Unit: % Source: |
Memory bandwidth used, as a share of the most the memory allows. |
Utilization > Compute
|
Section: Unit: % Source: |
Busiest compute engine. |
Utilization > Render
|
Section: Unit: % Source: |
Busiest render engine. |
Utilization > Media
|
Section: Unit: % Source: |
Busiest media engine. |
Utilization > Video
|
Section: Unit: % Source: |
Busiest video decode/encode engine. Linux runs decode and encode on one engine class, so they share this figure. From the engine counters, otherwise fdinfo; never the EU array. |
Utilization > Video Enhancement
|
Section: Unit: % Source: |
Busiest video enhancement engine (scaling, color conversion). |
Utilization > Copy
|
Section: Unit: % Source: |
Busiest copy engine. |
Temperature
The shutdown and slowdown rows are configured thresholds, the ones the health command compares against, not sensor readings.
Row |
Details |
Meaning |
|---|---|---|
Temperature > GPU Current Temp
|
Section: Unit: C Source: |
GPU core temperature. |
Temperature > GPU Shutdown Temp
|
Section: Unit: C Source: |
GPU core temperature at which the device shuts down: the threshold configured for the device, otherwise xpu-smi’s default (130 C) lowered to the driver’s maximum for the sensor (125 C on CRI). |
Temperature > GPU Slowdown Temp
|
Section: Unit: C Source: |
GPU core temperature at which the clock is throttled. |
Temperature > GPU Max Operating Temp
|
Section: Unit: C Source: |
Highest temperature the driver says the GPU sensor can operate at; 125 C on CRI. Left out where the driver reports none. |
Temperature > Memory Current Temp
|
Section: Unit: C Source: |
Memory temperature. |
Temperature > Memory Shutdown Temp
|
Section: Unit: C Source: |
Memory temperature at which the device shuts down: the configured threshold, otherwise xpu-smi’s default (100 C) lowered to the driver’s maximum, if lower. |
Temperature > Memory Slowdown Temp
|
Section: Unit: C Source: |
Memory temperature at which the clock is throttled. |
Temperature > Memory Max Operating Temp
|
Section: Unit: C Source: |
The same for the memory sensor. |
Power and clocks
Row |
Details |
Meaning |
|---|---|---|
GPU Power Readings > Average Power Draw
|
Section: Unit: W Source: |
Power the card drew, averaged over the sampling window. |
GPU Power Readings > Instantaneous Power Draw
|
Section: Unit: W Source: |
Card power at one moment, as the driver reports it ( |
GPU Power Readings > GPU Domain Power Draw
|
Section: Unit: W Source: |
The GPU power domain’s share, averaged over the sampling window. |
GPU Power Readings > Current Power Limit
|
Section: Unit: W Source: |
Power limit in force: the sustained limit, or the burst or peak limit on a device without one. |
GPU Power Readings > Burst Power Limit
|
Section: Unit: W Source: |
Burst power limit (PL2), on devices that report one. |
GPU Power Readings > Peak Power Limit
|
Section: Unit: W Source: |
Peak power limit (PL4), on devices that report one. Current Power Limit shows it on a device with no sustained or burst limit. |
GPU Power Readings > Default Power Limit
|
Section: Unit: W Source: |
Default power limit from the device properties. Printed where the driver supplies it; |
GPU Power Readings > Min Power Limit
|
Section: Unit: W Source: |
Lowest power limit that can be set. Printed where the driver supplies it; |
GPU Power Readings > Max Power Limit
|
Section: Unit: W Source: |
Highest power limit that can be set. Printed where the driver supplies it; |
GPU Power Readings > Memory Power Draw
|
Section: Unit: W Source: |
Memory power domain at one moment, on devices with one (the B580 has one; CRI does not). |
Clocks > Graphics
|
Section: Unit: MHz Source: |
Current GPU core clock. |
Clocks > Memory
|
Section: Unit: MHz Source: |
Current memory clock. |
Clocks > Media
|
Section: Unit: MHz Source: |
Current media engine clock; can read |
Applications Clocks > Graphics
|
Section: Unit: MHz Source: |
GPU core clock the driver last requested, which the GPU runs at unless a clock event reason holds it back. |
Max Clocks > Graphics
|
Section: Unit: MHz Source: |
Highest GPU core clock the device supports. |
Max Clocks > Media
|
Section: Unit: MHz Source: |
Highest media engine clock the device supports. |
Supported Clocks > Graphics
|
Section: Unit: MHz Source: |
GPU core clocks the minimum and maximum of |
Processes
One record per process using the device; None when there is none. In JSON, processes is an array of objects with the keys below.
Row |
Details |
Meaning |
|---|---|---|
Processes > Process ID
|
Section: Source: |
Process ID. |
Processes > Type
|
Section: Source: |
Engine the process uses: |
Processes > Name
|
Section: Source: |
Command name. |
Processes > Used GPU Memory
|
Section: Unit: MiB Source: |
Device memory the process holds. |
Reading the Report
A value the device, driver or platform cannot supply prints as
N/A. Where the value needs something the caller lacks, the text report says what, for exampleN/A (requires CAP_SYS_ADMIN):CAP_SYS_ADMINfor the PCIe link generation and width, the atomic capabilities and Resizable BAR, which come from PCI configuration space;CAP_PERFMONfor engine utilization; read-write access to the device’s/dev/mei*node for the GFX firmware version. The report prints no diagnostic for such a value; setXPU_SMI_LOG_LEVEL=DBGto see why one is missing.Measured values (power draw, utilization, throughput, bandwidth) are averaged over a 200 ms window that the first report waits for. In a loop each later report averages over the time since the previous one.
Values with a unit are shown to two decimals. JSON keeps the full precision.
GPU IP Version is the graphics IP version the driver reports, in hex. It identifies the architecture: newer devices have higher values.
The report has no ECC section for now: ECC mode, the ECC and RAS error counts, Offline Pages and Memory Repair are left out until reading the driver’s RAS counters is reliable. Use
--query-gpu(for example--query-gpu ecc.errors.aggregate.total) orstats -rfor them meanwhile.PCI: Host Max is the link capability of the root port the device is under, the CPU end of the path; a switch in between can limit the link further. PCIe Errors are the device’s AER counters since it was enumerated, and Atomic Caps Inbound and Atomic Requests come from its PCI Express capability, which needs root. All of these are Linux only, and left out where the device or OS does not report them.
Fan Speed, the Performance Factors, Throttled Time, PCIe Replays Since Reset, the default, minimum and maximum power limits and Memory Power Draw come from Level Zero calls that many drivers do not implement; CRI’s driver supplies none of them. They are printed where the driver supplies a value, and with
--verboseotherwise.GPU Power Readings: Average Power Draw is the card’s draw over the window, Instantaneous Power Draw the driver’s reading at one moment, and GPU Domain Power Draw the GPU domain’s share. Current Power Limit is the sustained limit, or the burst or peak limit on a device without one; the burst and peak limits are listed on devices that report them.
BAR Memory is the device’s largest memory BAR, through which the host reaches device memory. Resizable BAR says whether it was resized; the driver reads that from PCI configuration space.
FB Memory Usage: Reserved is memory the driver keeps back (installed size minus Total). Used counts it, so Total is Used plus Free. A memory clock the driver reports as 0 reads
N/A.Utilization comes from the Sysman engine counters, or from the per-process engine times in fdinfo where those are unavailable; never from the EU array, whose metric stream is slow to open. Video and Video Enhancement split Media into its decode/encode engines (which Linux reports as one) and its enhancement engines, on devices that have them.
GPU utilization is the busiest engine’s share of the window. An engine counts as busy for all the time it has work scheduled, so it can read higher than
eu.activeunder the same workload.Applications Clocks shows the graphics clock the driver last requested, which the GPU runs at unless a throttle reason holds it back. Minor Number is the number of the device’s DRM card node, and reads
N/Aon Windows. Slot Number is the physical PCI slot the platform firmware names, and readsN/Aon systems whose firmware names none.GPU Recovery Action says what the driver reports the device needs:
None,Reset(for example a wedged device), orReset to repair.As root, the GFX firmware version is read from the GSC firmware interface, which takes about 200 ms per device on some platforms. Devices are read in parallel, and the read overlaps the measurement window. On a device with an AMC the serial number and the board part number are read from the AMC, one after the other.
The slowdown and shutdown temperatures are the configured thresholds the Health command compares against, not sensor readings. Without a threshold configured for the device, the default shutdown temperature is lowered to the driver’s maximum for that sensor, as on CRI (125 C). The max operating temperatures are what the driver reports for each sensor, on devices that report one.
On Windows the kernel-mode driver version reads
N/A.Rows only some devices or drivers supply, such as the burst and peak power limits, are left out on a device without them, so it does not fill with
N/A; the JSON output leaves out the same rows.--verboseprints them all, andNot Supportedfor a value the driver or OS says the device does not support; a value missing for another or an unknown reason staysN/A.
A device in survivability mode is listed with only its state and the recovery action
(Firmware update and GPU reset).
JSON Output
--json prints one object. Its keys are the lower-case, underscore-separated form of the
labels in the text report, and it has the same rows: a row the text leaves out is not a key,
and --verbose adds them to both. A value that is not available, printed N/A in the
text, is null. Numbers are strings in the unit shown in the text report, and processes
is an array.
{
"timestamp": "2026-10-21T13:28:16Z",
"umd_version": "1.17.39980",
"kmd_version": null,
"level_zero_version": "1.33.1",
"attached_gpus": 1,
"gpus": [
{
"pci_bus_id": "0000:03:00.0",
"product_name": "Intel(R) Arc(TM) B580 Graphics",
"fb_memory_usage": {
"total": "12216",
"reserved": "0",
"used": "218.62109375",
"free": "11997.37890625"
},
"processes": []
}
]
}
Examples
Report on every device:
xpu-smi query
Report only memory and power for device 0:
xpu-smi query --device 0 --display MEMORY,POWER
Save a report to a file:
xpu-smi query --file report.txt
Print the power and temperature sections every 5 seconds, 12 times, as JSON:
xpu-smi query --display POWER,TEMPERATURE --json --loop 5 --count 12