Nvidia MSTFLINT Documentation page 82

Hide thumbs Also See for MSTFLINT:
Table of Contents

Advertisement

mstresourcedump dump Usage 
mstresourcedump dump [-h] --device DEVICE --segment SEGMENT [--virtual-hca-id VIRTUAL_HCA_ID] [--index1 INDEX1] [--
index2 INDEX2] [--num-of-obj1 NUM_OF_OBJ1] [--num-of-obj2 NUM_OF_OBJ2] [--depth DEPTH] [--bin BIN]
where
-h, --help
--virtual-hca-id 
--index1
--index2
--num-of-obj1
--num-of-obj2
--depth
--bin
-d, --device
--segment
--mem
Examples of how to:
run the dump command: 
# mstresourcedump dump --device
Found
10
segments:
-------------------------------------------
Segment Type:
0xfffe
Segment Size:
16
Segment Data:
0x0004FFFE 0x00000000 0x00000000 0x101A0111
-------------------------------------------
Segment Type:
0xfffa
Segment Size:
20
Segment Data:
0x0005FFFA 0x12000000 0x00000404 0x00000000
0x00000000
-------------------------------------------
Show help message and exit
The virtual HCA (host channel adapter, NIC) ID
The first context index to dump (if supported for this segment)
The second context index to dump (if supported for this segment)
The number of objects to be dumped (if supported for this
segment). accepts: ["all", "active", number, depends on the
capabilities]
The number of objects to be dumped (if supported for this
segment). accepts: ["all", "active", number, depends on the
capabilities]
The depth of walking through reference segments. 0 stands for flat,
1 allows crawling of a single layer down the struct, etc. "inf" for all
The output to a binary file that replaces the default print in
hexadecimal, a readable format
The device name
The segment to dump
Perform the dump through memory (ofed with rdma-core
dependency).
Accepts: [ibv device (for example "mlx5_4")] 
04:00.0
--segment
Bytes
Bytes
0x1200
--index1
0x404
--depth
0
82

Advertisement

Table of Contents
loading

Table of Contents