Debian Codegraph @

doc/man/nvme_mi_event.2

raw
1 .TH "libnvme" 9 "struct nvme_mi_event" "November 2025" "API Manual" LINUX
2 .SH NAME
3 struct nvme_mi_event \- AE event information structure
4 .SH SYNOPSIS
5 struct nvme_mi_event {
6 .br
7 .BI " uint8_t aeoi;"
8 .br
9 .BI " uint8_t aessi;"
10 .br
11 .BI " uint32_t aeocidi;"
12 .br
13 .BI " void *spec_info;"
14 .br
15 .BI " size_t spec_info_len;"
16 .br
17 .BI " void *vend_spec_info;"
18 .br
19 .BI " size_t vend_spec_info_len;"
20 .br
21 .BI "
22 };
23 .br
24
25 .SH Members
26 .IP "aeoi" 12
27 Event identifier
28 .IP "aessi" 12
29 Event occurrence scope info
30 .IP "aeocidi" 12
31 Event occurrence scope ID info
32 .IP "spec_info" 12
33 Specific info buffer
34 .IP "spec_info_len" 12
35 Length of specific info buffer
36 .IP "vend_spec_info" 12
37 Vendor specific info buffer
38 .IP "vend_spec_info_len" 12
39 Length of vendor specific info buffer
40 .SH "Description"
41 Application callbacks for nvme_mi_aem_process will be able to call
42 nvme_mi_aem_get_next_event which will return a pointer to such an identifier
43 for the next event the application should parse