Home
last modified time | relevance | path

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

/linux-4.4.14/drivers/target/iscsi/
Discsi_target_datain_values.c98 if (dr->recovery && dr->generate_recovery_values) { in iscsit_set_datain_values_yes_and_yes()
106 next_burst_len = (!dr->recovery) ? in iscsit_set_datain_values_yes_and_yes()
108 read_data_done = (!dr->recovery) ? in iscsit_set_datain_values_yes_and_yes()
144 datain->data_sn = (!dr->recovery) ? cmd->data_sn++ : dr->data_sn++; in iscsit_set_datain_values_yes_and_yes()
147 if (!dr->recovery) { in iscsit_set_datain_values_yes_and_yes()
155 if (!dr->recovery) { in iscsit_set_datain_values_yes_and_yes()
165 (dr->recovery == DATAIN_WITHIN_COMMAND_RECOVERY) ? in iscsit_set_datain_values_yes_and_yes()
172 (dr->recovery == DATAIN_WITHIN_COMMAND_RECOVERY) ? in iscsit_set_datain_values_yes_and_yes()
197 if (dr->recovery && dr->generate_recovery_values) { in iscsit_set_datain_values_no_and_yes()
205 read_data_done = (!dr->recovery) ? in iscsit_set_datain_values_no_and_yes()
[all …]
Discsi_target.h26 extern int iscsit_build_r2ts_for_cmd(struct iscsi_conn *, struct iscsi_cmd *, bool recovery);
Discsi_target_erl0.c398 int dump = 0, recovery = 0; in iscsit_dataout_pre_datapduinorder_yes() local
417 recovery = 1; in iscsit_dataout_pre_datapduinorder_yes()
427 recovery = 1; in iscsit_dataout_pre_datapduinorder_yes()
451 return (recovery) ? iscsit_recover_dataout_sequence(cmd, in iscsit_dataout_pre_datapduinorder_yes()
Discsi_target_erl1.c456 dr->recovery = DATAIN_WITHIN_COMMAND_RECOVERY; in iscsit_handle_recovery_datain()
617 int i, send_recovery_r2t = 0, recovery = 0; in iscsit_dataout_datapduinorder_no_fbit() local
670 recovery = 1; in iscsit_dataout_datapduinorder_no_fbit()
686 return (!recovery) ? DATAOUT_NORMAL : DATAOUT_WITHIN_COMMAND_RECOVERY; in iscsit_dataout_datapduinorder_no_fbit()
Discsi_target_tmr.c350 dr->recovery = DATAIN_CONNECTION_RECOVERY; in iscsit_task_reassign_complete_read()
Discsi_target_util.c65 int recovery, in iscsit_add_r2t_to_list() argument
77 r2t->recovery_r2t = recovery; in iscsit_add_r2t_to_list()
Discsi_target.c3094 bool recovery) in iscsit_build_r2ts_for_cmd() argument
3106 !recovery) in iscsit_build_r2ts_for_cmd()
3113 if (first_r2t && recovery) { in iscsit_build_r2ts_for_cmd()
/linux-4.4.14/drivers/ide/
Dcs5520.c49 int recovery; member
68 (cs5520_pio_clocks[pio].recovery << 4) | in cs5520_set_pio_mode()
76 (cs5520_pio_clocks[pio].recovery << 4) | in cs5520_set_pio_mode()
80 (cs5520_pio_clocks[pio].recovery << 4) | in cs5520_set_pio_mode()
Dqd65xx.h57 s16 recovery; /* recovery time */ member
Dqd65xx.c167 *recovery_time = p->recovery; in qd_find_disk_type()
DKconfig180 perform below the driver data recovery if needed. This is the most
/linux-4.4.14/drivers/md/
Dmd.c336 set_bit(MD_RECOVERY_NEEDED, &mddev->recovery); in mddev_resume()
2447 if (test_bit(MD_RECOVERY_RUNNING, &mddev->recovery)) in md_update_sb()
2488 set_bit(MD_RECOVERY_RECOVER, &mddev->recovery); in add_bound_rdev()
2489 set_bit(MD_RECOVERY_NEEDED, &mddev->recovery); in add_bound_rdev()
2632 set_bit(MD_RECOVERY_NEEDED, &rdev->mddev->recovery); in state_store()
2662 set_bit(MD_RECOVERY_NEEDED, &rdev->mddev->recovery); in state_store()
2777 set_bit(MD_RECOVERY_NEEDED, &rdev->mddev->recovery); in slot_store()
2788 if (test_bit(MD_RECOVERY_RUNNING, &rdev->mddev->recovery)) in slot_store()
2874 test_bit(MD_RECOVERY_RUNNING,&mddev->recovery)) in new_offset_store()
3464 test_bit(MD_RECOVERY_RUNNING, &mddev->recovery) || in level_store()
[all …]
Ddm-raid.c1340 if (test_bit(MD_RECOVERY_FROZEN, &mddev->recovery)) in decipher_sync_action()
1343 if (test_bit(MD_RECOVERY_RUNNING, &mddev->recovery) || in decipher_sync_action()
1344 (!mddev->ro && test_bit(MD_RECOVERY_NEEDED, &mddev->recovery))) { in decipher_sync_action()
1345 if (test_bit(MD_RECOVERY_RESHAPE, &mddev->recovery)) in decipher_sync_action()
1348 if (test_bit(MD_RECOVERY_SYNC, &mddev->recovery)) { in decipher_sync_action()
1349 if (!test_bit(MD_RECOVERY_REQUESTED, &mddev->recovery)) in decipher_sync_action()
1351 else if (test_bit(MD_RECOVERY_CHECK, &mddev->recovery)) in decipher_sync_action()
1356 if (test_bit(MD_RECOVERY_RECOVER, &mddev->recovery)) in decipher_sync_action()
1377 if (test_bit(MD_RECOVERY_RUNNING, &rs->md.recovery)) in raid_status()
1388 } else if (test_bit(MD_RECOVERY_REQUESTED, &rs->md.recovery)) { in raid_status()
[all …]
Draid10.c151 if (test_bit(MD_RECOVERY_SYNC, &conf->mddev->recovery) || in r10buf_pool_alloc()
152 test_bit(MD_RECOVERY_RESHAPE, &conf->mddev->recovery)) in r10buf_pool_alloc()
181 &conf->mddev->recovery)) { in r10buf_pool_alloc()
473 &rdev->mddev->recovery); in raid10_end_write_request()
1004 if (!test_bit(MD_RECOVERY_RESHAPE, &rdev->mddev->recovery) || in choose_data_offset()
1083 while (test_bit(MD_RECOVERY_RESHAPE, &mddev->recovery) && in __make_request()
1096 if (test_bit(MD_RECOVERY_RESHAPE, &mddev->recovery) && in __make_request()
1591 set_bit(MD_RECOVERY_INTR, &mddev->recovery); in error()
1900 &rdev->mddev->recovery); in end_sync_write()
1982 if (test_bit(MD_RECOVERY_CHECK, &mddev->recovery)) in sync_request_write()
[all …]
Draid1.c124 if (test_bit(MD_RECOVERY_REQUESTED, &pi->mddev->recovery)) in r1buf_pool_alloc()
136 if (!test_bit(MD_RECOVERY_REQUESTED, &pi->mddev->recovery)) { in r1buf_pool_alloc()
421 conf->mddev->recovery); in raid1_end_write_request()
1476 set_bit(MD_RECOVERY_INTR, &mddev->recovery); in error()
1746 mddev->recovery); in end_sync_write()
1782 rdev->mddev->recovery); in r1_sync_page_io()
1861 set_bit(MD_RECOVERY_INTR, &mddev->recovery); in fix_sync_read_error()
1992 if (j < 0 || (test_bit(MD_RECOVERY_CHECK, &mddev->recovery) in process_checks()
2018 if (test_bit(MD_RECOVERY_REQUESTED, &mddev->recovery)) in sync_request_write()
2030 !test_bit(MD_RECOVERY_SYNC, &mddev->recovery)))) in sync_request_write()
[all …]
Draid5.c2459 &rdev->mddev->recovery); in raid5_end_write_request()
2515 set_bit(MD_RECOVERY_INTR, &mddev->recovery); in error()
3211 if (test_bit(MD_RECOVERY_RECOVER, &conf->mddev->recovery)) { in handle_failed_sync()
3750 if (test_bit(MD_RECOVERY_CHECK, &conf->mddev->recovery)) in handle_parity_checks5()
3902 if (test_bit(MD_RECOVERY_CHECK, &conf->mddev->recovery)) in handle_parity_checks6()
4186 test_bit(MD_RECOVERY_REQUESTED, &(conf->mddev->recovery))) in analyse_stripe()
5462 || test_bit(MD_RECOVERY_INTR, &mddev->recovery)); in reshape_request()
5471 test_bit(MD_RECOVERY_INTR, &mddev->recovery)); in reshape_request()
5472 if (test_bit(MD_RECOVERY_INTR, &mddev->recovery)) in reshape_request()
5560 || test_bit(MD_RECOVERY_INTR, &mddev->recovery)); in reshape_request()
[all …]
Dmd.h358 unsigned long recovery; member
692 set_bit(MD_RECOVERY_NEEDED, &mddev->recovery); in rdev_dec_pending()
Dmd-cluster.c271 set_bit(MD_RECOVERY_NEEDED, &mddev->recovery); in recover_bitmaps()
389 set_bit(MD_RECOVERY_NEEDED, &mddev->recovery); in process_suspend_info()
684 set_bit(MD_RECOVERY_NEEDED, &mddev->recovery); in gather_all_resync_info()
Dbitmap.c1849 set_bit(MD_RECOVERY_NEEDED, &bitmap->mddev->recovery); in bitmap_load()
2127 if (mddev->recovery || mddev->sync_thread) in location_store()
DKconfig388 reads. Useful in some recovery situations.
/linux-4.4.14/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()
DMakefile37 ath6kl_core-y += recovery.o
/linux-4.4.14/Documentation/devicetree/bindings/input/touchscreen/
Dtsc2005.txt15 - ti,esd-recovery-timeout-ms : integer, if the touchscreen does not respond after
39 ti,esd-recovery-timeout-ms = <8000>;
62 ti,esd-recovery-timeout-ms = <8000>;
/linux-4.4.14/Documentation/PCI/
D00-INDEX7 pci-error-recovery.txt
8 - info on PCI error recovery
Dpci-error-recovery.txt25 of a bus disconnection, and then performing error recovery.
28 Reporting and recovery is performed in several steps. First, when
37 Next, recovery is performed in several stages. Most of the complexity
56 through a large number of contortions to complete recovery. Almost all
60 device drivers already handle very similar recovery procedures;
70 The error recovery API support is exposed to the driver in the form of
73 and the actual recovery steps taken are platform dependent. The
106 is assumed that the driver is not doing any direct recovery and requires
155 particular, if the platform doesn't isolate slots), and recovery
159 then recovery proceeds to STEP 4 (Slot Reset).
[all …]
Dpcieaer-howto.txt35 - Performs error recovery actions.
152 3.2.2 PCI error-recovery callbacks
156 when performing error recovery actions.
161 pci-error-recovery.txt except pci express specific parts (e.g.
162 reset_link). Pls. refer to pci-error-recovery.txt for detailed
172 require any recovery actions. The AER driver clears the device's
224 error recovery handler (pci_driver->err_handler is equal to NULL)?
233 A: Fatal error recovery will fail if the errors are reported by the
253 Debugging PCIe AER error recovery code is quite difficult because it
Dpci.txt122 err_handler See Documentation/PCI/pci-error-recovery.txt
/linux-4.4.14/drivers/ata/
Dpata_cs5520.c49 int recovery; member
78 (cs5520_pio_clocks[pio].recovery << 4) | in cs5520_set_timings()
83 (cs5520_pio_clocks[pio].recovery << 4) | in cs5520_set_timings()
87 (cs5520_pio_clocks[pio].recovery << 4) | in cs5520_set_timings()
Dpata_legacy.c655 int active, recovery; in qdi65x0_set_piomode() local
663 recovery = 18 - clamp_val(t.recover, 3, 18); in qdi65x0_set_piomode()
666 recovery = 15 - clamp_val(t.recover, 0, 15); in qdi65x0_set_piomode()
668 timing = (recovery << 4) | active | 0x08; in qdi65x0_set_piomode()
790 int active, recovery; in winbond_set_piomode() local
803 recovery = (clamp_val(t.recover, 1, 15) + 1) & 0x0F; in winbond_set_piomode()
804 timing = (active << 4) | recovery; in winbond_set_piomode()
Dpata_sis.c234 static const u8 recovery[] = { 0x00, 0x06, 0x04, 0x03, 0x03 }; in sis_old_set_piomode() local
245 t2 |= recovery[speed]; in sis_old_set_piomode()
/linux-4.4.14/drivers/i2c/busses/
Di2c-uniphier.c181 bool recovery = false; in uniphier_i2c_master_xfer_one() local
198 recovery = true; in uniphier_i2c_master_xfer_one()
206 recovery = true; in uniphier_i2c_master_xfer_one()
211 if (recovery) in uniphier_i2c_master_xfer_one()
/linux-4.4.14/drivers/staging/unisys/Documentation/
Dproc-entries.txt73 and the Linux-based installation and recovery tool. These values are
80 next reboot will launch the installation and recovery tool. If set to
85 and recovery tool mode requested for the next boot.
88 and recovery tool to pass status and result information back to the
/linux-4.4.14/Documentation/devicetree/bindings/sound/
Dst,sta32x.txt40 If present, thermal warning recovery is enabled.
45 - st,fault-detect-recovery:
46 If present, then fault recovery will be enabled.
Dcs35l32.txt39 - cirrus,battery-recovery : Low battery nominal recovery threshold, rising VP.
Dst,sta350.txt40 If present, thermal warning recovery is enabled.
45 - st,fault-detect-recovery:
46 If present, then fault recovery will be enabled.
/linux-4.4.14/fs/jbd2/
DMakefile7 jbd2-objs := transaction.o commit.o recovery.o checkpoint.o revoke.o journal.o
/linux-4.4.14/arch/arm/boot/dts/
Dimx6q-gk802.dts43 recovery-button {
44 label = "recovery";
Drk3288-veyron.dtsi511 recovery-switch {
Domap3-n900.dts840 ti,esd-recovery-timeout-ms = <8000>;
/linux-4.4.14/fs/nilfs2/
DMakefile3 btnode.o bmap.o btree.o direct.o dat.o recovery.o \
DKconfig9 consistency like conventional LFS, it achieves quick recovery after
/linux-4.4.14/fs/ocfs2/dlm/
Ddlmlock.c566 int convert = 0, recovery = 0; in dlmlock() local
588 recovery = (flags & LKM_RECOVERY); in dlmlock()
590 if (recovery && in dlmlock()
675 if (!recovery) in dlmlock()
716 if (recovery) { in dlmlock()
/linux-4.4.14/drivers/misc/genwqe/
DKconfig16 int "Use platform recovery procedures (0=off, 1=on)"
/linux-4.4.14/Documentation/scsi/
Dscsi_eh.txt176 performs during recovery. This will be discussed in [2-2].
178 Once recovery is complete, SCSI EH resumes normal operation by
204 To achieve these goals, EH performs recovery actions with increasing
220 During recovery, the following rules are followed
223 eh_work_q. If a recovery action succeeds for a scmd, recovered
226 Note that single recovery action on a scmd can recover multiple
233 - EH reuses failed scmds to issue commands for recovery. For
312 causes higher-severity recovery to be taken for the scmd.
345 states, no further recovery action is needed.
428 scsi_unjam_host() and it is responsible for whole recovery process.
DBusLogic.txt45 tune driver performance and error recovery to their particular needs.
155 The driver implements extensive error recovery procedures. When the higher
159 based on the recommendation of the SCSI subsystem. Error recovery strategies
163 recovery entirely to avoid perturbing an improperly functioning device. If
164 the bus device reset error recovery strategy is selected and sending a bus
172 device. These error recovery options improve overall system robustness by
190 data transfer and error recovery statistics are available through the
Ddpti.txt70 * Add ioctl passthru error recovery
DChangeLog.ips107 - Fix error recovery code
Daic79xx.txt148 - Correct a race condition in our error recovery handler.
158 - Improve recovery for certain PCI-X errors.
171 - Added abort and target/lun reset error recovery handler and
DChangeLog.arcmsr57 ** 1.implement PCI-Express error recovery function and AER capability
DChangeLog.sym53c8xx_248 - Cleanup a bit the PPR failure recovery code.
DFlashPoint.txt143 test system provided an ideal environment for testing error recovery
DChangeLog.megaraid609 ix. Better implementation of error handling and recovery. Driver now
610 performs extended errors recovery for instances like scsi cable pull.
DChangeLog.ncr53c8xx350 Remove the error recovery code that have'nt been really useful.
398 - Buglet fixed in parity error recovery SCRIPTS (never tested).
DChangeLog.sym53c8xx409 - Major rewrite of the interrupt handling and recovery stuff for
417 - Add 'recovery' option to driver set-up.
Dscsi_mid_low_api.txt818 * EH_NOT_HANDLED Begin normal error recovery
825 * Notes: This is to give the LLD an opportunity to do local recovery.
826 * This recovery is limited to determining if the outstanding command
/linux-4.4.14/fs/gfs2/
DMakefile7 recovery.o rgrp.o super.o sys.o trans.o util.o
/linux-4.4.14/fs/f2fs/
DMakefile4 f2fs-y += checkpoint.o gc.o data.o node.o segment.o recovery.o
Dsuper.c1036 int *recovery) in read_raw_super_block() argument
1046 *recovery = 1; in read_raw_super_block()
1064 *recovery = 1; in read_raw_super_block()
1134 int recovery, i; in f2fs_fill_super() local
1140 recovery = 0; in f2fs_fill_super()
1153 err = read_raw_super_block(sb, &raw_super, &raw_super_buf, &recovery); in f2fs_fill_super()
1353 if (recovery && !f2fs_readonly(sb) && !bdev_read_only(sb->s_bdev)) { in f2fs_fill_super()
/linux-4.4.14/fs/ubifs/
DMakefile6 ubifs-y += recovery.o ioctl.o lpt_commit.o tnc_misc.o xattr.o debug.o
/linux-4.4.14/Documentation/filesystems/
Dgfs2-uevents.txt39 of journal recovery for one of the filesystems journals. It has
45 recovery via the /sys/fs/gfs2/<fsname>/lock_module/recovery file.
Dnilfs2.txt8 like conventional LFS, it achieves quick recovery after system
74 norecovery Disable recovery of the filesystem on mount.
245 summary. The recovery code of nilfs2 looks this boundary information
Dudf.txt54 The remaining are for debugging and disaster recovery:
Dceph.txt13 * Fast recovery from node failures
Df2fs.txt35 a log-like structure, thereby speeding up both file writing and crash recovery.
109 disable_roll_forward Disable the roll-forward recovery routine
110 norecovery Disable the roll-forward recovery routine, mounted read-
Dtmpfs.txt121 NUMA capability (perhaps a safe recovery kernel), or with fewer nodes
Dxfs-delayed-logging-design.txt130 It should be noted that this does not change the guarantee that log recovery
288 either be completely replayed during log recovery, or not replayed at all. If
300 only complete previous transaction in the log. This will result in a recovery
306 formatted log items and a commit record at the tail. From a recovery
309 might need to tune the recovery transaction object hash size.
Dromfs.txt40 would be for a recovery disk, when you are reinstalling a workstation
Dbtrfs.txt171 recovery
Dntfs.txt182 recover: At present only supported is recovery of
184 If read-only mount, the recovery is done
Dgfs2-glocks.txt21 used only during recovery, and even then only for journal locks.
Dext4.txt138 This will allow the recovery code in e2fsck and the
400 mode - metadata journaling. A crash+recovery can cause incorrect data to
Dxfs.txt167 The filesystem will be mounted without running log recovery.
Dxfs-self-describing-metadata.txt348 log recovery. So, it's gone unnoticed until now. This won't matter immediately -
/linux-4.4.14/drivers/staging/unisys/Documentation/ABI/
Dsysfs-platform-visorchipset47 Description: This field is used to tell s-Par which type of recovery tool
83 the recovery message.
102 the initial recovery message.
/linux-4.4.14/arch/powerpc/platforms/powernv/
DKconfig28 recovery diagnostics on OpenPower machines
/linux-4.4.14/drivers/staging/rtl8188eu/include/
Dphy.h29 void rtl88eu_phy_iq_calibrate(struct adapter *adapter, bool recovery);
/linux-4.4.14/Documentation/DocBook/
D.filesystems.xml.cmd2 …node.c fs/debugfs/file.c include/linux/jbd2.h fs/jbd2/journal.c fs/jbd2/recovery.c fs/jbd2/transac…
Dlibata.xml.db151 API-ata-msense-rw-recovery
Dfilesystems.xml.db256 API-jbd2-journal-skip-recovery
Ddevice-drivers.xml.db546 API-mpt-do-ioc-recovery
1086 API-struct-i2c-bus-recovery-info
/linux-4.4.14/drivers/net/wireless/realtek/rtlwifi/rtl8192c/
Ddm_common.h140 void rtl92c_phy_iq_calibrate(struct ieee80211_hw *hw, bool recovery);
/linux-4.4.14/Documentation/i2c/
Dfault-codes9 faults. There may be fancier recovery schemes that are appropriate in
11 recovery, triggered by a fault report, there is no error.
59 SMBus adapter) needs some fault recovery (such as resetting),
/linux-4.4.14/firmware/advansys/
Dmcode.bin.ihex147 /* Microcode buffer is kept after initialization for error recovery. */
D3550.bin.ihex317 /* Microcode buffer is kept after initialization for error recovery. */
D38C0800.bin.ihex336 /* Microcode buffer is kept after initialization for error recovery. */
D38C1600.bin.ihex398 /* Microcode buffer is kept after initialization for error recovery. */
/linux-4.4.14/Documentation/powerpc/
D00-INDEX16 eeh-pci-error-recovery.txt
Deeh-pci-error-recovery.txt78 Detection and recovery are performed with the aid of ppc64
92 pending work) and start recovery of the card. Recovery normally
115 At this time, a generic EEH recovery mechanism has been implemented,
117 EEH recovery. This generic mechanism piggy-backs on the PCI hotplug
162 To assist in the recovery of the device, eeh.c exports the
295 There are several issues with the current EEH software recovery design,
Dcxlflash.txt29 special path for user space access, and performing error recovery. It
296 This ioctl is used to drive recovery (if such an action is warranted)
298 is re-established upon successful recovery.
/linux-4.4.14/Documentation/vm/
Dhwpoison.txt4 (``MCA recovery''). This requires the OS to declare a page "poisoned",
51 There are two (actually three) modi memory failure recovery can be in:
54 All memory failures cause a panic. Do not attempt recovery.
/linux-4.4.14/drivers/net/can/softing/
DKconfig15 As such, some actions (start/stop/busoff recovery) on 1 bus
/linux-4.4.14/Documentation/devicetree/bindings/i2c/
Di2c-imx.txt20 bus recovery, call it "gpio" state
/linux-4.4.14/Documentation/isdn/
DREADME.pcbit30 version includes several procedures for error recovery that should
/linux-4.4.14/Documentation/filesystems/nfs/
Dnfs.txt24 is associated with this identity. To support robust NFSv4 state recovery
39 or loss of state during NFS reboot recovery or transparent state migration.
/linux-4.4.14/Documentation/devicetree/bindings/memory-controllers/
Dingenic,jz4780-nemc.txt36 - ingenic,nemc-tSTRV: Static memory recovery time in nanoseconds.
/linux-4.4.14/arch/mips/sibyte/
DKconfig128 bool "All cache exceptions considered fatal (no recovery attempted)"
/linux-4.4.14/tools/testing/selftests/rcutorture/doc/
Dinitrd.txt73 export recovery=
/linux-4.4.14/Documentation/
Dmd.txt442 correct. This is normally zero, but during a recovery
443 operation it will steadily increase, and if the recovery is
444 interrupted, restoring this value can cause recovery to
508 'idle' will stop an active resync/recovery etc. There is no
509 guarantee that another resync/recovery may not be automatically
512 'resync' or 'recovery' can be used to restart the
519 "recover" if a recovery seems to be needed, but cannot be
Dmd-cluster.txt127 starts a cluster recovery thread. The cluster recovery thread:
Dvfio.txt312 error recovery. A PE may be a single or multi-function IOA (IO Adapter), a
329 VFIO_EEH_PE_OP - provides an API for EEH setup, error detection and recovery.
410 * recovery is finished.
Drobust-futexes.txt139 - no kernel-space recovery call (FUTEX_RECOVER) is needed.
Dinitrd.txt296 A third scenario is more convenient recovery disks, because information
Dxillybus.txt245 even though the PCIe standard requires a graceful recovery.
Dkernel-docs.txt99 Keywords: software architecture, architecture recovery,
Dkernel-parameters.txt1862 hot-unplug link recovery
2324 not to attempt recovery of lost locks.
/linux-4.4.14/arch/alpha/lib/
Dev6-copy_user.S230 $exitout: # Destination for exception recovery(?)
Dev6-clear_user.S219 $exception: # Destination for exception recovery(?)
/linux-4.4.14/Documentation/ide/
DChangeLog.ide-tape.1995-2002115 * Some improvements in error recovery.
137 * Some error recovery bug fixes.
228 * Onstream read recovery.
DChangeLog.ide-floppy.1996-20027 * Ver 0.3 Dec 2 96 Fixed error recovery bug.
/linux-4.4.14/drivers/scsi/aic7xxx/
DKconfig.aic79xx42 The bus settle delay following all error recovery actions is
DKconfig.aic7xxx47 The bus settle delay following all error recovery actions is
Daic79xx.seq2144 * recovery can be performed.
/linux-4.4.14/Documentation/x86/x86_64/
Dmachinecheck65 Note this only makes a difference if the CPU allows recovery
/linux-4.4.14/fs/nfsd/
DKconfig115 testing error recovery on the NFS client.
/linux-4.4.14/Documentation/device-mapper/
Ddm-raid.txt141 # min recovery rate at 20 kiB/sec/disk
169 recovery. Here is a fuller description of the individual fields:
Dthin-provisioning.txt306 contain the string 'Fail'. The userspace recovery tools
395 will just contain the string 'Fail'. The userspace recovery
Dcache.txt259 contain the string 'Fail'. The userspace recovery tools
/linux-4.4.14/arch/powerpc/boot/dts/
Dac14xx.dts70 label = "recovery";
Dc2k.dts356 label = "recovery";
/linux-4.4.14/drivers/net/wireless/ti/wlcore/
Dconf.h1392 struct conf_recovery_settings recovery; member
Dmain.c337 wl->conf.recovery.bug_on_recovery = (u8) bug_on_recovery; in wlcore_adjust_conf()
340 wl->conf.recovery.no_recovery = (u8) no_recovery; in wlcore_adjust_conf()
1000 BUG_ON(wl->conf.recovery.bug_on_recovery && in wl1271_recovery_work()
1003 if (wl->conf.recovery.no_recovery) { in wl1271_recovery_work()
/linux-4.4.14/Documentation/ioctl/
Dbotching-up-ioctls.txt112 entire box (by means of an unkillable X process). If the state recovery is
116 * Have testcases for the really tricky corner cases in your error recovery code
/linux-4.4.14/Documentation/blockdev/
Dcciss.txt165 side during the SCSI error recovery process, the cciss driver only
DREADME.DAC960465 recovery procedures. Concurrently with the above, the driver status available
/linux-4.4.14/include/target/iscsi/
Discsi_target_core.h309 enum datain_req_rec_table recovery; member
/linux-4.4.14/drivers/scsi/
Dncr53c8xx.h539 u8 recovery; member
DKconfig1635 boot process fractionally longer but may assist recovery from errors
Dncr53c8xx.c753 driver_setup.recovery = val; in sym53c8xx__setup()
/linux-4.4.14/drivers/staging/rtl8188eu/hal/
Dphy.c1311 void rtl88eu_phy_iq_calibrate(struct adapter *adapt, bool recovery) in rtl88eu_phy_iq_calibrate() argument
1337 if (recovery) { in rtl88eu_phy_iq_calibrate()
/linux-4.4.14/mm/
DKconfig351 bool "Enable recovery from hardware memory errors"
356 with MCA recovery. This allows a system to continue running
/linux-4.4.14/drivers/staging/lustre/
Dsysfs-fs-lustre301 Controls if client should replay unused locks during recovery
303 recovery times might become prolonged.
/linux-4.4.14/Documentation/ia64/
Dmca.txt15 specification for ia64 SAL, error recovery and unwind, it is not as
/linux-4.4.14/arch/powerpc/
DKconfig942 One use is for the kexec on panic case where the recovery kernel
1052 One use is for the kexec on panic case where the recovery kernel
/linux-4.4.14/Documentation/trace/
Dftrace-design.txt166 the fault recovery table (the asm(...) code). The rest should be the same
/linux-4.4.14/Documentation/sysctl/
Dvm.txt416 Enable memory failure recovery (when supported by the platform)
418 1: Attempt recovery.
/linux-4.4.14/arch/ia64/
DKconfig464 tristate "MCA recovery from errors other than TLB."
/linux-4.4.14/drivers/net/wireless/ti/wl12xx/
Dmain.c376 .recovery = {
/linux-4.4.14/Documentation/networking/
Dip-sysctl.txt244 losses into fast recovery (draft-dukkipati-tcpm-tcp-loss-probe-01).
248 2 enables ER but delays fast recovery and fast retransmit
295 F-RTO is an enhanced recovery algorithm for TCP retransmission
437 This value is a bitmap to enable various experimental loss recovery
Dbonding.txt746 when failure of the active slave or recovery of the primary slave
807 slave after a link recovery has been detected. This option is
2505 during switch initialization (e.g., during recovery after a switch
Dcan.txt1152 bus-off recovery can be enabled by setting the "restart-ms" to a
/linux-4.4.14/drivers/net/wireless/ti/wl18xx/
Dmain.c504 .recovery = {
/linux-4.4.14/lib/
DKconfig.debug1677 tristate "Self test for hardware accelerated raid6 recovery"
1682 recovery of all the possible two disk failure scenarios for a
1684 raid6 recovery routines, and will optionally use an offload
/linux-4.4.14/Documentation/s390/
Dcds.txt339 bottom-half, unless a non deterministically long running error recovery procedure
/linux-4.4.14/Documentation/development-process/
D4.Coding270 fact of the matter, though, is that the resulting failure recovery paths
/linux-4.4.14/Documentation/nvdimm/
Dnvdimm.txt159 NVDIMM storage, it does not provide the best system RAS (recovery,
/linux-4.4.14/tools/perf/Documentation/
Dintel-pt.txt238 starting point for decoding or recovery from errors.
/linux-4.4.14/Documentation/cgroups/
Dcgroups.txt216 error-recovery issues.
Dcpusets.txt150 - in vmscan.c, to restrict page recovery to the current cpuset.
/linux-4.4.14/Documentation/usb/
Dpower-management.txt581 implementation shares the same device recovery path (and honors the same
/linux-4.4.14/drivers/infiniband/ulp/isert/
Dib_isert.c2912 isert_get_dataout(struct iscsi_conn *conn, struct iscsi_cmd *cmd, bool recovery) in isert_get_dataout() argument
/linux-4.4.14/arch/x86/
DKconfig1862 One use is for the kexec on panic case where the recovery kernel
/linux-4.4.14/
DMAINTAINERS4176 F: Documentation/powerpc/eeh-pci-error-recovery.txt
8105 F: Documentation/PCI/pci-error-recovery.txt