nvme_telemetry_log - Man Page
Retrieve internal data specific to the manufacturer.
Synopsis
struct nvme_telemetry_log {
__u8 lpi;
__u8 rsvd1[4];
__u8 ieee[3];
__le16 dalb1;
__le16 dalb2;
__le16 dalb3;
__u8 rsvd14[2];
__le32 dalb4;
__u8 rsvd20[361];
__u8 hostdgn;
__u8 ctrlavail;
__u8 ctrldgn;
__u8 rsnident[128];
__u8 data_area[];
};
Members
- lpi
Log Identifier, either NVME_LOG_LID_TELEMETRY_HOST or NVME_LOG_LID_TELEMETRY_CTRL
- rsvd1
Reserved
- ieee
IEEE OUI Identifier is the Organization Unique Identifier (OUI) for the controller vendor that is able to interpret the data.
- dalb1
Telemetry Controller-Initiated Data Area 1 Last Block is the value of the last block in this area.
- dalb2
Telemetry Controller-Initiated Data Area 1 Last Block is the value of the last block in this area.
- dalb3
Telemetry Controller-Initiated Data Area 1 Last Block is the value of the last block in this area.
- rsvd14
Reserved
- dalb4
Telemetry Controller-Initiated Data Area 4 Last Block is the value of the last block in this area.
- rsvd20
Reserved
- hostdgn
Telemetry Host-Initiated Data Generation Number is a value that is incremented each time the host initiates a capture of its internal controller state in the controller .
- ctrlavail
Telemetry Controller-Initiated Data Available, if cleared, then the controller telemetry log does not contain saved internal controller state. If this field is set to 1h, the controller log contains saved internal controller state. If this field is set to 1h, the data will be latched until the host releases it by reading the log with RAE cleared.
- ctrldgn
Telemetry Controller-Initiated Data Generation Number is a value that is incremented each time the controller initiates a capture of its internal controller state in the controller .
- rsnident
Reason Identifiers a vendor specific identifier that describes the operating conditions of the controller at the time of capture.
- data_area
Telemetry data blocks, vendor specific information data.
Description
This log consists of a header describing the log and zero or more Telemetry Data Blocks. All Telemetry Data Blocks are NVME_LOG_TELEM_BLOCK_SIZE, 512 bytes, in size. This log captures the controller’s internal state.