| /openbmc/openbmc/meta-ibm/recipes-phosphor/pldm/ |
| H A D | pldm_%.bbappend | 12 #so increasing that to 10 seconds here.IBMs custom firmware stack can tolerate
|
| /openbmc/linux/arch/x86/include/asm/ |
| H A D | kfence.h | 52 * does not flush TLBs on all CPUs. We can tolerate some inaccuracy; in kfence_protect_page()
|
| /openbmc/linux/tools/testing/selftests/net/forwarding/ |
| H A D | mirror_lib.sh | 53 # Tolerate a couple stray extra packets.
|
| /openbmc/linux/arch/powerpc/tools/ |
| H A D | head_check.sh | 30 # tolerate them being inserted into head code, they can't be allowed in low
|
| /openbmc/linux/tools/testing/selftests/powerpc/pmu/ |
| H A D | count_instructions.c | 65 /* Tolerate a difference below 0.0001 % */ in do_count_loop()
|
| H A D | count_stcx_fail.c | 70 /* Tolerate a difference below 0.0001 % */ in do_count_loop()
|
| /openbmc/qemu/scripts/ |
| H A D | python_qmp_updater.py | 110 # tolerate this bad style
|
| /openbmc/linux/tools/memory-model/Documentation/ |
| H A D | access-marking.txt | 127 Values from some reads feed into heuristics that can tolerate occasional
151 After all, if the heuristic can tolerate the occasional bogus value
152 due to compiler-mangled reads, it can also tolerate the occasional
|
| /openbmc/linux/tools/testing/selftests/powerpc/pmu/ebb/ |
| H A D | instruction_count_test.c | 61 /* Tolerate a difference of up to 0.0001 % */ in do_count_loop()
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | kernel-per-CPU-kthreads.rst | 202 housekeeping CPUs, which can tolerate OS jitter.
244 application cannot tolerate:
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-platform-dfl-port | 47 Set ltr to 1 if the AFU can tolerate latency >= 40us or set it
|
| /openbmc/linux/arch/powerpc/include/asm/ |
| H A D | paravirt.h | 135 * migration, and callers can tolerate the potential for in vcpu_is_preempted()
|
| /openbmc/linux/tools/power/x86/x86_energy_perf_policy/ |
| H A D | x86_energy_perf_policy.8 | 83 The processor will tolerate minor performance compromise
|
| /openbmc/linux/Documentation/accel/qaic/ |
| H A D | qaic.rst | 21 MSIs per second. It has been observed that most systems cannot tolerate this
|
| /openbmc/linux/drivers/iio/adc/ |
| H A D | ep93xx_adc.c | 202 * We can tolerate rate setting failure because the module should in ep93xx_adc_probe()
|
| /openbmc/linux/Documentation/RCU/ |
| H A D | listRCU.rst | 219 So, when readers can tolerate stale data and when entries are either added or
478 Read-mostly list-based data structures that can tolerate stale data are
|
| /openbmc/linux/Documentation/mm/ |
| H A D | numa.rst | 127 Some kernel allocations do not want or cannot tolerate this allocation fallback
|
| /openbmc/linux/Documentation/driver-api/thermal/ |
| H A D | cpu-idle-cooling.rst | 132 - It is less than or equal to the latency we tolerate when the
|
| /openbmc/linux/Documentation/input/devices/ |
| H A D | ntrig.rst | 43 frames. By holding off on deactivation for a few frames we can tolerate false
|
| /openbmc/docs/ |
| H A D | code-of-conduct.md | 31 community, which LF Projects will not tolerate.
|
| /openbmc/linux/arch/powerpc/include/asm/nohash/ |
| H A D | pgtable.h | 203 * mappings, we can't tolerate spurious faults, so make sure in __set_pte_at()
|
| /openbmc/linux/arch/ia64/lib/ |
| H A D | clear_user.S | 49 // be ok, we can't tolerate a mistake. A classical example is the case
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | ceph.rst | 39 and can tolerate arbitrary (well, non-Byzantine) node failures. The
|
| /openbmc/linux/drivers/platform/x86/intel/ifs/ |
| H A D | ifs.h | 70 * is running latency sensitive applications that cannot tolerate an
|
| /openbmc/linux/mm/kasan/ |
| H A D | hw_tags.c | 332 * The kernel doesn't tolerate having the PC register tagged. in __kasan_unpoison_vmalloc()
|