Figure 31: Requester Request Descriptor Format for Memory, I/O, and Atomic Op
Requests
0
1
2
3
4
5
6
7
+0
0
1
2
3
4
5
6
7
+1
0
1
2
3
4
5
6
7
+2
0
1
2
3
4
5
6
7
+3
DW + 0
Address [63:2]
Address Type (AT)
0
1
2
3
4
5
6
7
+4
0
1
2
3
4
5
6
7
+5
0
1
2
3
4
5
6
7
+6
0
1
2
3
4
5
6
7
+7
DW + 1
Dword Count
0
1
2
3
4
5
6
7
+8
0
1
2
3
4
5
6
7
+9
0
1
2
3
4
5
6
7
+10
0
1
2
3
4
5
6
7
+11
DW + 2
Tag
TC
0
1
2
3
4
5
6
7
+12
0
1
2
3
4
5
6
7
+13
0
1
2
3
4
5
6
7
+14
0
1
2
3
4
5
6
7
+15
DW + 3
Attr
Req Type
96
64
32
Poisoned Request
Bus
Completer ID
Requester ID Enable
Force ECRC
Bus
Device/Function
Requester ID
Device/Function
127
63
0
X12212
0
1
2
3
4
5
6
7
+0
0
1
2
3
4
5
6
7
+1
0
1
2
3
4
5
6
7
+2
0
1
2
3
4
5
6
7
+3
DW + 0
Address [63:2]
Address Type (AT)
0
1
2
3
4
5
6
7
+4
0
1
2
3
4
5
6
7
+5
0
1
2
3
4
5
6
7
+6
0
1
2
3
4
5
6
7
+7
DW + 1
Dword Count
0
1
2
3
4
5
6
7
+8
0
1
2
3
4
5
6
7
+9
0
1
2
3
4
5
6
7
+10
0
1
2
3
4
5
6
7
+11
DW + 2
Tag
TC
0
1
2
3
4
5
6
7
+12
0
1
2
3
4
5
6
7
+13
0
1
2
3
4
5
6
7
+14
0
1
2
3
4
5
6
7
+15
DW + 3
Attr
Req Type
96
64
32
Poisoned Request
Bus
Completer ID
Requester ID Enable / T8
T9
Bus
Device/Function
Requester ID
Device/Function
127
63
0
X25573-071821
The format of the following figure is used for Vendor-Defined Messages (Type 0 or Type 1) only.
Chapter 4: Designing with the Core
PG346 (v3.3) November 16, 2022
CPM Mode for PCI Express
157