Home
last modified time | relevance | path

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

/linux/Documentation/arch/x86/
H 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
H A Dmicrocode.rst158 To be paranoid and get predictable behavior, the OS can choose to set
/linux/Documentation/livepatch/
H A Dcallbacks.rst117 In this case, if we're being super paranoid, it might make sense to
/linux/arch/arc/kernel/
H A Dentry-compact.S356 ; paranoid check, given A1 was active when A2 happened, preempt count
/linux/tools/perf/util/
H A Devsel.c3786 int paranoid; in evsel__fallback() local
3809 (paranoid = perf_event_paranoid()) > 1) { in evsel__fallback()
3830 " samples", paranoid); in evsel__fallback()
/linux/Documentation/virt/uml/
H A Duser_mode_linux_howto_v2.rst941 already in the COW file header. If you're paranoid, boot the new
/linux/Documentation/networking/
H A Dcan.rst342 /* paranoid check ... */
/linux/init/
H A DKconfig746 If you are paranoid and not sure what the kernel will be
/linux/Documentation/admin-guide/
H A Dkernel-parameters.txt718 Under FineIBT, enable "paranoid" mode when
724 paranoid: Add caller hash checking under FineIBT.