NVME-GET-REG(1)

📦 version 3.2, in arch rolling

💅 NVME-GET-REG 💅

okay so this is a page from the nvme manual and honestly? it's a little baddie. it's called nvme-get-reg and it's here to read controller registers and show you what's inside. let's get into it 🫶

✨ NAME ✨

nvme-get-reg — read and show the defined NVMe controller register 💖

🌸 SYNOPSIS 🌸

nvme [<global-options>] get-reg <device>
                        [--register=<name>[,<name>...] | -r <name>[,<name>...]]
                        [--offset=<offset> | -O <offset>]

🦋 DESCRIPTION 🦋

so basically it reads controller registers and shows them to you 👑 and it does this two different ways depending on the vibe of your controller:

  • for an NVMe over PCIe controller, it reads them from its PCI memory space
  • for an NVMe over Fabrics controller, it reads its properties with Property Get commands

the <device> parameter is mandatory — no cap, you cannot skip it — and it has to be the nvme admin character device (example: /dev/nvme0). 💅

on a fabrics controller: if you ask for a register that isn't a property of a fabrics controller, or a property the controller doesn't implement, the command fails — but only after the other registers are shown. so you get the tea first, then the error. 😭

🎀 OPTIONS 🎀

  • -r <name>[,<name>...], --register=<name>[,<name>...] — the registers to show, by name, in register order. pick from: cap, vs, intms, intmc, cc, csts, nssr, aqa, asq, acq, cmbloc, cmbsz, bpinfo, bprsel, bpmbl, cmbmsc, cmbsts, cmbebs, cmbswtp, nssd, crto, pmrcap, pmrctl, pmrsts, pmrebs, pmrswtp, pmrmscl, pmrmscu. and yes bestie, the option may be given more than once 🧚
  • -O <offset>, --offset=<offset> — a register to show, by offset or name, e.g. 0x14 or cc. the offset has to be the one of a register, ok? it can't just be any random number you feel like typing 🙈
⚠️ ok so the options --cap, --vs, --cc and so on from earlier versions — one for each register — still work, but they're deprecated: use --register. like they still slay but they're kinda living in the past 💀

🌈 GLOBAL OPTIONS 🌈

these are defined at the top-level nvme command and they're available to this subcommand:

  • --dry-run — print the command that would be executed, but do not actually execute it. all the planning, none of the commitment 💅
  • --no-ioctl-probing — disable probing for 64-bit IOCTL support.
  • --no-retries — disable retry logic on transient errors.
  • -o <fmt>, --output-format=<fmt> — set the reporting format to normal, tabular, json, or binary. only one output format may be used at a time, so don't get greedy 😌
  • --output-format-version=<version> — select the output format version. version 1 uses the original field naming, while version 2 (default) provides more consistent and script-friendly field names. other versions are rejected — no negotiating 🚫
  • --quiet — suppress informational messages. errors are still reported, and --quiet cancels any --verbose for the library log level. it's giving "i'm not reading all that" ✨
  • --set-options=<key=value>[,<key=value>...] — set libnvme library options for this invocation. supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir.
  • --timeout=<ms> — set the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). literally forever. bestie will wait 🫶
  • -v, --verbose — increase the level of detail in the output. may be specified multiple times to further increase verbosity. stack 'em 👑

these options can also be set as machine-wide defaults in nvme-cli.conf(5). a command-line flag always overrides the file — CLI stays the main character 👑

with -v, the fields of each register are shown decoded. the JSON output has the value of each register under its name, and with -v you get an object of the value and its decoded fields:

{
  "cc": 4587521
}

⭐ EXAMPLES ⭐

  • show the Controller Configuration register
# nvme get-reg /dev/nvme0 --register=cc
register : 0x14 (Controller Configuration), value: 0x460001
  • show the Controller Capabilities and Status registers, decoded
# nvme get-reg /dev/nvme0 -r cap,csts -v

💜 NVME 💜

part of the nvme-user suite. iykyk 💅

and that's the whole page bestie, no notes 🎀 this was the NVMe manual, NVME-GET-REG(1), dated 10/30/2026 — go read your registers, they're literally iconic ✨👑🔥

📦 where this page comes from