Home
last modified time | relevance | path

Searched full:tolerate (Results 1 – 25 of 78) sorted by relevance

1234

/linux/arch/x86/include/asm/
H A Dkfence.h52 * does not flush TLBs on all CPUs. We can tolerate some inaccuracy; in kfence_protect_page()
/linux/arch/powerpc/tools/
H A Dhead_check.sh30 # tolerate them being inserted into head code, they can't be allowed in low
/linux/tools/testing/selftests/powerpc/pmu/
H A Dcount_instructions.c65 /* Tolerate a difference below 0.0001 % */ in do_count_loop()
H A Dcount_stcx_fail.c70 /* Tolerate a difference below 0.0001 % */ in do_count_loop()
/linux/tools/memory-model/Documentation/
H A Daccess-marking.txt133 Values from some reads feed into heuristics that can tolerate occasional
157 After all, if the heuristic can tolerate the occasional bogus value
158 due to compiler-mangled reads, it can also tolerate the occasional
/linux/tools/testing/selftests/powerpc/pmu/ebb/
H A Dinstruction_count_test.c61 /* Tolerate a difference of up to 0.0001 % */ in do_count_loop()
/linux/Documentation/ABI/testing/
H A Dsysfs-platform-dfl-port47 Set ltr to 1 if the AFU can tolerate latency >= 40us or set it
H A Dsysfs-platform-dfl-fme245 Function Units (AFUs) can tolerate latency >= 40us for memory
/linux/arch/powerpc/include/asm/
H A Dparavirt.h173 * migration, and callers can tolerate the potential for in vcpu_is_preempted()
/linux/Documentation/RCU/
H A DlistRCU.rst228 So, when readers can tolerate stale data and when entries are either added or
487 Read-mostly list-based data structures that can tolerate stale data are
/linux/tools/power/x86/x86_energy_perf_policy/
H A Dx86_energy_perf_policy.883 The processor will tolerate minor performance compromise
/linux/Documentation/driver-api/thermal/
H A Dcpu-idle-cooling.rst132 - It is less than or equal to the latency we tolerate when the
/linux/Documentation/mm/
H A Dnuma.rst127 Some kernel allocations do not want or cannot tolerate this allocation fallback
/linux/Documentation/input/devices/
H A Dntrig.rst43 frames. By holding off on deactivation for a few frames we can tolerate false
/linux/mm/kasan/
H A Dhw_tags.c342 * The kernel doesn't tolerate having the PC register tagged. in __kasan_unpoison_vmalloc()
/linux/Documentation/accel/qaic/
H A Dqaic.rst24 MSIs per second. It has been observed that most systems cannot tolerate this
/linux/tools/testing/selftests/net/forwarding/
H A Dvxlan_bridge_1d.sh497 # Tolerate a couple stray extra packets.
617 # Tolerate a couple stray extra packets.
H A Dvxlan_bridge_1d_ipv6.sh618 # Tolerate a couple stray extra packets.
730 # Tolerate a couple stray extra packets.
/linux/arch/powerpc/include/asm/nohash/
H A Dpgtable.h338 * mappings, we can't tolerate spurious faults, so make sure in __set_pte_at()
/linux/drivers/platform/x86/intel/ifs/
H A Difs.h70 * is running latency sensitive applications that cannot tolerate an
/linux/arch/arm64/mm/
H A Dcontpte.c17 * on the PTL. But kernel mappings can't tolerate faults. in mm_is_user()
/linux/Documentation/watchdog/
H A Dwatchdog-kernel-api.rst94 if the hardware can not tolerate lower intervals between heartbeats.
/linux/Documentation/arch/powerpc/
H A Deeh-pci-error-recovery.rst318 Reiserfs does not tolerate errors returned from the block device.
/linux/Documentation/networking/
H A Drds.rst58 does not change. RDS will tolerate IPs moving around (eg in
/linux/kernel/debug/kdb/
H A Dkdb_support.c74 * tolerate the possibility of garbled symbol display from the outer kdb

1234