| /openbmc/linux/net/dccp/ |
| H A D | qpolicy.c | 48 struct sk_buff *skb, *worst = NULL; in qpolicy_prio_worst_skb() local
51 if (worst == NULL || skb->priority < worst->priority) in qpolicy_prio_worst_skb()
52 worst = skb; in qpolicy_prio_worst_skb()
53 return worst; in qpolicy_prio_worst_skb()
|
| /openbmc/linux/Documentation/devicetree/bindings/power/ |
| H A D | domain-idle-state.yaml | 33 The worst case latency in microseconds required to enter the idle
39 The worst case latency in microseconds required to exit the idle
|
| /openbmc/linux/arch/x86/boot/ |
| H A D | header.S | 448 # The worst case at the block level is a growth of the compressed data
451 # The worst case internal to a compressed block is very hard to figure.
452 # The worst case can at least be bounded by having one bit that represents
459 # block adding an extra 32767 bytes (the worst case uncompressed block size)
460 # is sufficient, to ensure that in the worst case the decompressed data for
|
| /openbmc/linux/Documentation/arch/x86/x86_64/ |
| H A D | cpu-hotplug-spec.rst | 21 In the worst case the user can overwrite this choice using a command line
|
| /openbmc/linux/tools/power/cpupower/bench/ |
| H A D | README-BENCH | 7 - Identify worst case performance loss when doing dynamic frequency
84 will always see 50% loads and you get worst performance impact never
|
| /openbmc/linux/Documentation/devicetree/bindings/regulator/ |
| H A D | vctrl.txt | 29 down in the worst case (lightest expected load).
|
| /openbmc/linux/arch/x86/kernel/cpu/mce/ |
| H A D | core.c | 1250 int *worst) in __mc_scan_banks() argument
1312 if (severity > *worst) { in __mc_scan_banks()
1314 *worst = severity; in __mc_scan_banks()
1444 int worst = 0, order, no_way_out, kill_current_task, lmce, taint = 0; in do_machine_check() local
1525 taint = __mc_scan_banks(&m, regs, final, toclear, valid_banks, no_way_out, &worst); in do_machine_check()
1537 no_way_out = worst >= MCE_PANIC_SEVERITY; in do_machine_check()
1551 if (worst >= MCE_PANIC_SEVERITY) { in do_machine_check()
1567 if (worst != MCE_AR_SEVERITY && !kill_current_task) in do_machine_check()
|
| /openbmc/linux/drivers/block/mtip32xx/ |
| H A D | mtip32xx.h | 165 u8 worst; member
|
| /openbmc/linux/Documentation/hwmon/ |
| H A D | stpddc60.rst | 41 writing to those limits since in the worst case the commanded output voltage
|
| /openbmc/linux/arch/x86/math-emu/ |
| H A D | README | 239 each function was tested at about 400 points. Ideal worst-case results
307 worst-case results which are better than the worst-case results given
321 the worst accuracy which was found (in bits) and the approximate value
326 instr arg range # tests 63.7 63.8 63.9 worst at arg
|
| /openbmc/linux/Documentation/admin-guide/media/ |
| H A D | cafe_ccic.rst | 38 then worst-case-sized buffers will be allocated at module load time.
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | pixfmt-v4l2-mplane.rst | 30 codec to support the worst-case compression scenario.
|
| /openbmc/linux/Documentation/tools/rtla/ |
| H A D | rtla-hwnoise.rst | 72 for the application. In the worst single period, the CPU caused *4 us* of
|
| /openbmc/linux/Documentation/mm/ |
| H A D | ksm.rst | 60 deduplication factor at the expense of slower worst case for rmap
|
| /openbmc/linux/arch/arm/nwfpe/ |
| H A D | ChangeLog | 44 * I discovered several bugs. First and worst is that the kernel
|
| /openbmc/linux/Documentation/timers/ |
| H A D | timers-howto.rst | 94 worst case, fire an interrupt for your upper bound.
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-platform-dptf | 52 (RO) Shows the rest (outside of SoC) of worst-case platform power.
|
| /openbmc/u-boot/doc/ |
| H A D | README.autoboot | 42 dies or loses its connection (modems can disconnect at the worst
|
| /openbmc/openbmc/poky/meta/conf/distro/include/ |
| H A D | cve-extra-exclusions.inc | 72 The issue is of low impact, at worst sitting in an infinite loop rather than exploitable."
|
| /openbmc/linux/Documentation/admin-guide/device-mapper/ |
| H A D | log-writes.rst | 26 simulate the worst case scenario with regard to power failures. Consider the
|
| /openbmc/linux/Documentation/devicetree/bindings/display/panel/ |
| H A D | panel-edp.yaml | 29 list eDP panels. We solve that here with two tricks. The "worst case"
|
| /openbmc/linux/Documentation/arch/arm64/ |
| H A D | memory.rst | 142 the "worst" case.
|
| /openbmc/linux/Documentation/security/ |
| H A D | self-protection.rst | 13 In the worst-case scenario, we assume an unprivileged local attacker
16 but with systems in place that defend against the worst case we'll
|
| /openbmc/linux/Documentation/locking/ |
| H A D | pi-futex.rst | 25 determinism and well-bound latencies. Even in the worst-case, PI will
|
| /openbmc/linux/Documentation/powerpc/ |
| H A D | eeh-pci-error-recovery.rst | 97 reinitialization of the device driver. In a worst-case scenario,
105 kernel/device driver should assume the worst-case scenario, that the
|