/openbmc/linux/Documentation/admin-guide/pm/ |
H A D | cpufreq.rst | 415 "IO-wait boosting". That happens when the :c:macro:`SCHED_CPUFREQ_IOWAIT` flag 613 If it is hardware-based (e.g. on x86), the decision to trigger the boosting is 617 whether or not to trigger boosting and when to do that. 630 trigger boosting (in the hardware-based case), or the software is allowed to 631 trigger boosting (in the software-based case). It does not mean that boosting 654 1. Boosting means overclocking the processor, although under controlled 664 boosting while the system is running may be useful then. 667 to be able to run tests with and without boosting, preferably without 671 the boosting functionality depends on the load of the whole package,
|
/openbmc/linux/Documentation/locking/ |
H A D | rt-mutex.rst | 22 boosting to the owner of the other rt_mutex it gets blocked on. The 23 priority boosting is immediately removed once the rt_mutex has been
|
H A D | futex-requeue-pi.rst | 8 boosting logic [see rt-mutex-design.rst] For the purposes of 51 previously mentioned PI-boosting algorithms.
|
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Control/Host/ |
H A D | TurboAllowed.interface.yaml | 2 Turbo mode is a setting to enable processor frequency boosting. This
|
/openbmc/linux/kernel/rcu/ |
H A D | Kconfig | 195 bool "Enable RCU priority boosting" 208 int "Milliseconds to delay boosting after RCU grace-period start" 214 a given grace period before priority-boosting preempted RCU
|
H A D | tree.h | 106 /* boosting is needed for this rcu_node */ 112 /* Used only for the priority-boosting */ 115 /* When to start boosting (jiffies). */ 121 /* boosting for this rcu_node structure. */ 262 /* 6) RCU priority boosting. */
|
H A D | tree_plugin.h | 69 pr_info("\tRCU priority boosting: priority %d delay %d ms.\n", in rcu_bootup_announce_oddness() 640 bool expboost; // Expedited GP in flight or possible boosting. in rcu_read_unlock_special() 1003 * If boosting, set rcuc kthreads to realtime priority. 1040 * Carry out RCU priority boosting on the task indicated by ->exp_tasks 1044 * Note that irqs must be enabled: boosting the task can block. 1060 * Recheck under the lock: all tasks in need of boosting in rcu_boost() 1091 * rnp->lock also resolves races between our priority boosting in rcu_boost() 1108 * Priority-boosting kthread, one per leaf rcu_node. 1143 * Check to see if it is time to start boosting RCU readers that are 1145 * kthread to start boosting them. If there is an expedited grace
|
H A D | tree_stall.h | 828 * is nothing that RCU priority boosting can do to help, so we shouldn't 829 * count this as an RCU priority boosting failure. A return of true says 830 * RCU priority boosting is to blame, and false says otherwise. If false 877 // Can't blame CPUs, so must blame RCU priority boosting. in rcu_check_boost_fail()
|
/openbmc/linux/drivers/gpu/drm/i915/gem/ |
H A D | i915_gem_wait.c | 42 * Prescan all fences for potential boosting before we begin waiting. in i915_gem_object_boost() 47 * request is currently executing and not worthy of boosting. But if in i915_gem_object_boost()
|
/openbmc/linux/drivers/cpuidle/ |
H A D | Kconfig | 31 focused on timer events and does not do any interactivity boosting.
|
/openbmc/openbmc/meta-security/dynamic-layers/meta-python/recipes-security/mfa/ |
H A D | python3-privacyidea_3.9.1.bb | 2 …b sites or web portals with a second factor during authentication. Thus boosting the security of y…
|
/openbmc/linux/drivers/gpu/drm/i915/gt/ |
H A D | intel_rps_types.h | 90 u8 boost_freq; /* Frequency to request when wait boosting */
|
/openbmc/linux/drivers/gpu/drm/panel/ |
H A D | panel-novatek-nt35510.c | 98 #define NT35510_P1_BT4CTR 0xB9 /* VGH boosting times/freq */ 192 * bits 4..6 in the upper nibble controls BTP, the boosting 213 * bits 4..5 in the upper nibble controls BTN, the boosting 233 * bits 4..5 in the upper nibble controls BTH, the boosting 252 * bits 4..5 in the upper nibble controls BTL, the boosting
|
/openbmc/linux/Documentation/admin-guide/ |
H A D | kernel-per-CPU-kthreads.rst | 304 the need for RCU priority boosting. This approach is feasible 309 boosting, for example, if you ensure frequent idle time on all
|
/openbmc/linux/Documentation/RCU/ |
H A D | torture.rst | 79 * "rtbf": The number of times that RCU priority boosting failed 84 priority boosting via the "test_boost" module parameter, this
|
/openbmc/qemu/include/hw/intc/ |
H A D | armv7m_nvic.h | 181 * and minus any PRIMASK/FAULTMASK/BASEPRI priority boosting.
|
/openbmc/linux/Documentation/gpu/rfc/ |
H A D | i915_scheduler.rst | 50 * Port i915 priority inheritance / boosting feature in DRM scheduler
|
/openbmc/linux/Documentation/devicetree/bindings/phy/ |
H A D | phy-stm32-usbphyc.yaml | 91 description: Current boosting in uA
|
/openbmc/linux/kernel/locking/ |
H A D | rwbase_rt.c | 38 * Implementing the one by one reader boosting/handover mechanism is a
|
/openbmc/linux/drivers/cpufreq/ |
H A D | Kconfig.x86 | 108 to disable the Core Performance Boosting feature of AMD CPUs. This
|
H A D | acpi-cpufreq.c | 140 pr_debug("CPU %*pbl: Core Boosting %s.\n", in set_boost() 544 * this cpu cannot block the remaining ones from boosting. in cpufreq_boost_down_prep()
|
/openbmc/linux/drivers/devfreq/ |
H A D | tegra30-devfreq.c | 245 * High freq + high boosting percent + large polling interval are in do_percent() 502 /* reset boosting on governor's restart */ in tegra_actmon_configure_device()
|
/openbmc/linux/drivers/clk/ti/ |
H A D | clkt_dpll.c | 97 pr_debug("rejecting n=%d due to Fint failure, boosting min_divider\n", in _dpll_test_fint()
|
/openbmc/linux/Documentation/ABI/testing/ |
H A D | sysfs-devices-system-cpu | 295 Description: Processor frequency boosting control 298 Boosting allows the CPU and the firmware to run at a frequency
|
/openbmc/linux/Documentation/scheduler/ |
H A D | sched-util-clamp.rst | 32 of the system. UCLAMP_MIN implies boosting a task, while UCLAMP_MAX implies 448 to restrict how much boosting tasks are allowed to acquire.
|