Searched refs:paranoid (Results 1 – 10 of 10) sorted by relevance
903 .macro idtentry sym do_sym has_error_code:req paranoid=0 shift_ist=-1908 .if \shift_ist != -1 && \paranoid == 0918 .if \paranoid == 1923 .if \paranoid931 .if \paranoid959 .if \paranoid965 .if \paranoid == 1995 idtentry double_fault do_double_fault has_error_code=1 paranoid=21150 idtentry debug do_debug has_error_code=0 paranoid=1 shift_ist=DEBUG_STACK1168 idtentry machine_check do_mce has_error_code=0 paranoid=1
69 The expensive (paranoid) way is to read back the MSR_GS_BASE value94 must use idtentry with paranoid=1 to handle gsbase correctly. This101 We try to only use IST entries and the paranoid entry code for vectors103 generate all 'normal' entry points with the regular (faster) paranoid=0
374 ; paranoid check, given A1 was active when A2 happened, preempt count
102 paranoid HP-UX behaviour.
288 If you're exceptionally paranoid, there are 3 ways of making metadata
2765 int paranoid; in perf_evsel__fallback() local2787 (paranoid = perf_event_paranoid()) > 1) { in perf_evsel__fallback()2804 "kernel.perf_event_paranoid=%d, trying to fall back to excluding kernel samples", paranoid); in perf_evsel__fallback()
101 In this case, if we're being super paranoid, it might make sense to
379 0x0800 More paranoid debug in callc.c (not for normal use)
309 /* paranoid check ... */
1973 already in the COW file header. If you're paranoid, boot the new
