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()186 if (cd->detectors) { in channel_detector_exit()188 struct pri_detector *de = cd->detectors[i]; in channel_detector_exit()193 kfree(cd->detectors); in channel_detector_exit()209 cd->detectors = kmalloc_array(dpd->num_radar_types, in channel_detector_create()210 sizeof(*cd->detectors), GFP_ATOMIC); in channel_detector_create()211 if (cd->detectors == NULL) in channel_detector_create()219 cd->detectors[i] = de; in channel_detector_create()297 struct pri_detector *pd = cd->detectors[i]; in dpd_add_pulse()
24 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
245 This new device type allows for non-memory type of ECC hardware detectors249 Some architectures have ECC detectors for L1, L2 and L3 caches,
3655 To disable both hard and soft lockup detectors,3945 nowatchdog [KNL] Disable both lockup detectors, i.e.7076 disables both lockup detectors. Default is 10
1119 * lockup detectors) and so should be last resort.
1101 * lockup detectors) and so should be last resort.
1622 0 Disable both lockup detectors.1623 1 Enable both lockup detectors.
426 as the generic hardlockup detectors.
1119 # Both the "perf" and "buddy" hardlockup detectors count hrtimer1220 that watchdogs and lockup detectors are working properly.
