brintos

brintos / linux-shallow public Read only

0
0
Text · 14.5 KiB · 3318a14 Raw
324 lines · plain
1What:           /sys/kernel/debug/accel/<parent_device>/addr2Date:           Jan 20193KernelVersion:  5.14Contact:        ogabbay@kernel.org5Description:    Sets the device address to be used for read or write through6                PCI bar, or the device VA of a host mapped memory to be read or7                written directly from the host. The latter option is allowed8                only when the IOMMU is disabled.9                The acceptable value is a string that starts with "0x"10 11What:           /sys/kernel/debug/accel/<parent_device>/clk_gate12Date:           May 202013KernelVersion:  5.814Contact:        ogabbay@kernel.org15Description:    This setting is now deprecated as clock gating is handled solely by the f/w16 17What:           /sys/kernel/debug/accel/<parent_device>/command_buffers18Date:           Jan 201919KernelVersion:  5.120Contact:        ogabbay@kernel.org21Description:    Displays a list with information about the currently allocated22                command buffers23 24What:           /sys/kernel/debug/accel/<parent_device>/command_submission25Date:           Jan 201926KernelVersion:  5.127Contact:        ogabbay@kernel.org28Description:    Displays a list with information about the currently active29                command submissions30 31What:           /sys/kernel/debug/accel/<parent_device>/command_submission_jobs32Date:           Jan 201933KernelVersion:  5.134Contact:        ogabbay@kernel.org35Description:    Displays a list with detailed information about each JOB (CB) of36                each active command submission37 38What:           /sys/kernel/debug/accel/<parent_device>/data3239Date:           Jan 201940KernelVersion:  5.141Contact:        ogabbay@kernel.org42Description:    Allows the root user to read or write directly through the43                device's PCI bar. Writing to this file generates a write44                transaction while reading from the file generates a read45                transaction. This custom interface is needed (instead of using46                the generic Linux user-space PCI mapping) because the DDR bar47                is very small compared to the DDR memory and only the driver can48                move the bar before and after the transaction.49 50                If the IOMMU is disabled, it also allows the root user to read51                or write from the host a device VA of a host mapped memory52 53What:           /sys/kernel/debug/accel/<parent_device>/data6454Date:           Jan 202055KernelVersion:  5.656Contact:        ogabbay@kernel.org57Description:    Allows the root user to read or write 64 bit data directly58                through the device's PCI bar. Writing to this file generates a59                write transaction while reading from the file generates a read60                transaction. This custom interface is needed (instead of using61                the generic Linux user-space PCI mapping) because the DDR bar62                is very small compared to the DDR memory and only the driver can63                move the bar before and after the transaction.64 65                If the IOMMU is disabled, it also allows the root user to read66                or write from the host a device VA of a host mapped memory67 68What:           /sys/kernel/debug/accel/<parent_device>/data_dma69Date:           Apr 202170KernelVersion:  5.1371Contact:        ogabbay@kernel.org72Description:    Allows the root user to read from the device's internal73                memory (DRAM/SRAM) through a DMA engine.74                This property is a binary blob that contains the result of the75                DMA transfer.76                This custom interface is needed (instead of using the generic77                Linux user-space PCI mapping) because the amount of internal78                memory is huge (>32GB) and reading it via the PCI bar will take79                a very long time.80                This interface doesn't support concurrency in the same device.81                In GAUDI and GOYA, this action can cause undefined behavior82                in case it is done while the device is executing user83                workloads.84                Only supported on GAUDI at this stage.85 86What:           /sys/kernel/debug/accel/<parent_device>/device87Date:           Jan 201988KernelVersion:  5.189Contact:        ogabbay@kernel.org90Description:    Enables the root user to set the device to specific state.91                Valid values are "disable", "enable", "suspend", "resume".92                User can read this property to see the valid values93 94What:           /sys/kernel/debug/accel/<parent_device>/device_release_watchdog_timeout95Date:           Oct 202296KernelVersion:  6.297Contact:        ttayar@habana.ai98Description:    The watchdog timeout value in seconds for a device release upon99                certain error cases, after which the device is reset.100 101What:           /sys/kernel/debug/accel/<parent_device>/dma_size102Date:           Apr 2021103KernelVersion:  5.13104Contact:        ogabbay@kernel.org105Description:    Specify the size of the DMA transaction when using DMA to read106                from the device's internal memory. The value can not be larger107                than 128MB. Writing to this value initiates the DMA transfer.108                When the write is finished, the user can read the "data_dma"109                blob110 111What:           /sys/kernel/debug/accel/<parent_device>/dump_razwi_events112Date:           Aug 2022113KernelVersion:  5.20114Contact:        fkassabri@habana.ai115Description:    Dumps all razwi events to dmesg if exist.116                After reading the status register of an existing event117                the routine will clear the status register.118                Usage: cat dump_razwi_events119 120What:           /sys/kernel/debug/accel/<parent_device>/dump_security_violations121Date:           Jan 2021122KernelVersion:  5.12123Contact:        ogabbay@kernel.org124Description:    Dumps all security violations to dmesg. This will also ack125                all security violations meanings those violations will not be126                dumped next time user calls this API127 128What:           /sys/kernel/debug/accel/<parent_device>/engines129Date:           Jul 2019130KernelVersion:  5.3131Contact:        ogabbay@kernel.org132Description:    Displays the status registers values of the device engines and133                their derived idle status134 135What:           /sys/kernel/debug/accel/<parent_device>/i2c_addr136Date:           Jan 2019137KernelVersion:  5.1138Contact:        ogabbay@kernel.org139Description:    Sets I2C device address for I2C transaction that is generated140                by the device's CPU, Not available when device is loaded with secured141                firmware142 143What:           /sys/kernel/debug/accel/<parent_device>/i2c_bus144Date:           Jan 2019145KernelVersion:  5.1146Contact:        ogabbay@kernel.org147Description:    Sets I2C bus address for I2C transaction that is generated by148                the device's CPU, Not available when device is loaded with secured149                firmware150 151What:           /sys/kernel/debug/accel/<parent_device>/i2c_data152Date:           Jan 2019153KernelVersion:  5.1154Contact:        ogabbay@kernel.org155Description:    Triggers an I2C transaction that is generated by the device's156                CPU. Writing to this file generates a write transaction while157                reading from the file generates a read transaction, Not available158                when device is loaded with secured firmware159 160What:           /sys/kernel/debug/accel/<parent_device>/i2c_len161Date:           Dec 2021162KernelVersion:  5.17163Contact:        obitton@habana.ai164Description:    Sets I2C length in bytes for I2C transaction that is generated by165                the device's CPU, Not available when device is loaded with secured166                firmware167 168What:           /sys/kernel/debug/accel/<parent_device>/i2c_reg169Date:           Jan 2019170KernelVersion:  5.1171Contact:        ogabbay@kernel.org172Description:    Sets I2C register id for I2C transaction that is generated by173                the device's CPU, Not available when device is loaded with secured174                firmware175 176What:           /sys/kernel/debug/accel/<parent_device>/led0177Date:           Jan 2019178KernelVersion:  5.1179Contact:        ogabbay@kernel.org180Description:    Sets the state of the first S/W led on the device, Not available181                when device is loaded with secured firmware182 183What:           /sys/kernel/debug/accel/<parent_device>/led1184Date:           Jan 2019185KernelVersion:  5.1186Contact:        ogabbay@kernel.org187Description:    Sets the state of the second S/W led on the device, Not available188                when device is loaded with secured firmware189 190What:           /sys/kernel/debug/accel/<parent_device>/led2191Date:           Jan 2019192KernelVersion:  5.1193Contact:        ogabbay@kernel.org194Description:    Sets the state of the third S/W led on the device, Not available195                when device is loaded with secured firmware196 197What:           /sys/kernel/debug/accel/<parent_device>/memory_scrub198Date:           May 2022199KernelVersion:  5.19200Contact:        dhirschfeld@habana.ai201Description:    Allows the root user to scrub the dram memory. The scrubbing202                value can be set using the debugfs file memory_scrub_val.203 204What:           /sys/kernel/debug/accel/<parent_device>/memory_scrub_val205Date:           May 2022206KernelVersion:  5.19207Contact:        dhirschfeld@habana.ai208Description:    The value to which the dram will be set to when the user209                scrubs the dram using 'memory_scrub' debugfs file and210                the scrubbing value when using module param 'memory_scrub'211 212What:           /sys/kernel/debug/accel/<parent_device>/mmu213Date:           Jan 2019214KernelVersion:  5.1215Contact:        ogabbay@kernel.org216Description:    Displays the hop values and physical address for a given ASID217                and virtual address. The user should write the ASID and VA into218                the file and then read the file to get the result.219                e.g. to display info about VA 0x1000 for ASID 1 you need to do:220                echo "1 0x1000" > /sys/kernel/debug/accel/<parent_device>/mmu221 222What:           /sys/kernel/debug/accel/<parent_device>/mmu_error223Date:           Mar 2021224KernelVersion:  5.12225Contact:        fkassabri@habana.ai226Description:    Check and display page fault or access violation mmu errors for227                all MMUs specified in mmu_cap_mask.228                e.g. to display error info for MMU hw cap bit 9, you need to do:229                echo "0x200" > /sys/kernel/debug/accel/<parent_device>/mmu_error230                cat /sys/kernel/debug/accel/<parent_device>/mmu_error231 232What:           /sys/kernel/debug/accel/<parent_device>/monitor_dump233Date:           Mar 2022234KernelVersion:  5.19235Contact:        osharabi@habana.ai236Description:    Allows the root user to dump monitors status from the device's237                protected config space.238                This property is a binary blob that contains the result of the239                monitors registers dump.240                This custom interface is needed (instead of using the generic241                Linux user-space PCI mapping) because this space is protected242                and cannot be accessed using PCI read.243                This interface doesn't support concurrency in the same device.244                Only supported on GAUDI.245 246What:           /sys/kernel/debug/accel/<parent_device>/monitor_dump_trig247Date:           Mar 2022248KernelVersion:  5.19249Contact:        osharabi@habana.ai250Description:    Triggers dump of monitor data. The value to trigger the operation251                must be 1. Triggering the monitor dump operation initiates dump of252                current registers values of all monitors.253                When the write is finished, the user can read the "monitor_dump"254                blob255 256What:           /sys/kernel/debug/accel/<parent_device>/server_type257Date:           Feb 2024258KernelVersion:  6.11259Contact:        trisin@habana.ai260Description:    Exposes the device's server type, maps to enum hl_server_type.261 262What:           /sys/kernel/debug/accel/<parent_device>/set_power_state263Date:           Jan 2019264KernelVersion:  5.1265Contact:        ogabbay@kernel.org266Description:    Sets the PCI power state. Valid values are "1" for D0 and "2"267                for D3Hot268 269What:           /sys/kernel/debug/accel/<parent_device>/skip_reset_on_timeout270Date:           Jun 2021271KernelVersion:  5.13272Contact:        ynudelman@habana.ai273Description:    Sets the skip reset on timeout option for the device. Value of274                "0" means device will be reset in case some CS has timed out,275                otherwise it will not be reset.276 277What:           /sys/kernel/debug/accel/<parent_device>/state_dump278Date:           Oct 2021279KernelVersion:  5.15280Contact:        ynudelman@habana.ai281Description:    Gets the state dump occurring on a CS timeout or failure.282                State dump is used for debug and is created each time in case of283                a problem in a CS execution, before reset.284                Reading from the node returns the newest state dump available.285                Writing an integer X discards X state dumps, so that the286                next read would return X+1-st newest state dump.287 288What:           /sys/kernel/debug/accel/<parent_device>/stop_on_err289Date:           Mar 2020290KernelVersion:  5.6291Contact:        ogabbay@kernel.org292Description:    Sets the stop-on_error option for the device engines. Value of293                "0" is for disable, otherwise enable.294                Relevant only for GOYA and GAUDI.295 296What:           /sys/kernel/debug/accel/<parent_device>/timeout_locked297Date:           Sep 2021298KernelVersion:  5.16299Contact:        obitton@habana.ai300Description:    Sets the command submission timeout value in seconds.301 302What:           /sys/kernel/debug/accel/<parent_device>/userptr303Date:           Jan 2019304KernelVersion:  5.1305Contact:        ogabbay@kernel.org306Description:    Displays a list with information about the current user307                pointers (user virtual addresses) that are pinned and mapped308                to DMA addresses309 310What:           /sys/kernel/debug/accel/<parent_device>/userptr_lookup311Date:           Oct 2021312KernelVersion:  5.15313Contact:        ogabbay@kernel.org314Description:    Allows to search for specific user pointers (user virtual315                addresses) that are pinned and mapped to DMA addresses, and see316                their resolution to the specific dma address.317 318What:           /sys/kernel/debug/accel/<parent_device>/vm319Date:           Jan 2019320KernelVersion:  5.1321Contact:        ogabbay@kernel.org322Description:    Displays a list with information about all the active virtual323                address mappings per ASID and all user mappings of HW blocks324