187 lines · plain
1What: /sys/kernel/debug/hisi_hpre/<bdf>/cluster[0-3]/regs2Date: Sep 20193Contact: linux-crypto@vger.kernel.org4Description: Dump debug registers from the HPRE cluster.5 Only available for PF.6 7What: /sys/kernel/debug/hisi_hpre/<bdf>/cluster[0-3]/cluster_ctrl8Date: Sep 20199Contact: linux-crypto@vger.kernel.org10Description: Write the HPRE core selection in the cluster into this file,11 and then we can read the debug information of the core.12 Only available for PF.13 14What: /sys/kernel/debug/hisi_hpre/<bdf>/rdclr_en15Date: Sep 201916Contact: linux-crypto@vger.kernel.org17Description: HPRE cores debug registers read clear control. 1 means enable18 register read clear, otherwise 0. Writing to this file has no19 functional effect, only enable or disable counters clear after20 reading of these registers.21 Only available for PF.22 23What: /sys/kernel/debug/hisi_hpre/<bdf>/current_qm24Date: Sep 201925Contact: linux-crypto@vger.kernel.org26Description: One HPRE controller has one PF and multiple VFs, each function27 has a QM. Select the QM which below qm refers to.28 Only available for PF.29 30What: /sys/kernel/debug/hisi_hpre/<bdf>/alg_qos31Date: Jun 202132Contact: linux-crypto@vger.kernel.org33Description: The <bdf> is related the function for PF and VF.34 HPRE driver supports to configure each function's QoS, the driver35 supports to write <bdf> value to alg_qos in the host. Such as36 "echo <bdf> value > alg_qos". The qos value is 1~1000, means37 1/1000~1000/1000 of total QoS. The driver reading alg_qos to38 get related QoS in the host and VM, Such as "cat alg_qos".39 40What: /sys/kernel/debug/hisi_hpre/<bdf>/regs41Date: Sep 201942Contact: linux-crypto@vger.kernel.org43Description: Dump debug registers from the HPRE.44 Only available for PF.45 46What: /sys/kernel/debug/hisi_hpre/<bdf>/qm/regs47Date: Sep 201948Contact: linux-crypto@vger.kernel.org49Description: Dump debug registers from the QM.50 Available for PF and VF in host. VF in guest currently only51 has one debug register.52 53What: /sys/kernel/debug/hisi_hpre/<bdf>/qm/current_q54Date: Sep 201955Contact: linux-crypto@vger.kernel.org56Description: One QM may contain multiple queues. Select specific queue to57 show its debug registers in above regs.58 Only available for PF.59 60What: /sys/kernel/debug/hisi_hpre/<bdf>/qm/clear_enable61Date: Sep 201962Contact: linux-crypto@vger.kernel.org63Description: QM debug registers(regs) read clear control. 1 means enable64 register read clear, otherwise 0.65 Writing to this file has no functional effect, only enable or66 disable counters clear after reading of these registers.67 Only available for PF.68 69What: /sys/kernel/debug/hisi_hpre/<bdf>/qm/err_irq70Date: Apr 202071Contact: linux-crypto@vger.kernel.org72Description: Dump the number of invalid interrupts for73 QM task completion.74 Available for both PF and VF, and take no other effect on HPRE.75 76What: /sys/kernel/debug/hisi_hpre/<bdf>/qm/aeq_irq77Date: Apr 202078Contact: linux-crypto@vger.kernel.org79Description: Dump the number of QM async event queue interrupts.80 Available for both PF and VF, and take no other effect on HPRE.81 82What: /sys/kernel/debug/hisi_hpre/<bdf>/qm/abnormal_irq83Date: Apr 202084Contact: linux-crypto@vger.kernel.org85Description: Dump the number of interrupts for QM abnormal event.86 Available for both PF and VF, and take no other effect on HPRE.87 88What: /sys/kernel/debug/hisi_hpre/<bdf>/qm/create_qp_err89Date: Apr 202090Contact: linux-crypto@vger.kernel.org91Description: Dump the number of queue allocation errors.92 Available for both PF and VF, and take no other effect on HPRE.93 94What: /sys/kernel/debug/hisi_hpre/<bdf>/qm/mb_err95Date: Apr 202096Contact: linux-crypto@vger.kernel.org97Description: Dump the number of failed QM mailbox commands.98 Available for both PF and VF, and take no other effect on HPRE.99 100What: /sys/kernel/debug/hisi_hpre/<bdf>/qm/status101Date: Apr 2020102Contact: linux-crypto@vger.kernel.org103Description: Dump the status of the QM.104 Two states: work, stop.105 Available for both PF and VF, and take no other effect on HPRE.106 107What: /sys/kernel/debug/hisi_hpre/<bdf>/qm/diff_regs108Date: Mar 2022109Contact: linux-crypto@vger.kernel.org110Description: QM debug registers(regs) read hardware register value. This111 node is used to show the change of the qm register values. This112 node can be help users to check the change of register values.113 114What: /sys/kernel/debug/hisi_hpre/<bdf>/qm/qm_state115Date: Jan 2024116Contact: linux-crypto@vger.kernel.org117Description: Dump the state of the device.118 0: busy, 1: idle.119 Only available for PF, and take no other effect on HPRE.120 121What: /sys/kernel/debug/hisi_hpre/<bdf>/qm/dev_timeout122Date: Feb 2024123Contact: linux-crypto@vger.kernel.org124Description: Set the wait time when stop queue fails. Available for both PF125 and VF, and take no other effect on HPRE.126 0: not wait(default), others value: wait dev_timeout * 20 microsecond.127 128What: /sys/kernel/debug/hisi_hpre/<bdf>/qm/dev_state129Date: Feb 2024130Contact: linux-crypto@vger.kernel.org131Description: Dump the stop queue status of the QM. The default value is 0,132 if dev_timeout is set, when stop queue fails, the dev_state133 will return non-zero value. Available for both PF and VF,134 and take no other effect on HPRE.135 136What: /sys/kernel/debug/hisi_hpre/<bdf>/hpre_dfx/diff_regs137Date: Mar 2022138Contact: linux-crypto@vger.kernel.org139Description: HPRE debug registers(regs) read hardware register value. This140 node is used to show the change of the register values. This141 node can be help users to check the change of register values.142 143What: /sys/kernel/debug/hisi_hpre/<bdf>/hpre_dfx/send_cnt144Date: Apr 2020145Contact: linux-crypto@vger.kernel.org146Description: Dump the total number of sent requests.147 Available for both PF and VF, and take no other effect on HPRE.148 149What: /sys/kernel/debug/hisi_hpre/<bdf>/hpre_dfx/recv_cnt150Date: Apr 2020151Contact: linux-crypto@vger.kernel.org152Description: Dump the total number of received requests.153 Available for both PF and VF, and take no other effect on HPRE.154 155What: /sys/kernel/debug/hisi_hpre/<bdf>/hpre_dfx/send_busy_cnt156Date: Apr 2020157Contact: linux-crypto@vger.kernel.org158Description: Dump the total number of requests sent159 with returning busy.160 Available for both PF and VF, and take no other effect on HPRE.161 162What: /sys/kernel/debug/hisi_hpre/<bdf>/hpre_dfx/send_fail_cnt163Date: Apr 2020164Contact: linux-crypto@vger.kernel.org165Description: Dump the total number of completed but error requests.166 Available for both PF and VF, and take no other effect on HPRE.167 168What: /sys/kernel/debug/hisi_hpre/<bdf>/hpre_dfx/invalid_req_cnt169Date: Apr 2020170Contact: linux-crypto@vger.kernel.org171Description: Dump the total number of invalid requests being received.172 Available for both PF and VF, and take no other effect on HPRE.173 174What: /sys/kernel/debug/hisi_hpre/<bdf>/hpre_dfx/overtime_thrhld175Date: Apr 2020176Contact: linux-crypto@vger.kernel.org177Description: Set the threshold time for counting the request which is178 processed longer than the threshold.179 0: disable(default), 1: 1 microsecond.180 Available for both PF and VF, and take no other effect on HPRE.181 182What: /sys/kernel/debug/hisi_hpre/<bdf>/hpre_dfx/over_thrhld_cnt183Date: Apr 2020184Contact: linux-crypto@vger.kernel.org185Description: Dump the total number of time out requests.186 Available for both PF and VF, and take no other effect on HPRE.187