Home
last modified time | relevance | path

Searched refs:diagnose (Results 1 – 25 of 29) sorted by relevance

12

/kernel/linux/linux-5.10/tools/perf/arch/s390/util/
Dauxtrace.c92 int diagnose = 0; in auxtrace_record__init() local
100 diagnose = 1; in auxtrace_record__init()
105 if (!diagnose) in auxtrace_record__init()
/kernel/linux/linux-5.10/scripts/
Dcheck_extable.sh106 function diagnose() function
141 diagnose
/kernel/linux/linux-5.10/Documentation/networking/device_drivers/ethernet/mellanox/
Dmlx5.rst193 TX reporter also support on demand diagnose callback, on which it provides
200 $ devlink health diagnose pci/0000:82:00.0 reporter tx
222 RX reporter also supports on demand diagnose callback, on which it
227 $ devlink health diagnose pci/0000:82:00.0 reporter rx
238 The fw reporter implements diagnose and dump callbacks.
241 The fw reporter diagnose command can be triggered any time by the user to check
248 $ devlink health diagnose pci/0000:82:00.0 reporter fw
/kernel/linux/linux-5.10/tools/testing/selftests/drivers/net/netdevsim/
Ddevlink.sh382 devlink health diagnose $DL_HANDLE reporter empty >/dev/null
467 local diagnose=$(devlink health diagnose $DL_HANDLE reporter dummy -j -p)
470 local rcvrd_break_msg=$(echo $diagnose | jq -r ".recovered_break_message")
/kernel/linux/linux-5.10/drivers/net/netdevsim/
Dhealth.c31 .diagnose = nsim_dev_empty_reporter_diagnose,
226 .diagnose = nsim_dev_dummy_reporter_diagnose,
/kernel/linux/linux-5.10/Documentation/virt/kvm/
Dhypercalls.rst21 S390 uses diagnose instruction as hypercall (0x500) along with hypercall
24 For further information on the S390 diagnose call as supported by KVM,
Ds390-diag.rst86 This diagnose function code has no subfunctions and uses no parameters.
Ds390-pv-boot.rst34 This diagnose instruction is the basic mechanism to handle IPL and
/kernel/linux/linux-5.10/kernel/irq/
DKconfig138 developers and debugging of hard to diagnose interrupt problems.
/kernel/linux/linux-5.10/Documentation/networking/devlink/
Ddevlink-health.rst95 |(diagnose,
/kernel/linux/linux-5.10/Documentation/admin-guide/wimax/
Dwimax.rst51 be used to diagnose issues. By default, said messages are disabled.
/kernel/linux/linux-5.10/arch/parisc/kernel/
Dperf_asm.S118 ; shifting is done, from or to, remote diagnose registers.
1368 ; shifting is done, from or to, the remote diagnose registers.
/kernel/linux/linux-5.10/Documentation/admin-guide/
Dsecurity-bugs.rst23 will be to diagnose and fix. Please review the procedure outlined in
/kernel/linux/linux-5.10/drivers/net/ethernet/mellanox/mlx5/core/en/
Dreporter_tx.c442 .diagnose = mlx5e_tx_reporter_diagnose,
Dreporter_rx.c606 .diagnose = mlx5e_rx_reporter_diagnose,
/kernel/linux/linux-5.10/mm/
DKconfig.debug109 manipulation. This tracking is useful to diagnose functional failure
/kernel/linux/linux-5.10/drivers/base/
DKconfig201 spam to the console log, but will make it easier to diagnose
/kernel/linux/linux-5.10/drivers/net/ethernet/mellanox/mlx5/core/
Dhealth.c561 .diagnose = mlx5_fw_reporter_diagnose,
/kernel/linux/linux-5.10/drivers/net/ethernet/broadcom/bnxt/
Dbnxt_devlink.c86 .diagnose = bnxt_fw_reporter_diagnose,
/kernel/linux/linux-5.10/arch/x86/
DKconfig.debug193 This might help diagnose strange hangs that rely on NMI to
/kernel/linux/linux-5.10/Documentation/ia64/
Dmca.rst59 monarch is entered. The monarch now tries to diagnose the problem
/kernel/linux/linux-5.10/include/net/
Ddevlink.h654 int (*diagnose)(struct devlink_health_reporter *reporter, member
/kernel/linux/linux-5.10/Documentation/RCU/
Dstallwarn.rst110 To diagnose the cause of the stall, inspect the stack traces.
/kernel/linux/linux-5.10/Documentation/kernel-hacking/
Dlocking.rst886 trivial to diagnose: not a
900 This complete lockup is easy to diagnose: on SMP boxes the watchdog
/kernel/linux/linux-5.10/Documentation/networking/
Dl2tp.rst473 implemented to provide extra debug information to help diagnose

12