nvme1.3 Get Log Page Command - Telemetry

5.14 Get Log Page Command

5.14.1.7 Telemetry Host-initiated(Log Identifier 07h)

这种log由头信息和Telemetry Data Blocks组成(参见8.14)。所有的Telemetry Data Blocks都是由512Byte为单位。当Controller要处理一条Get Log Page命令且Log Specific字段中的Create Telemetry Host-Initiated Data bit为1时，Controller应当将Controller的内部状态放入此Log Page。如果Host指定的Log Page Offset Lower值不是512Byte的倍数，那么Controller应当返回一个Invalid Field。

Bits	Description
11：09	Reserved
08	Create Telemetry Host-Initiated Data:如果设置为1，则Controller应当截取此时Controller内部状态的Telemetry Host-Initiated Data返回给Get Log Page命令。如果清0，则Controller不会更新Telemetry Host-Initiated,一直到： 此bit被设置为1； 收到了Firmware Commit命令； Power On Reset。

 

Telemetry Host-Initiated Data有三个区域组成：Telemetry Host-Initiated Data Area 1,Telemetry Host-Initiated Data Area 2和Telemetry Host-Initiated Data Area 3。三个区域都会已Telemetry Host-Initiated Data Area Block 1作为起始。最后一个Block会以Telemetry Host-Initiated Data Area y Last Block作为结束。遥测数据的获取和大小是基于厂商定义的。Log page的大小是基于Telemetry Host-Initiated Data Area y Last Block可变的。

Controller应当返回所有请求的数据。超出elemetry Host-Initiated Data Area y Last Block的数据时未定义的。当host请求的数据不是512Byte的倍数时，Controller应当返回invalid Field。

Figure 203: Get Log Page  Telemetry Controller-Initiated Log (Log Identifier 08h)

Bytes	Description
00	Log Identifier: This field shall be set to 07h
04:01	Reserved
07:05	IEEE OUI Identifier (IEEE): Contains the Organization Unique Identifier (OUI) for the controller vendor that is able to interpret the data. If cleared to 0h, no IEEE OUI Identifier is present. The OUI shall be a valid IEEE/RAC assigned identifier that is registered at http://standards.ieee.org/develop/regauth/oui/public.html.
09:08	Telemetry Host-Initiated Data Area 1 Last Block: Contains the value of the last block of Telemetry Host-Initiated Data Area 1. If the Telemetry Host-Initiated Data Area 1 does not contain data, then this field shall be cleared to 0h. If this field is not 0h, then Telemetry Host-Initiated Data Area 1 begins at block 1h and ends at the block indicated in this field.
11:10	Telemetry Host-Initiated Data Area 2 Last Block: Contains the value of the last block of Telemetry Host-Initiated Data Area 2. This value shall be greater than or equal to the value in the Telemetry Host-Initiated Data Area 1 Last Block field. If this field is not 0h, then Telemetry Host-Initiated Data Area 2 begins at block 1h and ends at the block indicated in this field.
13:12	Telemetry Host-Initiated Data Area 3 Last Block: Contains the value of the last block of Telemetry Host-Initiated Data Area 3. This value shall be greater than or equal to the value in the Telemetry Host-Initiated Data Area 2 Last Block field. If this field is not 0h, then Telemetry Host-Initiated Data Area 3 begins at block 1h and ends at the block contained in this field.
381:14	Reserved
382	Telemetry Controller-Initiated Data Available: Contains the value of Telemetry Controller-Initiated Data Available field in the Telemetry Controller-Initiated log (refer to Figure 203).
383	Telemetry Controller-Initiated Data Generation Number: Contains the value of the Telemetry Controller-Initiated Data Generation Number field in the Telemetry Controller- Initiated log (refer to Figure 203).
511:384	Reason Identifier: Contains a vendor specific identifier that describes the operating conditions of the controller at the time of capture. The Reason Identifier field should provide an identification of unique operating conditions of the controller.
1023:512	Telemetry Host-Initiated Data Block 1: Contains Telemetry Data Block 1 for the Telemetry Host-Initiated Log.
1535:1024	Telemetry Host-Initiated Data Block 2: Contains Telemetry Data Block 2 for the Telemetry Host-Initiated Log.
...	...
(n*512)+511:(n*512)	Telemetry Host-Initiated Data Block n: Contains Telemetry Data Block n for the Telemetry Host-Initiated Log.

 

5.14.1.8 Telemetry Controller-Initiated (Log Identifier 08h)

Bytes	Description
00	Log Identifier: This field shall be set to 08h
04:01	Reserved
07:05	IEEE OUI Identifier (IEEE): Contains the Organization Unique Identifier (OUI) for the controller vendor that is able to interpret the data. If cleared to 0h, no IEEE OUI Identifier is present. The OUI shall be a valid IEEE/RAC assigned identifier that is registered at http://standards.ieee.org/develop/regauth/oui/public.html.
09:08	Telemetry Controller-Initiated Data Area 1 Last Block: Contains the value of the last block of Telemetry Controller-Initiated Data Area 1. If the Telemetry Controller- Initiated Data Area 1 does not contain data, then this field shall be cleared to 0h. If this field is not 0h, then Telemetry Controller-Initiated Data Area 1 begins at block 1 and ends at the block indicated in this field.
11:10	Telemetry Controller-Initiated Data Area 2 Last Block: Contains the value of the last block of Telemetry Controller-Initiated Data Area 2. This value shall be greater than or equal to the value in the Telemetry Controller-Initiated Data Area 1 Last Block field. If this field is not 0h, then Telemetry Controller-Initiated Data Area 2 begins at block 1h and ends at the block indicated in this field.
13:12	Telemetry Controller-Initiated Data Area 3 Last Block: Contains the value of the last block of Telemetry Controller-Initiated Data Area 3. This value shall be greater than or equal to the value in the Telemetry Controller-Initiated Data Area 2 Last Block field. If this field is not 0h, then Telemetry Controller-Initiated Data Area 3 begins at block 1h and ends at the block indicated in this field.
381:14	Reserved
382	Telemetry Controller-Initiated Data Available: If this field is cleared to 0h, the log does not contain saved internal controller state. If this field is set to 1h, the log contains saved internal controller state. If this field is set to 1h, it shall not be cleared to 0h until a Get Log Page command with Retain Asynchronous Event bit cleared to \u20180\u2019 for the Telemetry Controller-Initiated log completes successfully. This value is persistent across power states and reset. Other values are reserved.
383	Telemetry Controller-Initiated Data Generation Number: Contains a value that is incremented each time the controller initiates a capture of its internal controller state into the Telemetry Controller-Initiated Data Blocks. If the value of this field is FFh, then the field shall be cleared to 0h when incremented (i.e., rolls over to 0h). This field is persistent across power on.
511:384	Reason Identifier: Contains a vendor specific identifier that describes the operating conditions of the controller at the time of capture. The Controller-Initiated Reason Identifier field should provide an identification of unique operating conditions of the controller.
1023:512	Telemetry Controller-Initiated Data Block 1: Contains Telemetry Data Block 1 for the Telemetry Controller -Initiated Log captured at a vendor specific time.
1535:1024	Telemetry Controller-Initiated Data Block 2: Contains Telemetry Data Block 2 for the Telemetry Controller -Initiated Log captured at a vendor specific time.
...	...
(n*512)+511:(n*512)	Telemetry Controller-Initiated Data Block n: Contains Telemetry Data Block n for the Telemetry Controller-Initiated log captured at a vendor specific time.