Home
last modified time | relevance | path

Searched refs:recovery (Results 1 – 25 of 263) sorted by relevance

1234567891011

/Linux-v6.6/drivers/target/iscsi/
Discsi_target_datain_values.c90 if (dr->recovery && dr->generate_recovery_values) { in iscsit_set_datain_values_yes_and_yes()
98 next_burst_len = (!dr->recovery) ? in iscsit_set_datain_values_yes_and_yes()
100 read_data_done = (!dr->recovery) ? in iscsit_set_datain_values_yes_and_yes()
136 datain->data_sn = (!dr->recovery) ? cmd->data_sn++ : dr->data_sn++; in iscsit_set_datain_values_yes_and_yes()
139 if (!dr->recovery) { in iscsit_set_datain_values_yes_and_yes()
147 if (!dr->recovery) { in iscsit_set_datain_values_yes_and_yes()
157 (dr->recovery == DATAIN_WITHIN_COMMAND_RECOVERY) ? in iscsit_set_datain_values_yes_and_yes()
164 (dr->recovery == DATAIN_WITHIN_COMMAND_RECOVERY) ? in iscsit_set_datain_values_yes_and_yes()
189 if (dr->recovery && dr->generate_recovery_values) { in iscsit_set_datain_values_no_and_yes()
197 read_data_done = (!dr->recovery) ? in iscsit_set_datain_values_no_and_yes()
[all …]
/Linux-v6.6/include/linux/qed/
Dqede_rdma.h53 int qede_rdma_dev_add(struct qede_dev *dev, bool recovery);
56 void qede_rdma_dev_remove(struct qede_dev *dev, bool recovery);
62 bool recovery) in qede_rdma_dev_add() argument
70 bool recovery) {} in qede_rdma_dev_remove() argument
/Linux-v6.6/drivers/md/
Dmd.c477 set_bit(MD_RECOVERY_NEEDED, &mddev->recovery); in mddev_resume()
1920 &mddev->recovery)) in super_1_validate()
2634 test_bit(MD_RECOVERY_RUNNING, &mddev->recovery) && in md_update_sb()
2635 test_bit(MD_RECOVERY_RECOVER, &mddev->recovery) && in md_update_sb()
2636 !test_bit(MD_RECOVERY_RESHAPE, &mddev->recovery) && in md_update_sb()
2770 if (test_bit(MD_RECOVERY_RUNNING, &mddev->recovery)) in md_update_sb()
2812 set_bit(MD_RECOVERY_RECOVER, &mddev->recovery); in add_bound_rdev()
2813 set_bit(MD_RECOVERY_NEEDED, &mddev->recovery); in add_bound_rdev()
2962 set_bit(MD_RECOVERY_NEEDED, &rdev->mddev->recovery); in state_store()
3000 set_bit(MD_RECOVERY_NEEDED, &rdev->mddev->recovery); in state_store()
[all …]
Ddm-raid.c3239 set_bit(MD_RECOVERY_FROZEN, &rs->md.recovery); in raid_ctr()
3359 static enum sync_state decipher_sync_action(struct mddev *mddev, unsigned long recovery) in decipher_sync_action() argument
3361 if (test_bit(MD_RECOVERY_FROZEN, &recovery)) in decipher_sync_action()
3365 if (!test_bit(MD_RECOVERY_DONE, &recovery) && in decipher_sync_action()
3366 (test_bit(MD_RECOVERY_RUNNING, &recovery) || in decipher_sync_action()
3367 (!mddev->ro && test_bit(MD_RECOVERY_NEEDED, &recovery)))) { in decipher_sync_action()
3368 if (test_bit(MD_RECOVERY_RESHAPE, &recovery)) in decipher_sync_action()
3371 if (test_bit(MD_RECOVERY_SYNC, &recovery)) { in decipher_sync_action()
3372 if (!test_bit(MD_RECOVERY_REQUESTED, &recovery)) in decipher_sync_action()
3374 if (test_bit(MD_RECOVERY_CHECK, &recovery)) in decipher_sync_action()
[all …]
Draid10.c144 if (test_bit(MD_RECOVERY_SYNC, &conf->mddev->recovery) || in r10buf_pool_alloc()
145 test_bit(MD_RECOVERY_RESHAPE, &conf->mddev->recovery)) in r10buf_pool_alloc()
191 &conf->mddev->recovery)) { in r10buf_pool_alloc()
488 &rdev->mddev->recovery); in raid10_end_write_request()
1101 if (!test_bit(MD_RECOVERY_RESHAPE, &rdev->mddev->recovery) || in choose_data_offset()
1154 while (test_bit(MD_RECOVERY_RESHAPE, &mddev->recovery) && in regular_request_wait()
1439 if (test_bit(MD_RECOVERY_RESHAPE, &mddev->recovery) && in raid10_write_request()
1671 if (test_bit(MD_RECOVERY_RESHAPE, &mddev->recovery)) in raid10_handle_discard()
1684 if (test_bit(MD_RECOVERY_RESHAPE, &mddev->recovery)) in raid10_handle_discard()
2050 set_bit(MD_RECOVERY_INTR, &mddev->recovery); in raid10_error()
[all …]
/Linux-v6.6/Documentation/networking/devlink/
Ddevlink-health.rst23 attributes of the health reporting and recovery procedures.
50 * Auto recovery attempt is being done. Depends on:
52 - Auto-recovery configuration
80 * Configure reporter's generic parameters (like: disable/enable auto recovery)
81 * Invoke recovery procedure
95 - Triggers reporter's recovery procedure.
98 event in terms of recovery flow should follow closely that of a real
Dsfc.rst47 * - ``coproc.recovery``
49 - SmartNIC application co-processor (APU) recovery operating system version.
/Linux-v6.6/Documentation/ABI/testing/
Dsysfs-class-remoteproc83 copy the dump. Also recovery process will not proceed until
86 What: /sys/class/remoteproc/.../recovery
89 Description: Remote processor recovery mechanism
91 Reports the recovery mechanism of the remote processor,
99 processor crashes while recovery is disabled, it will
100 be automatically recovered too as soon as recovery is enabled.
/Linux-v6.6/drivers/net/wireless/ath/ath6kl/
Drecovery.c100 struct ath6kl_fw_recovery *recovery = &ar->fw_recovery; in ath6kl_recovery_init() local
103 INIT_WORK(&recovery->recovery_work, ath6kl_recovery_work); in ath6kl_recovery_init()
104 recovery->seq_num = 0; in ath6kl_recovery_init()
105 recovery->hb_misscnt = 0; in ath6kl_recovery_init()
/Linux-v6.6/tools/testing/selftests/drivers/net/bonding/
DMakefile9 mode-1-recovery-updelay.sh \
10 mode-2-recovery-updelay.sh \
/Linux-v6.6/Documentation/PCI/
Dpcieaer-howto.rst43 - Performs error recovery actions.
98 To enable error recovery, a software driver must provide callbacks.
152 PCI error-recovery callbacks
157 when performing error recovery actions.
162 pci-error-recovery.rst except PCIe-specific parts (e.g.
163 reset_link). Please refer to pci-error-recovery.rst for detailed
174 require any recovery actions. The AER driver clears the device's
200 function. If reset_link is not NULL, recovery function will use it
210 error recovery handler (pci_driver->err_handler is equal to NULL)?
222 Fatal error recovery will fail if the errors are reported by the
[all …]
Dpci-error-recovery.rst26 of a bus disconnection, and then performing error recovery.
29 Reporting and recovery is performed in several steps. First, when
38 Next, recovery is performed in several stages. Most of the complexity
57 through a large number of contortions to complete recovery. Almost all
61 device drivers already handle very similar recovery procedures;
72 The error recovery API support is exposed to the driver in the form of
75 and the actual recovery steps taken are platform dependent. The
111 is assumed that the driver is not doing any direct recovery and requires
160 particular, if the platform doesn't isolate slots), and recovery
164 then recovery proceeds to STEP 4 (Slot Reset).
[all …]
/Linux-v6.6/Documentation/devicetree/bindings/sound/
Dst,sta32x.txt44 If present, thermal warning recovery is enabled.
46 - st,fault-detect-recovery:
47 If present, fault detect recovery is enabled.
52 - st,fault-detect-recovery:
53 If present, then fault recovery will be enabled.
Dcs35l32.txt39 - cirrus,battery-recovery : Low battery nominal recovery threshold, rising VP.
/Linux-v6.6/drivers/ata/
Dpata_cs5520.c40 int recovery; member
70 (cs5520_pio_clocks[pio].recovery << 4) | in cs5520_set_timings()
75 (cs5520_pio_clocks[pio].recovery << 4) | in cs5520_set_timings()
79 (cs5520_pio_clocks[pio].recovery << 4) | in cs5520_set_timings()
/Linux-v6.6/arch/arm64/boot/dts/marvell/
Darmada-3720-uDPU.dts23 i2c1_recovery_pins: i2c1-recovery-pins {
31 pinctrl-names = "default", "recovery";
Darmada-3720-uDPU.dtsi112 i2c2_recovery_pins: i2c2-recovery-pins {
120 pinctrl-names = "default", "recovery";
/Linux-v6.6/Documentation/i2c/
Dgpio-fault-injection.rst36 master under test should detect this condition and trigger a bus recovery (see
38 core (see 'struct bus_recovery_info'). However, the bus recovery will not
47 device. Bus recovery should be able to fix these situations. But please note:
51 and will init a bus recovery on its own. If you want to implement bus recovery
64 recovery. This time, however, it should succeed and the device should release
82 This is why bus recovery (up to 9 clock pulses) must either check SDA or send
/Linux-v6.6/drivers/net/ethernet/qlogic/qede/
Dqede_rdma.c86 int qede_rdma_dev_add(struct qede_dev *edev, bool recovery) in qede_rdma_dev_add() argument
94 if (recovery) in qede_rdma_dev_add()
116 void qede_rdma_dev_remove(struct qede_dev *edev, bool recovery) in qede_rdma_dev_remove() argument
122 if (!recovery) { in qede_rdma_dev_remove()
/Linux-v6.6/drivers/i2c/busses/
Di2c-uniphier.c161 bool recovery = false; in uniphier_i2c_master_xfer_one() local
175 recovery = true; in uniphier_i2c_master_xfer_one()
183 recovery = true; in uniphier_i2c_master_xfer_one()
188 if (recovery) in uniphier_i2c_master_xfer_one()
/Linux-v6.6/Documentation/admin-guide/
Dfilesystem-monitoring.rst13 sysadmin, start recovery) when a file system problem is detected.
20 early file system problem detection and reporting recovery tools.
76 specific application can use that information to attempt a recovery
/Linux-v6.6/Documentation/ABI/stable/
Dsysfs-devices-node198 ignored by memory error recovery attempt, usually because
200 gives up the recovery.
207 failed by memory error recovery attempt. This usually means
208 a key recovery operation failed.
215 delayed by memory error recovery attempt. Delayed poisoned
223 recovered by memory error recovery attempt.
/Linux-v6.6/Documentation/devicetree/bindings/bus/
Dqcom,ebi2.txt77 - qcom,xmem-recovery-cycles: recovery cycles is the time the memory continues to
81 value is actually 1, so a value of 0 will still yield 1 recovery cycle.
99 - qcom,xmem-adv-to-oe-recovery-cycles: the number of cycles elapsed before an OE
131 qcom,xmem-recovery-cycles = <0>;
/Linux-v6.6/arch/arm/boot/dts/nxp/imx/
Dimx6q-gk802.dts33 recovery-button {
34 label = "recovery";
/Linux-v6.6/fs/jbd2/
DMakefile8 jbd2-objs := transaction.o commit.o recovery.o checkpoint.o revoke.o journal.o

1234567891011