Searched refs:paranoid (Results 1 – 11 of 11) sorted by relevance
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/Documentation/livepatch/ |
| D | callbacks.rst | 117 In this case, if we're being super paranoid, it might make sense to
|
| /kernel/linux/linux-5.10/arch/arc/kernel/ |
| D | entry-compact.S | 371 ; paranoid check, given A1 was active when A2 happened, preempt count
|
| /kernel/linux/linux-5.10/tools/perf/util/ |
| D | evsel.c | 2510 int paranoid; in evsel__fallback() local
2532 (paranoid = perf_event_paranoid()) > 1) { in evsel__fallback()
2554 " samples", paranoid); in evsel__fallback()
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ |
| D | mandatory-locking.rst | 109 paranoid HP-UX behaviour.
|
| D | ext2.rst | 298 If you're exceptionally paranoid, there are 3 ways of making metadata
|
| /kernel/linux/linux-5.10/arch/arc/ |
| D | Kconfig | 592 Enable paranoid checks and self-test of both ARC-specific and generic
|
| /kernel/linux/linux-5.10/Documentation/virt/uml/ |
| D | user_mode_linux_howto_v2.rst | 930 already in the COW file header. If you're paranoid, boot the new
|
| /kernel/linux/linux-5.10/Documentation/networking/ |
| D | can.rst | 309 /* paranoid check ... */
|
| /kernel/linux/linux-5.10/init/ |
| D | Kconfig | 642 If you are paranoid and not sure what the kernel will be
|
| /kernel/linux/patches/linux-5.10/imx8mm_patch/patches/drivers/ |
| D | 0036_linux_drivers_staging.patch | 26758 + * ultra-paranoid, goes as high as 10,000 cycles. NB, we consume
26761 + * we're being *really* paranoid here. */
|