Mercurial > hg > CbC > CbC_llvm

comparison llvm/docs/AMDGPU/gfx7_msg.rst @ 236:c4bab56944e8 llvm-original

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
LLVM 16
author kono
date Wed, 09 Nov 2022 17:45:10 +0900
parents 1d019706d866
children 1f2b6ac9f198
comparison
equal deleted inserted replaced
232:70dce7da266c 236:c4bab56944e8
3 * * 3 * *
4 * Automatically generated file, do not edit! * 4 * Automatically generated file, do not edit! *
5 * * 5 * *
6 ************************************************** 6 **************************************************
7 7
8 .. _amdgpu_synid7_msg: 8 .. _amdgpu_synid_gfx7_msg:
9 9
10 msg 10 msg
11 =========================== 11 ===
12 12
13 A 16-bit message code. The bits of this operand have the following meaning: 13 A 16-bit message code. The bits of this operand have the following meaning:
14 14
15 ============ =============================== =============== 15 ============ =============================== ===============
16 Bits Description Value Range 16 Bits Description Value Range
45 Numeric values may be specified as positive :ref:`integer numbers<amdgpu_synid_integer_number>` 45 Numeric values may be specified as positive :ref:`integer numbers<amdgpu_synid_integer_number>`
46 or :ref:`absolute expressions<amdgpu_synid_absolute_expression>`. 46 or :ref:`absolute expressions<amdgpu_synid_absolute_expression>`.
47 47
48 Each message type supports specific operations: 48 Each message type supports specific operations:
49 49
50 ================= ========== ============================== ============ ========== 50 ====================== ========== ============================== ============ ==========
51 Message name Message Id Supported Operations Operation Id Stream Id 51 Message name Message Id Supported Operations Operation Id Stream Id
52 ================= ========== ============================== ============ ========== 52 ====================== ========== ============================== ============ ==========
53 MSG_INTERRUPT 1 \- \- \- 53 MSG_INTERRUPT 1 \- \- \-
54 MSG_GS 2 GS_OP_CUT 1 Optional 54 MSG_GS 2 GS_OP_CUT 1 Optional
55 \ GS_OP_EMIT 2 Optional 55 \ GS_OP_EMIT 2 Optional
56 \ GS_OP_EMIT_CUT 3 Optional 56 \ GS_OP_EMIT_CUT 3 Optional
57 MSG_GS_DONE 3 GS_OP_NOP 0 \- 57 MSG_GS_DONE 3 GS_OP_NOP 0 \-
58 \ GS_OP_CUT 1 Optional 58 \ GS_OP_CUT 1 Optional
59 \ GS_OP_EMIT 2 Optional 59 \ GS_OP_EMIT 2 Optional
60 \ GS_OP_EMIT_CUT 3 Optional 60 \ GS_OP_EMIT_CUT 3 Optional
61 MSG_SYSMSG 15 SYSMSG_OP_ECC_ERR_INTERRUPT 1 \- 61 MSG_SYSMSG 15 SYSMSG_OP_ECC_ERR_INTERRUPT 1 \-
62 \ SYSMSG_OP_REG_RD 2 \- 62 \ SYSMSG_OP_REG_RD 2 \-
63 \ SYSMSG_OP_HOST_TRAP_ACK 3 \- 63 \ SYSMSG_OP_HOST_TRAP_ACK 3 \-
64 \ SYSMSG_OP_TTRACE_PC 4 \- 64 \ SYSMSG_OP_TTRACE_PC 4 \-
65 ================= ========== ============================== ============ ========== 65 ====================== ========== ============================== ============ ==========
66 66
67 *Sendmsg* arguments are validated depending on how *type* value is specified: 67 *Sendmsg* arguments are validated depending on how *type* value is specified:
68 68
69 * If message *type* is specified by name, arguments values must satisfy limitations detailed in the table above. 69 * If message *type* is specified by name, arguments values must satisfy limitations detailed in the table above.
70 * If message *type* is specified as a number, each argument must not exceed corresponding value range (see the first table). 70 * If message *type* is specified as a number, each argument must not exceed corresponding value range (see the first table).
89 msg = 2 89 msg = 2
90 op = 3 90 op = 3
91 stream = 1 91 stream = 1
92 s_sendmsg sendmsg(msg, op, stream) 92 s_sendmsg sendmsg(msg, op, stream)
93 s_sendmsg sendmsg(2, GS_OP_CUT) 93 s_sendmsg sendmsg(2, GS_OP_CUT)
94