| /dpdk/doc/guides/sample_app_ug/ |
| H A D | keep_alive.rst | 9 to detect 'failed' DPDK cores and notify a fault management entity 11 does not result in a fault that is not detectable by a management 27 higher level fault management entity of the core failure in order to 93 fault management entity through a callback function.
|
| H A D | vhost_crypto.rst | 50 in experimental stage and may cause the problem like segmentation fault. If
|
| /dpdk/drivers/net/fm10k/base/ |
| H A D | fm10k_api.c | 277 s32 fm10k_get_fault(struct fm10k_hw *hw, int type, struct fm10k_fault *fault) in fm10k_get_fault() argument 279 return fm10k_call_func(hw, hw->mac.ops.get_fault, (hw, type, fault), in fm10k_get_fault()
|
| H A D | fm10k_api.h | 28 s32 fm10k_get_fault(struct fm10k_hw *hw, int type, struct fm10k_fault *fault);
|
| H A D | fm10k_pf.c | 1610 struct fm10k_fault *fault) in fm10k_get_fault_pf() argument 1632 fault->address = FM10K_READ_REG(hw, type + FM10K_FAULT_ADDR_HI); in fm10k_get_fault_pf() 1633 fault->address <<= 32; in fm10k_get_fault_pf() 1634 fault->address = FM10K_READ_REG(hw, type + FM10K_FAULT_ADDR_LO); in fm10k_get_fault_pf() 1635 fault->specinfo = FM10K_READ_REG(hw, type + FM10K_FAULT_SPECINFO); in fm10k_get_fault_pf() 1642 fault->func = 0; in fm10k_get_fault_pf() 1644 fault->func = 1 + ((func & FM10K_FAULT_FUNC_VF_MASK) >> in fm10k_get_fault_pf() 1648 fault->type = func & FM10K_FAULT_FUNC_TYPE_MASK; in fm10k_get_fault_pf()
|
| /dpdk/drivers/net/fm10k/ |
| H A D | fm10k_ethdev.c | 2456 struct fm10k_fault fault; in fm10k_dev_handle_fault() local 2462 err = fm10k_get_fault(hw, FM10K_PCA_FAULT, &fault); in fm10k_dev_handle_fault() 2465 switch (fault.type) { in fm10k_dev_handle_fault() 2484 estr, fault.func ? "VF" : "PF", fault.func, in fm10k_dev_handle_fault() 2485 fault.address, fault.specinfo); in fm10k_dev_handle_fault() 2493 switch (fault.type) { in fm10k_dev_handle_fault() 2502 estr, fault.func ? "VF" : "PF", fault.func, in fm10k_dev_handle_fault() 2503 fault.address, fault.specinfo); in fm10k_dev_handle_fault() 2511 switch (fault.type) { in fm10k_dev_handle_fault() 2540 estr, fault.func ? "VF" : "PF", fault.func, in fm10k_dev_handle_fault() [all …]
|
| /dpdk/drivers/common/cnxk/hw/ |
| H A D | cpt.h | 108 uint64_t fault : 1; member 133 uint64_t fault : 1; member
|
| /dpdk/drivers/common/cpt/ |
| H A D | cpt_hw_types.h | 530 uint64_t fault : 1; member 552 uint64_t fault : 1;
|
| /dpdk/doc/guides/vdpadevs/ |
| H A D | features_overview.rst | 97 Slave expose page-fault FD for migration process.
|
| /dpdk/doc/guides/prog_guide/ |
| H A D | link_bonding_poll_mode_drv_lib.rst | 22 redundant links, fault tolerance and/or load balancing. 47 This mode provides load balancing and fault tolerance by transmission of 62 thereby providing fault tolerance to slave failure. The single logical 74 transmission policy) and fault tolerance. The default policy (layer2) uses 95 This mode provides fault tolerance by transmission of packets on all slave
|
| H A D | vhost_lib.rst | 69 not pre-fault the guest shared memory, otherwise migration would fail.
|
| /dpdk/doc/guides/rawdevs/ |
| H A D | ifpga.rst | 18 different users. FPGA hot upgrade and fault tolerance can be provided easily.
|
| H A D | ntb.rst | 9 user cases can benefit from this, such as fault tolerance and visual
|
| /dpdk/drivers/crypto/octeontx/ |
| H A D | otx_cryptodev_hw_access.c | 166 vqx_misc_int.s.fault = 1; in otx_cpt_clear_fault_intr()
|
| /dpdk/doc/guides/rel_notes/ |
| H A D | known_issues.rst | 521 dmar: DRHD: handling fault status reg 2 522 dmar: DMAR:[DMA Read] Request device [02:00.0] fault addr a0c58000 523 DMAR:[fault reason 02] Present bit in context entry is clear
|
| H A D | release_2_1.rst | 413 fault. 590 * **fm10k: Fix interrupt fault handling.** 670 hit a segmentation fault as a result of decrementing an unsigned index with
|
| H A D | release_16_04.rst | 14 Use cases for this feature include fault detection, and monitoring 418 * **librte_port: Fixed segmentation fault for ring and ethdev writer nodrop.**
|
| H A D | release_17_02.rst | 240 PCI data resulting in a segmentation fault.
|
| /dpdk/doc/guides/nics/ |
| H A D | mlx5.rst | 121 Calling a function at the wrong address leads to a segmentation fault.
|