Searched refs:detectors (Results 1 – 11 of 11) sorted by relevance
164 struct pri_detector *detectors[]; member175 cd->detectors[i]->reset(cd->detectors[i], dpd->last_pulse_ts); in channel_detector_reset()188 struct pri_detector *de = cd->detectors[i]; in channel_detector_exit()202 cd = kzalloc(struct_size(cd, detectors, dpd->num_radar_types), GFP_ATOMIC); in channel_detector_create()214 cd->detectors[i] = de; in channel_detector_create()292 struct pri_detector *pd = cd->detectors[i]; in dpd_add_pulse()
21 the common infrastructure for handling hardlockup detectors. It is
13 1. Bus clash or parity errors: This mechanism relies on low-level detectors
36 The soft and hard lockup detectors are built on top of the hrtimer and
4165 To disable both hard and soft lockup detectors,4430 nowatchdog [KNL] Disable both lockup detectors, i.e.8134 disables both lockup detectors. Default is 10
1120 * lockup detectors) and so should be last resort.
1102 * lockup detectors) and so should be last resort.
249 This new device type allows for non-memory type of ECC hardware detectors253 Some architectures have ECC detectors for L1, L2 and L3 caches,
1674 0 Disable both lockup detectors.1675 1 Enable both lockup detectors.
445 as the generic hardlockup detectors.
1210 # Both the "perf" and "buddy" hardlockup detectors count hrtimer1322 that watchdogs and lockup detectors are working properly.