From 9cd3e2c64f889a48b0d14bda22e867722b55497e Mon Sep 17 00:00:00 2001 From: Jacob Keller Date: Thu, 9 Jan 2020 14:46:25 -0800 Subject: devlink: document region snapshot triggering from userspace Now that devlink regions can be triggered via DEVLINK_CMD_REGION_TRIGGER, document this in the devlink-region.rst file. Signed-off-by: Jacob Keller Signed-off-by: David S. Miller --- Documentation/networking/devlink/devlink-region.rst | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) (limited to 'Documentation/networking') diff --git a/Documentation/networking/devlink/devlink-region.rst b/Documentation/networking/devlink/devlink-region.rst index efa11b9a20da..1a7683e7acb2 100644 --- a/Documentation/networking/devlink/devlink-region.rst +++ b/Documentation/networking/devlink/devlink-region.rst @@ -12,10 +12,13 @@ region can then be accessed via the devlink region interface. Region snapshots are collected by the driver, and can be accessed via read or dump commands. This allows future analysis on the created snapshots. +Regions may optionally support triggering snapshots on demand. The major benefit to creating a region is to provide access to internal -address regions that are otherwise inaccessible to the user. They can be -used to provide an additional way to debug complex error states. +address regions that are otherwise inaccessible to the user. + +Regions may also be used to provide an additional way to debug complex error +states, but see also :doc:`devlink-health` example usage ------------- @@ -37,6 +40,9 @@ example usage # Delete a snapshot using: $ devlink region del pci/0000:00:05.0/cr-space snapshot 1 + # Trigger (request) a snapshot be taken: + $ devlink region trigger pci/0000:00:05.0/cr-space + # Dump a snapshot: $ devlink region dump pci/0000:00:05.0/fw-health snapshot 1 0000000000000000 0014 95dc 0014 9514 0035 1670 0034 db30 -- cgit v1.2.3-59-g8ed1b