Searched refs:paranoid (Results 1 – 10 of 10) 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
158 To be paranoid and get predictable behavior, the OS can choose to set
117 In this case, if we're being super paranoid, it might make sense to
356 ; paranoid check, given A1 was active when A2 happened, preempt count
2838 int paranoid; in evsel__fallback() local2860 (paranoid = perf_event_paranoid()) > 1) { in evsel__fallback()2881 " samples", paranoid); in evsel__fallback()
549 Enable paranoid checks and self-test of both ARC-specific and generic
297 If you're exceptionally paranoid, there are 3 ways of making metadata
939 already in the COW file header. If you're paranoid, boot the new
342 /* paranoid check ... */
665 If you are paranoid and not sure what the kernel will be
