Searched refs:diagnose (Results 1 – 25 of 26) sorted by relevance
12
| /Linux-v5.4/tools/perf/arch/s390/util/ |
| D | auxtrace.c | 92 int diagnose = 0; in auxtrace_record__init() local
100 diagnose = 1; in auxtrace_record__init()
105 if (!diagnose) in auxtrace_record__init()
|
| /Linux-v5.4/scripts/ |
| D | check_extable.sh | 106 function diagnose() function
141 diagnose
|
| /Linux-v5.4/Documentation/networking/device_drivers/mellanox/ |
| D | mlx5.rst | 172 TX reporter also support on demand diagnose callback, on which it provides
179 $ devlink health diagnose pci/0000:82:00.0 reporter tx
201 RX reporter also supports on demand diagnose callback, on which it
206 $ devlink health diagnose pci/0000:82:00.0 reporter rx
217 The fw reporter implements diagnose and dump callbacks.
220 The fw reporter diagnose command can be triggered any time by the user to check
227 $ devlink health diagnose pci/0000:82:00.0 reporter fw
|
| /Linux-v5.4/Documentation/virt/kvm/ |
| D | hypercalls.txt | 17 S390 uses diagnose instruction as hypercall (0x500) along with hypercall
20 For further information on the S390 diagnose call as supported by KVM,
|
| D | s390-diag.txt | 83 This diagnose function code has no subfunctions and uses no parameters.
|
| /Linux-v5.4/kernel/irq/ |
| D | Kconfig | 134 developers and debugging of hard to diagnose interrupt problems.
|
| /Linux-v5.4/Documentation/networking/ |
| D | devlink-health.txt | 67 |(diagnose,
|
| D | l2tp.txt | 197 implemented to provide extra debug information to help diagnose
|
| /Linux-v5.4/drivers/net/ethernet/mellanox/mlx5/core/en/ |
| D | reporter_tx.c | 279 .diagnose = mlx5e_tx_reporter_diagnose,
|
| D | reporter_rx.c | 375 .diagnose = mlx5e_rx_reporter_diagnose,
|
| /Linux-v5.4/Documentation/admin-guide/wimax/ |
| D | wimax.rst | 51 be used to diagnose issues. By default, said messages are disabled.
|
| /Linux-v5.4/arch/parisc/kernel/ |
| D | perf_asm.S | 118 ; shifting is done, from or to, remote diagnose registers.
1368 ; shifting is done, from or to, the remote diagnose registers.
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | security-bugs.rst | 23 will be to diagnose and fix. Please review the procedure outlined in
|
| /Linux-v5.4/mm/ |
| D | Kconfig.debug | 109 manipulation. This tracking is useful to diagnose functional failure
|
| /Linux-v5.4/drivers/net/ethernet/broadcom/bnxt/ |
| D | bnxt_devlink.c | 60 .diagnose = bnxt_fw_reporter_diagnose,
|
| /Linux-v5.4/drivers/base/ |
| D | Kconfig | 196 spam to the console log, but will make it easier to diagnose
|
| /Linux-v5.4/drivers/net/ethernet/mellanox/mlx5/core/ |
| D | health.c | 542 .diagnose = mlx5_fw_reporter_diagnose,
|
| /Linux-v5.4/include/net/ |
| D | devlink.h | 513 int (*diagnose)(struct devlink_health_reporter *reporter, member
|
| /Linux-v5.4/arch/x86/ |
| D | Kconfig.debug | 242 This might help diagnose strange hangs that rely on NMI to
|
| /Linux-v5.4/Documentation/ia64/ |
| D | mca.rst | 59 monarch is entered. The monarch now tries to diagnose the problem
|
| /Linux-v5.4/Documentation/RCU/ |
| D | stallwarn.txt | 98 To diagnose the cause of the stall, inspect the stack traces.
|
| /Linux-v5.4/Documentation/kernel-hacking/ |
| D | locking.rst | 886 trivial to diagnose: not a
900 This complete lockup is easy to diagnose: on SMP boxes the watchdog
|
| /Linux-v5.4/arch/ |
| D | Kconfig | 850 caught immediately rather than causing difficult-to-diagnose
|
| /Linux-v5.4/net/core/ |
| D | devlink.c | 5111 if (!reporter->ops->diagnose) { in devlink_nl_cmd_health_reporter_diagnose_doit()
5126 err = reporter->ops->diagnose(reporter, fmsg); in devlink_nl_cmd_health_reporter_diagnose_doit()
|
| /Linux-v5.4/init/ |
| D | Kconfig | 1430 very difficult to diagnose system problems, saying N here is
|
12
