Searched refs:paranoid (Results 1 – 10 of 10) sorted by relevance
| /Linux-v5.4/arch/x86/entry/ |
| D | entry_64.S | 869 .macro idtentry_part do_sym, has_error_code:req, read_cr2:req, paranoid:req, shift_ist=-1, ist_offs…
871 .if \paranoid
894 .if \paranoid == 0
924 .if \paranoid
971 .macro idtentry sym do_sym has_error_code:req paranoid=0 shift_ist=-1 ist_offset=0 create_gap=0 rea…
976 .if \shift_ist != -1 && \paranoid != 1
980 .if \create_gap && \paranoid
990 .if \paranoid == 1
1009 idtentry_part \do_sym, \has_error_code, \read_cr2, \paranoid, \shift_ist, \ist_offset
1011 .if \paranoid == 1
[all …]
|
| /Linux-v5.4/Documentation/x86/ |
| D | entry_64.rst | 75 The expensive (paranoid) way is to read back the MSR_GS_BASE value
100 must use idtentry with paranoid=1 to handle gsbase correctly. This
107 We try to only use IST entries and the paranoid entry code for vectors
109 generate all 'normal' entry points with the regular (faster) paranoid=0
|
| /Linux-v5.4/Documentation/livepatch/ |
| D | callbacks.rst | 117 In this case, if we're being super paranoid, it might make sense to
|
| /Linux-v5.4/arch/arc/kernel/ |
| D | entry-compact.S | 371 ; paranoid check, given A1 was active when A2 happened, preempt count
|
| /Linux-v5.4/tools/perf/util/ |
| D | evsel.c | 2333 int paranoid; in perf_evsel__fallback() local
2355 (paranoid = perf_event_paranoid()) > 1) { in perf_evsel__fallback()
2373 " samples", paranoid); in perf_evsel__fallback()
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | mandatory-locking.txt | 102 paranoid HP-UX behaviour.
|
| D | ext2.txt | 294 If you're exceptionally paranoid, there are 3 ways of making metadata
|
| /Linux-v5.4/Documentation/networking/ |
| D | can.rst | 309 /* paranoid check ... */
|
| /Linux-v5.4/init/ |
| D | Kconfig | 577 If you are paranoid and not sure what the kernel will be
|
| /Linux-v5.4/Documentation/virt/uml/ |
| D | UserModeLinux-HOWTO.txt | 1973 already in the COW file header. If you're paranoid, boot the new
|
