Searched refs:paranoid (Results 1 – 9 of 9) sorted by relevance
75 The expensive (paranoid) way is to read back the MSR_GS_BASE value100 must use idtentry with paranoid=1 to handle gsbase correctly. This107 We try to only use IST entries and the paranoid entry code for vectors109 generate all 'normal' entry points with the regular (faster) paranoid=0
117 In this case, if we're being super paranoid, it might make sense to
371 ; paranoid check, given A1 was active when A2 happened, preempt count
2656 int paranoid; in evsel__fallback() local2678 (paranoid = perf_event_paranoid()) > 1) { in evsel__fallback()2700 " samples", paranoid); in evsel__fallback()
547 Enable paranoid checks and self-test of both ARC-specific and generic
299 If you're exceptionally paranoid, there are 3 ways of making metadata
930 already in the COW file header. If you're paranoid, boot the new
342 /* paranoid check ... */
659 If you are paranoid and not sure what the kernel will be
