@@ -82,6 +82,24 @@ Description: Allows the root user to read or write 64 bit data directly
82
82
If the IOMMU is disabled, it also allows the root user to read
83
83
or write from the host a device VA of a host mapped memory
84
84
85
+ What: /sys/kernel/debug/habanalabs/hl<n>/data_dma
86
+ Date: Apr 2021
87
+ KernelVersion: 5.13
88
+
89
+ Description: Allows the root user to read from the device's internal
90
+ memory (DRAM/SRAM) through a DMA engine.
91
+ This property is a binary blob that contains the result of the
92
+ DMA transfer.
93
+ This custom interface is needed (instead of using the generic
94
+ Linux user-space PCI mapping) because the amount of internal
95
+ memory is huge (>32GB) and reading it via the PCI bar will take
96
+ a very long time.
97
+ This interface doesn't support concurrency in the same device.
98
+ In GAUDI and GOYA, this action can cause undefined behavior
99
+ in case the it is done while the device is executing user
100
+ workloads.
101
+ Only supported on GAUDI at this stage.
102
+
85
103
What: /sys/kernel/debug/habanalabs/hl<n>/device
86
104
Date: Jan 2019
87
105
KernelVersion: 5.1
@@ -90,6 +108,24 @@ Description: Enables the root user to set the device to specific state.
90
108
Valid values are "disable", "enable", "suspend", "resume".
91
109
User can read this property to see the valid values
92
110
111
+ What: /sys/kernel/debug/habanalabs/hl<n>/dma_size
112
+ Date: Apr 2021
113
+ KernelVersion: 5.13
114
+
115
+ Description: Specify the size of the DMA transaction when using DMA to read
116
+ from the device's internal memory. The value can not be larger
117
+ than 128MB. Writing to this value initiates the DMA transfer.
118
+ When the write is finished, the user can read the "data_dma"
119
+ blob
120
+
121
+ What: /sys/kernel/debug/habanalabs/hl<n>/dump_security_violations
122
+ Date: Jan 2021
123
+ KernelVersion: 5.12
124
+
125
+ Description: Dumps all security violations to dmesg. This will also ack
126
+ all security violations meanings those violations will not be
127
+ dumped next time user calls this API
128
+
93
129
What: /sys/kernel/debug/habanalabs/hl<n>/engines
94
130
Date: Jul 2019
95
131
KernelVersion: 5.3
@@ -154,13 +190,30 @@ Description: Displays the hop values and physical address for a given ASID
154
190
e.g. to display info about VA 0x1000 for ASID 1 you need to do:
155
191
echo "1 0x1000" > /sys/kernel/debug/habanalabs/hl0/mmu
156
192
193
+ What: /sys/kernel/debug/habanalabs/hl<n>/mmu_error
194
+ Date: Mar 2021
195
+ KernelVersion: 5.12
196
+
197
+ Description: Check and display page fault or access violation mmu errors for
198
+ all MMUs specified in mmu_cap_mask.
199
+ e.g. to display error info for MMU hw cap bit 9, you need to do:
200
+ echo "0x200" > /sys/kernel/debug/habanalabs/hl0/mmu_error
201
+ cat /sys/kernel/debug/habanalabs/hl0/mmu_error
202
+
157
203
What: /sys/kernel/debug/habanalabs/hl<n>/set_power_state
158
204
Date: Jan 2019
159
205
KernelVersion: 5.1
160
206
161
207
Description: Sets the PCI power state. Valid values are "1" for D0 and "2"
162
208
for D3Hot
163
209
210
+ What: /sys/kernel/debug/habanalabs/hl<n>/stop_on_err
211
+ Date: Mar 2020
212
+ KernelVersion: 5.6
213
+
214
+ Description: Sets the stop-on_error option for the device engines. Value of
215
+ "0" is for disable, otherwise enable.
216
+
164
217
What: /sys/kernel/debug/habanalabs/hl<n>/userptr
165
218
Date: Jan 2019
166
219
KernelVersion: 5.1
@@ -174,19 +227,4 @@ Date: Jan 2019
174
227
KernelVersion: 5.1
175
228
176
229
Description: Displays a list with information about all the active virtual
177
- address mappings per ASID
178
-
179
- What: /sys/kernel/debug/habanalabs/hl<n>/stop_on_err
180
- Date: Mar 2020
181
- KernelVersion: 5.6
182
-
183
- Description: Sets the stop-on_error option for the device engines. Value of
184
- "0" is for disable, otherwise enable.
185
-
186
- What: /sys/kernel/debug/habanalabs/hl<n>/dump_security_violations
187
- Date: Jan 2021
188
- KernelVersion: 5.12
189
-
190
- Description: Dumps all security violations to dmesg. This will also ack
191
- all security violations meanings those violations will not be
192
- dumped next time user calls this API
230
+ address mappings per ASID and all user mappings of HW blocks
0 commit comments