Home
last modified time | relevance | path

Searched refs:paranoid (Results 1 – 10 of 10) sorted by relevance

/linux-6.3-rc2/Documentation/x86/
A Dentry_64.rst75 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
A Dmicrocode.rst158 To be paranoid and get predictable behavior, the OS can choose to set
/linux-6.3-rc2/Documentation/livepatch/
A Dcallbacks.rst117 In this case, if we're being super paranoid, it might make sense to
/linux-6.3-rc2/arch/arc/kernel/
A Dentry-compact.S371 ; paranoid check, given A1 was active when A2 happened, preempt count
/linux-6.3-rc2/tools/perf/util/
A Devsel.c2853 int paranoid; in evsel__fallback() local
2875 (paranoid = perf_event_paranoid()) > 1) { in evsel__fallback()
2897 " samples", paranoid); in evsel__fallback()
/linux-6.3-rc2/arch/arc/
A DKconfig545 Enable paranoid checks and self-test of both ARC-specific and generic
/linux-6.3-rc2/Documentation/filesystems/
A Dext2.rst297 If you're exceptionally paranoid, there are 3 ways of making metadata
/linux-6.3-rc2/Documentation/virt/uml/
A Duser_mode_linux_howto_v2.rst939 already in the COW file header. If you're paranoid, boot the new
/linux-6.3-rc2/Documentation/networking/
A Dcan.rst342 /* paranoid check ... */
/linux-6.3-rc2/init/
A DKconfig664 If you are paranoid and not sure what the kernel will be

Completed in 21 milliseconds