| 1 |
.TH "nvme_mi_aem_process" 9 "nvme_mi_aem_process" "November 2025" "libnvme API manual" LINUX |
| 2 |
.SH NAME |
| 3 |
nvme_mi_aem_process \- Process AEM on the provided endpoint |
| 4 |
.SH SYNOPSIS |
| 5 |
.B "int" nvme_mi_aem_process |
| 6 |
.BI "(nvme_mi_ep_t ep " "," |
| 7 |
.BI "void *userdata " ");" |
| 8 |
.SH ARGUMENTS |
| 9 |
.IP "ep" 12 |
| 10 |
Endpoint to process |
| 11 |
.IP "userdata" 12 |
| 12 |
Application provided context pointer for callback function |
| 13 |
.SH "DESCRIPTION" |
| 14 |
Call this if \fBpoll\fP indicates data is available on the fd provided by \fBnvme_mi_aem_get_fd\fP |
| 15 |
|
| 16 |
This will call the fn pointer, aem_handler, provided with nvme_mi_aem_config and the |
| 17 |
application can call \fBnvme_mi_aem_get_next_event\fP from within this callback to get |
| 18 |
aem event data. The callback function should return NVME_MI_AEM_HNA_ACK for normal operation. |
| 19 |
.SH "RETURN" |
| 20 |
0 is a success, nonzero is an error and errno may be read for further details |