ice_devlink_nvm_snapshot(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ NAME πŸŽ€

ice_devlink_nvm_snapshot β€” capture a snapshot of the NVM flash contents. This is the Kernel API Manual page for ice_devlink_nvm_snapshot(9), and she is literally here to grab flash contents for you, bestie. πŸ’–


✨ SYNOPSIS ✨

okay so here’s the exact signature, no edits, no cap:

int ice_devlink_nvm_snapshot (struct devlink *devlink , const struct
       devlink_region_ops *ops , struct netlink_ext_ack *extack , u8 **data );

πŸ’… ARGUMENTS πŸ’…

  • devlink β€” the devlink instance. Main character pointer energy.
  • ops β€” the devlink region to snapshot. This is the region we’re serving.
  • extack β€” extended ACK response structure.
  • data β€” on exit points to snapshot data buffer. Yes, it’s the output bestie.

πŸ¦‹ DESCRIPTION πŸ¦‹

This function is called in response to a DEVLINK_CMD_REGION_NEW for either the nvm-flash or shadow-ram region.

It captures a snapshot of the NVM or Shadow RAM flash contents. This snapshot can then later be viewed via the DEVLINK_CMD_REGION_READ netlink interface. Obsessed with the whole pipeline. 🌈

It returns zero on success, and updates the data pointer. Returns a non-zero error code on failure. So: success = zero, failure = non-zero. That’s the whole vibe check. πŸ’€


🌈 SEE ALSO 🌈

the whole friend group:


πŸ’– That’s the page, bestie! This one came from the Kernel API Manual; source/version: ./drivers/net/ethernet/intel/i...; date: October 2026; page: ice_devlink_nvm_snapshot(9). Slay and goodbye. πŸ’…

πŸ“¦ where this page comes from