| /kernel/linux/linux-6.6/drivers/target/iscsi/ |
| D | iscsi_target_datain_values.c | 76 * For Normal and Recovery DataSequenceInOrder=Yes and DataPDUInOrder=Yes.
90 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()
174 * For Normal and Recovery DataSequenceInOrder=No and DataPDUInOrder=Yes.
[all …]
|
| /kernel/linux/linux-5.10/drivers/target/iscsi/ |
| D | iscsi_target_datain_values.c | 76 * For Normal and Recovery DataSequenceInOrder=Yes and DataPDUInOrder=Yes.
90 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()
174 * For Normal and Recovery DataSequenceInOrder=No and DataPDUInOrder=Yes.
[all …]
|
| /kernel/linux/linux-6.6/drivers/remoteproc/ |
| D | remoteproc_sysfs.c | 22 * By writing to the 'recovery' sysfs entry, we control the behavior of the
23 * recovery mechanism dynamically. The default value of this entry is "enabled".
25 * The 'recovery' sysfs entry supports these commands:
29 * processor crashes while recovery is disabled, it will
30 * be automatically recovered too as soon as recovery is enabled.
36 * recover: This function will trigger an immediate recovery if the
38 * or checking the recovery state (enabled/disabled).
40 * additional crashes to happen after enabling recovery. In this
41 * case, enabling recovery will make it hard to debug subsequent
42 * crashes, so it's recommended to keep recovery disabled, and
[all …]
|
| D | remoteproc_debugfs.c | 61 * disabled: By default coredump collection is disabled. Recovery will
68 * recovery process will have to wait until data is read by
174 /* expose recovery flag via debugfs */
185 * By writing to the 'recovery' debugfs entry, we control the behavior of the
186 * recovery mechanism dynamically. The default value of this entry is "enabled".
188 * The 'recovery' debugfs entry supports these commands:
192 * processor crashes while recovery is disabled, it will
193 * be automatically recovered too as soon as recovery is enabled.
199 * recover: This function will trigger an immediate recovery if the
201 * or checking the recovery state (enabled/disabled).
[all …]
|
| /kernel/linux/linux-5.10/drivers/remoteproc/ |
| D | remoteproc_sysfs.c | 22 * By writing to the 'recovery' sysfs entry, we control the behavior of the
23 * recovery mechanism dynamically. The default value of this entry is "enabled".
25 * The 'recovery' sysfs entry supports these commands:
29 * processor crashes while recovery is disabled, it will
30 * be automatically recovered too as soon as recovery is enabled.
36 * recover: This function will trigger an immediate recovery if the
38 * or checking the recovery state (enabled/disabled).
40 * additional crashes to happen after enabling recovery. In this
41 * case, enabling recovery will make it hard to debug subsequent
42 * crashes, so it's recommended to keep recovery disabled, and
[all …]
|
| D | remoteproc_debugfs.c | 61 * disabled: By default coredump collection is disabled. Recovery will
68 * recovery process will have to wait until data is read by
174 /* expose recovery flag via debugfs */
185 * By writing to the 'recovery' debugfs entry, we control the behavior of the
186 * recovery mechanism dynamically. The default value of this entry is "enabled".
188 * The 'recovery' debugfs entry supports these commands:
192 * processor crashes while recovery is disabled, it will
193 * be automatically recovered too as soon as recovery is enabled.
199 * recover: This function will trigger an immediate recovery if the
201 * or checking the recovery state (enabled/disabled).
[all …]
|
| /kernel/linux/linux-6.6/fs/ocfs2/dlm/ |
| D | dlmrecovery.c | 5 * recovery stuff
127 /* Worker function used during recovery. */
164 * RECOVERY THREAD
169 /* wake the recovery thread in dlm_kick_recovery_thread()
171 * 1) sleeping with no recovery happening in dlm_kick_recovery_thread()
172 * 2) sleeping with recovery mastered elsewhere in dlm_kick_recovery_thread()
173 * 3) recovery mastered here, waiting on reco data */ in dlm_kick_recovery_thread()
178 /* Launch the recovery thread */
181 mlog(0, "starting dlm recovery thread...\n"); in dlm_launch_recovery_thread()
197 mlog(0, "waiting for dlm recovery thread to exit\n"); in dlm_complete_recovery_thread()
[all …]
|
| /kernel/linux/linux-5.10/fs/ocfs2/dlm/ |
| D | dlmrecovery.c | 7 * recovery stuff
136 /* Worker function used during recovery. */
173 * RECOVERY THREAD
178 /* wake the recovery thread in dlm_kick_recovery_thread()
180 * 1) sleeping with no recovery happening in dlm_kick_recovery_thread()
181 * 2) sleeping with recovery mastered elsewhere in dlm_kick_recovery_thread()
182 * 3) recovery mastered here, waiting on reco data */ in dlm_kick_recovery_thread()
187 /* Launch the recovery thread */
190 mlog(0, "starting dlm recovery thread...\n"); in dlm_launch_recovery_thread()
206 mlog(0, "waiting for dlm recovery thread to exit\n"); in dlm_complete_recovery_thread()
[all …]
|
| /kernel/linux/linux-5.10/drivers/s390/scsi/ |
| D | zfcp_dbf.h | 28 * struct zfcp_dbf_rec_trigger - trace record for triggered recovery action
29 * @ready: number of ready recovery actions
30 * @running: number of running recovery actions
31 * @want: wanted recovery action
32 * @need: needed recovery action
42 * struct zfcp_dbf_rec_running - trace record for running recovery
45 * @rec_step: current step of the recovery action
58 * enum zfcp_dbf_rec_id - recovery trace record id
59 * @ZFCP_DBF_REC_TRIG: triggered recovery identifier
60 * @ZFCP_DBF_REC_RUN: running recovery identifier
[all …]
|
| /kernel/linux/linux-6.6/drivers/s390/scsi/ |
| D | zfcp_dbf.h | 28 * struct zfcp_dbf_rec_trigger - trace record for triggered recovery action
29 * @ready: number of ready recovery actions
30 * @running: number of running recovery actions
31 * @want: wanted recovery action
32 * @need: needed recovery action
42 * struct zfcp_dbf_rec_running - trace record for running recovery
45 * @rec_step: current step of the recovery action
58 * enum zfcp_dbf_rec_id - recovery trace record id
59 * @ZFCP_DBF_REC_TRIG: triggered recovery identifier
60 * @ZFCP_DBF_REC_RUN: running recovery identifier
[all …]
|
| /kernel/linux/linux-5.10/Documentation/PCI/ |
| D | pci-error-recovery.rst | 4 PCI Error Recovery
26 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
110 is assumed that the driver is not doing any direct recovery and requires
159 particular, if the platform doesn't isolate slots), and recovery
[all …]
|
| /kernel/linux/linux-6.6/Documentation/PCI/ |
| D | pci-error-recovery.rst | 4 PCI Error Recovery
26 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
[all …]
|
| D | pcieaer-howto.rst | 43 - 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 …]
|
| /kernel/linux/linux-5.10/fs/gfs2/ |
| D | lock_dlm.c | 20 #include "recovery.h"
329 * dlm/gfs2 recovery coordination using dlm_recover callbacks
335 * 4. dlm_controld starts and finishes its own user level recovery
336 * 5. dlm_controld starts dlm-kernel dlm_recoverd to do kernel recovery
338 * 7. dlm_recoverd does its own lock recovery
344 * 13. gfs2_recover provides recovery results to gfs2_control (recovery_result)
348 * - failures during recovery
375 * - parallel recovery steps across all nodes
390 * and missing a journal recovery?
401 * require recovery, because the mount in step 4 could not have
[all …]
|
| /kernel/linux/linux-6.6/fs/gfs2/ |
| D | lock_dlm.c | 20 #include "recovery.h"
349 * dlm/gfs2 recovery coordination using dlm_recover callbacks
355 * 4. dlm_controld starts and finishes its own user level recovery
356 * 5. dlm_controld starts dlm-kernel dlm_recoverd to do kernel recovery
358 * 7. dlm_recoverd does its own lock recovery
364 * 13. gfs2_recover provides recovery results to gfs2_control (recovery_result)
368 * - failures during recovery
395 * - parallel recovery steps across all nodes
410 * and missing a journal recovery?
421 * require recovery, because the mount in step 4 could not have
[all …]
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-class-remoteproc | 83 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.
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | sysfs-class-remoteproc | 83 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.
|
| /kernel/linux/linux-6.6/arch/ia64/lib/ |
| D | strlen.S | 17 * 09/24/99 S.Eranian add speculation recovery code
39 // settings of the DCR register, we provide recovery code in case
40 // speculation fails. The recovery code is going to "redo" the work using
50 // It should be noted that we execute recovery code only when we need
52 // recovery code on pure read ahead data.
124 // We must return try the recovery code iff
132 (p6) br.cond.spnt .recover // jump to recovery if val1 is NaT
139 (p7) br.cond.spnt .recover // jump to recovery if val2 is NaT
154 // Outlined recovery code when speculation failed
193 br.ret.sptk.many rp // end of successful recovery code
|
| /kernel/linux/linux-5.10/arch/ia64/lib/ |
| D | strlen.S | 17 * 09/24/99 S.Eranian add speculation recovery code
39 // settings of the DCR register, we provide recovery code in case
40 // speculation fails. The recovery code is going to "redo" the work using
50 // It should be noted that we execute recovery code only when we need
52 // recovery code on pure read ahead data.
124 // We must return try the recovery code iff
132 (p6) br.cond.spnt .recover // jump to recovery if val1 is NaT
139 (p7) br.cond.spnt .recover // jump to recovery if val2 is NaT
154 // Outlined recovery code when speculation failed
193 br.ret.sptk.many rp // end of successful recovery code
|
| /kernel/linux/linux-6.6/Documentation/networking/devlink/ |
| D | devlink-health.rst | 23 attributes of the health reporting and recovery procedures.
33 * 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
|
| /kernel/linux/linux-5.10/Documentation/networking/devlink/ |
| D | devlink-health.rst | 23 attributes of the health reporting and recovery procedures.
33 * Recovery procedures
50 * Auto recovery attempt is being done. Depends on:
51 - Auto-recovery configuration
60 * Configure reporter's generic parameters (like: disable/enable auto recovery)
61 * Invoke recovery procedure
75 - Triggers a reporter's recovery procedure.
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | dm-region-hash.h | 84 * Region recovery control.
87 /* Prepare some regions for recovery by starting to quiesce them. */
90 /* Try fetching a quiesced region for recovery. */
93 /* Report recovery end on a region. */
96 /* Returns number of regions with recovery work outstanding. */
99 /* Start/stop recovery. */
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | dm-region-hash.h | 87 * Region recovery control.
90 /* Prepare some regions for recovery by starting to quiesce them. */
93 /* Try fetching a quiesced region for recovery. */
96 /* Report recovery end on a region. */
99 /* Returns number of regions with recovery work outstanding. */
102 /* Start/stop recovery. */
|
| /kernel/linux/linux-6.6/fs/ocfs2/ |
| D | journal.c | 81 * offline slots during recovery and mount
203 * If recovery thread is not running, we can directly transition to in ocfs2_recovery_disable()
211 /* Wait for recovery thread to acknowledge state transition */ in ocfs2_recovery_disable()
221 * At this point we know that no more recovery work can be queued so in ocfs2_recovery_disable()
222 * wait for any recovery completion work to complete. in ocfs2_recovery_disable()
237 /* disable any new recovery threads and wait for any currently in ocfs2_recovery_exit()
242 * Now that recovery is shut down, and the osb is about to be in ocfs2_recovery_exit()
946 /* Skip recovery waits here - journal inode metadata never in ocfs2_journal_init()
1311 /* Does the second half of the recovery process. By this point, the
1313 * hence it's no longer in the recovery map, but there's still some
[all …]
|
| /kernel/linux/linux-5.10/fs/ocfs2/ |
| D | journal.c | 82 * offline slots during recovery and mount
210 /* disable any new recovery threads and wait for any currently in ocfs2_recovery_exit()
217 /* At this point, we know that no more recovery threads can be in ocfs2_recovery_exit()
218 * launched, so wait for any recovery completion work to in ocfs2_recovery_exit()
224 * Now that recovery is shut down, and the osb is about to be in ocfs2_recovery_exit()
848 /* Skip recovery waits here - journal inode metadata never in ocfs2_journal_init()
1211 /* Does the second half of the recovery process. By this point, the
1213 * hence it's no longer in the recovery map, but there's still some
1214 * cleanup we can do which shouldn't happen within the recovery thread
1218 * NOTE: This function can and will sleep on recovery of other nodes
[all …]
|