Debian Codegraph @

doc/man/nvme_mi_aem_msg.2

raw
1 .TH "libnvme" 9 "struct nvme_mi_aem_msg" "November 2025" "API Manual" LINUX
2 .SH NAME
3 struct nvme_mi_aem_msg \- AEM Message definition.
4 .SH SYNOPSIS
5 struct nvme_mi_aem_msg {
6 .br
7 .BI " struct nvme_mi_msg_hdr hdr;"
8 .br
9 .BI " struct nvme_mi_aem_occ_list_hdr occ_list_hdr;"
10 .br
11 .BI "
12 };
13 .br
14
15 .SH Members
16 .IP "hdr" 12
17 the general response message header
18 .IP "occ_list_hdr" 12
19 ae occurrence list header.
20 .SH "Description"
21 Every ae message will start with one of these. The occ_list_hder wil define
22 information about how many ae occ data entries are included. Each entry is
23 defined by the nvme_mi_aem_occ_data structure which will follow the
24 occ_list_hdr. Each nvme_mi_aem_occ_data structure has a fixed length header
25 but a variable length payload ude to occurrence specific and vendor specific
26 info. For this reason, do not index the nvme_mi_ae_occ data structures by
27 array or fixed offset.