| 1 |
.TH "libnvme" 9 "struct nvme_self_test_log" "November 2025" "API Manual" LINUX |
| 2 |
.SH NAME |
| 3 |
struct nvme_self_test_log \- Device Self-test (Log Identifier 06h) |
| 4 |
.SH SYNOPSIS |
| 5 |
struct nvme_self_test_log { |
| 6 |
.br |
| 7 |
.BI " __u8 current_operation;" |
| 8 |
.br |
| 9 |
.BI " __u8 completion;" |
| 10 |
.br |
| 11 |
.BI " __u8 rsvd[2];" |
| 12 |
.br |
| 13 |
.BI " struct nvme_st_result result[NVME_LOG_ST_MAX_RESULTS];" |
| 14 |
.br |
| 15 |
.BI " |
| 16 |
}; |
| 17 |
.br |
| 18 |
|
| 19 |
.SH Members |
| 20 |
.IP "current_operation" 12 |
| 21 |
Current Device Self-Test Operation: indicates the status |
| 22 |
of the current device self-test operation. If a device |
| 23 |
self-test operation is in process (i.e., this field is set |
| 24 |
to #NVME_ST_CURR_OP_SHORT or #NVME_ST_CURR_OP_EXTENDED), |
| 25 |
then the controller shall not set this field to |
| 26 |
#NVME_ST_CURR_OP_NOT_RUNNING until a new Self-test Result |
| 27 |
Data Structure is created (i.e., if a device self-test |
| 28 |
operation completes or is aborted, then the controller |
| 29 |
shall create a Self-test Result Data Structure prior to |
| 30 |
setting this field to #NVME_ST_CURR_OP_NOT_RUNNING). |
| 31 |
See \fIenum nvme_st_curr_op\fP. |
| 32 |
.IP "completion" 12 |
| 33 |
Current Device Self-Test Completion: indicates the percentage |
| 34 |
of the device self-test operation that is complete (e.g., |
| 35 |
a value of 25 indicates that 25% of the device self-test |
| 36 |
operation is complete and 75% remains to be tested). |
| 37 |
If the \fIcurrent_operation\fP field is cleared to |
| 38 |
#NVME_ST_CURR_OP_NOT_RUNNING (indicating there is no device |
| 39 |
self-test operation in progress), then this field is ignored. |
| 40 |
.IP "rsvd" 12 |
| 41 |
Reserved |
| 42 |
.IP "result" 12 |
| 43 |
Self-test Result Data Structures, see \fIstruct nvme_st_result\fP. |