1libnvme(9)                        API Manual                        libnvme(9)
2
3
4

NAME

6       struct nvme_telemetry_log - Retrieve internal data specific to the man‐
7       ufacturer.
8

SYNOPSIS

10       struct nvme_telemetry_log {
11           __u8 lpi;
12           __u8 rsvd1[4];
13           __u8 ieee[3];
14           __le16 dalb1;
15           __le16 dalb2;
16           __le16 dalb3;
17           __u8 rsvd14[2];
18           __le32 dalb4;
19           __u8 rsvd20[361];
20           __u8 hostdgn;
21           __u8 ctrlavail;
22           __u8 ctrldgn;
23           __u8 rsnident[128];
24           __u8 data_area[];
25        };
26
27

Members

29       lpi         Log  Identifier,  either   NVME_LOG_LID_TELEMETRY_HOST   or
30                   NVME_LOG_LID_TELEMETRY_CTRL
31
32       rsvd1       Reserved
33
34       ieee        IEEE  OUI  Identifier is the Organization Unique Identifier
35                   (OUI) for the controller vendor that is able  to  interpret
36                   the data.
37
38       dalb1       Telemetry  Controller-Initiated  Data  Area 1 Last Block is
39                   the value of the last block in this area.
40
41       dalb2       Telemetry Controller-Initiated Data Area 1  Last  Block  is
42                   the value of the last block in this area.
43
44       dalb3       Telemetry  Controller-Initiated  Data  Area 1 Last Block is
45                   the value of the last block in this area.
46
47       rsvd14      Reserved
48
49       dalb4       Telemetry Controller-Initiated Data Area 4  Last  Block  is
50                   the value of the last block in this area.
51
52       rsvd20      Reserved
53
54       hostdgn     Telemetry  Host-Initiated Data Generation Number is a value
55                   that is incremented each time the host initiates a  capture
56                   of its internal controller state in the controller .
57
58       ctrlavail   Telemetry  Controller-Initiated Data Available, if cleared,
59                   then the controller telemetry log does  not  contain  saved
60                   internal  controller state. If this field is set to 1h, the
61                   controller log contains saved internal controller state. If
62                   this field is set to 1h, the data will be latched until the
63                   host releases it by reading the log with RAE cleared.
64
65       ctrldgn     Telemetry Controller-Initiated Data Generation Number is  a
66                   value  that  is incremented each time the controller initi‐
67                   ates a capture of its internal controller state in the con‐
68                   troller .
69
70       rsnident    Reason  Identifiers  a  vendor specific identifier that de‐
71                   scribes the operating conditions of the controller  at  the
72                   time of capture.
73
74       data_area   Telemetry data blocks, vendor specific information data.
75

Description

77       This  log  consists  of  a  header  describing the log and zero or more
78       Telemetry   Data   Blocks.    All    Telemetry    Data    Blocks    are
79       NVME_LOG_TELEM_BLOCK_SIZE,  512  bytes,  in size. This log captures the
80       controller’s internal state.
81
82
83
84October 2023               struct nvme_telemetry_log                libnvme(9)
Impressum