/linux-6.12.1/Documentation/admin-guide/pm/ |
D | cpuidle.rst | 1 .. SPDX-License-Identifier: GPL-2.0 8 CPU Idle Time Management 27 CPU idle time management is an energy-efficiency feature concerned about using 31 ------------ 33 CPU idle time management operates on CPUs as seen by the *CPU scheduler* (that 37 software as individual single-core processors. In other words, a CPU is an 38 entity which appears to be fetching instructions that belong to one sequence 42 First, if the whole processor can only follow one sequence of instructions (one 43 program) at a time, it is a CPU. In that case, if the hardware is asked to 46 Second, if the processor is multi-core, each core in it is able to follow at [all …]
|
/linux-6.12.1/tools/perf/pmu-events/arch/x86/jaketown/ |
D | uncore-interconnect.json | 164 "BriefDescription": "BL Ingress Occupancy - DRS", 189 "BriefDescription": "BL Ingress Occupancy - NCB", 214 "BriefDescription": "BL Ingress Occupancy - NCS", 256 …ddition to the source queue. Note the special filtering equation. We do OR-reduction on the requ… 266 …ddition to the source queue. Note the special filtering equation. We do OR-reduction on the requ… 276 …ddition to the source queue. Note the special filtering equation. We do OR-reduction on the requ… 331 …er of cycles when there are pending write ACK's in the switch but the switch->IRP pipeline is not … 353 "BriefDescription": "Direct 2 Core Spawning; Spawn Failure - Egress Credits", 363 "BriefDescription": "Direct 2 Core Spawning; Spawn Failure - Egress and RBT", 373 "BriefDescription": "Direct 2 Core Spawning; Spawn Failure - RBT Not Set", [all …]
|
D | uncore-memory.json | 8 …page on the DRAM devices so that it can be read or written to with a CAS. One can calculate the n… 12 … "BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; All DRAM WR_CAS (w/ and w/out auto-pre)", 30 … "BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; All DRAM RD_CAS (w/ and w/out auto-pre)", 57 …"BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; DRAM WR_CAS (w/ and w/out auto-pre) in Read… 66 …"BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; DRAM WR_CAS (w/ and w/out auto-pre) in Writ… 79 "PublicDescription": "Uncore Fixed Counter - uclks", 117 …ounter is only useful with ECC DRAM devices. This count will increment one time for each correcti… 126 …ected by a filter) on the given channel. Major modea are channel-wide, and not a per-rank (or di… 136 …ected by a filter) on the given channel. Major modea are channel-wide, and not a per-rank (or di… 146 …ected by a filter) on the given channel. Major modea are channel-wide, and not a per-rank (or di… [all …]
|
/linux-6.12.1/Documentation/ABI/testing/ |
D | debugfs-scmi-raw | 7 in little-endian binary format to have it sent to the configured 11 Each write to the entry causes one command request to be built 12 and sent while the replies are read back one message at time 22 in little-endian binary format to have it sent to the configured 29 Each write to the entry causes one command request to be built 30 and sent while the replies are read back one message at time 38 Description: SCMI Raw message errors facility; any kind of timed-out or 41 Each read gives back one message at time (receiving an EOF at 52 Each read gives back one message at time (receiving an EOF at 65 different test-run. [all …]
|
/linux-6.12.1/Documentation/driver-api/ |
D | ptp.rst | 1 .. SPDX-License-Identifier: GPL-2.0 18 - Set time 19 - Get time 20 - Shift the clock by a given offset atomically 21 - Adjust clock frequency 24 - Time stamp external events 25 - Period output signals configurable from user space 26 - Low Pass Filter (LPF) access from user space 27 - Synchronization of the Linux system time via the PPS subsystem 36 driver of asynchronous events (alarms and external time stamps) via [all …]
|
/linux-6.12.1/Documentation/admin-guide/ |
D | rtc.rst | 2 Real Time Clock (RTC) Drivers for Linux 5 When Linux developers talk about a "Real Time Clock", they usually mean 6 something that tracks wall clock time and is battery backed so that it 8 the local time zone or daylight savings time -- unless they dual boot 9 with MS-Windows -- but will instead be set to Coordinated Universal Time 10 (UTC, formerly "Greenwich Mean Time"). 12 The newest non-PC hardware tends to just count seconds, like the time(2) 13 system call reports, but RTCs also very commonly represent time using 14 the Gregorian calendar and 24 hour time, as reported by gmtime(3). 16 Linux has two largely-compatible userspace RTC API families you may [all …]
|
/linux-6.12.1/drivers/cpuidle/governors/ |
D | teo.c | 1 // SPDX-License-Identifier: GPL-2.0 5 * Copyright (C) 2018 - 2021 Intel Corporation 10 * DOC: teo-description 17 * idle state with target residency within the (known) time till the closest 22 * Of course, non-timer wakeup sources are more important in some use cases 23 * which can be covered by taking a few most recent idle time intervals of the 45 * They are updated every time before selecting an idle state for the given CPU 46 * in accordance with what happened last time. 50 * same bin (that is, the CPU appears to wake up "on time" relative to the sleep 54 * shallower than the one whose bin is fallen into by the sleep length (these [all …]
|
/linux-6.12.1/drivers/net/wireless/intel/iwlwifi/fw/api/ |
D | binding.h | 1 /* SPDX-License-Identifier: GPL-2.0 OR BSD-3-Clause */ 3 * Copyright (C) 2012-2014, 2020, 2022, 2024 Intel Corporation 4 * Copyright (C) 2013-2015 Intel Mobile Communications GmbH 5 * Copyright (C) 2016-2017 Intel Deutschland GmbH 17 * struct iwl_binding_cmd_v1 - configuring bindings 37 * struct iwl_binding_cmd - configuring bindings 66 * struct iwl_time_quota_data_v1 - configuration of time quota per binding 69 * @quota: absolute time quota in TU. The scheduler will try to divide the 70 * remainig quota (after Time Events) according to this quota. 80 * struct iwl_time_quota_cmd_v1 - configuration of time quota between bindings [all …]
|
D | dbg-tlv.h | 1 /* SPDX-License-Identifier: GPL-2.0 OR BSD-3-Clause */ 3 * Copyright (C) 2018-2024 Intel Corporation 34 * struct iwl_fw_ini_header - Common Header for all ini debug TLV's structures 37 * @domain: domain of the TLV. One of &enum iwl_fw_ini_dbg_domain 46 * struct iwl_fw_ini_addr_size - Base address and size that defines 49 * @addr: the base address (fixed size - 4 bytes) 58 * struct iwl_fw_ini_region_dev_addr_range - Configuration to read 62 * The addrs[] array will be treated as an array of &iwl_fw_ini_addr_size - 70 * struct iwl_fw_ini_region_dev_addr - Configuration to read device addresses 81 * struct iwl_fw_ini_region_fifos - Configuration to read Tx/Rx fifos [all …]
|
/linux-6.12.1/Documentation/leds/ |
D | ledtrig-transient.rst | 6 a one shot timer. The current support allows for setting two timers, one for 8 to be off. The delay_on value specifies the time period an LED should stay 11 gets deactivated. There is no provision for one time activation to implement 15 Without one shot timer interface, user space can still use timer trigger to 20 Transient trigger addresses the need for one shot timer activation. The 36 that are active at the time driver gets suspended, continue to run, without 56 non-transient state. When driver gets suspended, irrespective of the transient 71 - duration allows setting timer value in msecs. The initial value is 0. 72 - activate allows activating and deactivating the timer specified by 75 - state allows user to specify a transient state to be held for the specified [all …]
|
/linux-6.12.1/Documentation/driver-api/usb/ |
D | usb.rst | 1 .. _usb-hostside-api: 4 The Linux-USB Host Side API 18 That master/slave asymmetry was designed-in for a number of reasons, one 22 distributed auto-configuration since the pre-designated master node 37 USB Host-Side API Model 40 Host-side drivers for USB devices talk to the "usbcore" APIs. There are 41 two. One is intended for *general-purpose* drivers (exposed through 49 - USB supports four kinds of data transfers (control, bulk, interrupt, 54 - The device description model includes one or more "configurations" 55 per device, only one of which is active at a time. Devices are supposed [all …]
|
/linux-6.12.1/include/xen/interface/ |
D | vcpu.h | 1 /* SPDX-License-Identifier: MIT */ 18 * @extra_args == Operation-specific extra arguments (NULL if none). 23 * newly-initialised VCPU will not run until it is brought up by VCPUOP_up. 37 * Bring down a VCPU (i.e., make it non-runnable). 41 * idea to ensure that the VCPU has entered a non-critical loop before 56 * Return information about the state and running time of a VCPU. 63 /* When was current state entered (system time, ns)? */ 72 * Time spent in each RUNSTATE_* (ns). The sum of these times is 73 * guaranteed not to drift from system time. 75 uint64_t time[4]; member [all …]
|
/linux-6.12.1/Documentation/timers/ |
D | no_hz.rst | 2 NO_HZ: Reducing Scheduling-Clock Ticks 7 reduce the number of scheduling-clock interrupts, thereby improving energy 9 some types of computationally intensive high-performance computing (HPC) 10 applications and for real-time applications. 12 There are three main ways of managing scheduling-clock interrupts 13 (also known as "scheduling-clock ticks" or simply "ticks"): 15 1. Never omit scheduling-clock ticks (CONFIG_HZ_PERIODIC=y or 16 CONFIG_NO_HZ=n for older kernels). You normally will -not- 19 2. Omit scheduling-clock ticks on idle CPUs (CONFIG_NO_HZ_IDLE=y or 23 3. Omit scheduling-clock ticks on CPUs that are either idle or that [all …]
|
/linux-6.12.1/Documentation/process/ |
D | stable-api-nonsense.rst | 8 Greg Kroah-Hartman <greg@kroah.com> 18 The kernel to userspace interface is the one that application programs use, 19 the syscall interface. That interface is **very** stable over time, and 22 That interface is the one that users and application programmers can count 27 ----------------- 38 ----- 41 to worry about the in-kernel interfaces changing. For the majority of 59 ----------------------- 64 - Depending on the version of the C compiler you use, different kernel 71 - Depending on what kernel build options you select, a wide range of [all …]
|
D | 6.Followthrough.rst | 8 patches. One of the biggest mistakes that even experienced kernel 23 ---------------------- 31 - If you have explained your patch well, reviewers will understand its 35 Many of the changes you may be asked to make - from coding style tweaks 36 to substantial rewrites - come from the understanding that Linux will 39 - Code review is hard work, and it is a relatively thankless occupation; 47 - Similarly, code reviewers are not trying to promote their employers' 54 - Be prepared for seemingly silly requests for coding style changes 56 the kernel. One job the maintainers do is to keep things looking 59 kernel feature ready for next time. [all …]
|
/linux-6.12.1/Documentation/driver-api/pm/ |
D | cpuidle.rst | 1 .. SPDX-License-Identifier: GPL-2.0 5 CPU Idle Time Management 13 CPU Idle Time Management Subsystem 16 Every time one of the logical CPUs in the system (the entities that appear to 26 situation in principle, so it may be necessary to find the most suitable one 28 particular idle state. That is the role of the CPU idle time management 40 CPU Idle Time Governors 43 A CPU idle time (``CPUIdle``) governor is a bundle of policy code invoked when 44 one of the logical CPUs in the system turns out to be idle. Its role is to 61 only one in the list (that is, the list was empty before) or the value of its [all …]
|
/linux-6.12.1/Documentation/filesystems/ |
D | quota.rst | 1 .. SPDX-License-Identifier: GPL-2.0 10 of used inodes there are actually two limits. The first one is called softlimit 11 and the second one hardlimit. A user can never exceed a hardlimit for any 13 softlimit but only for limited period of time. This period is called "grace 14 period" or "grace time". When grace time is over, user is not able to allocate 17 Quota limits (and amount of grace time) are set independently for each 20 For more details about quota design, see the documentation in quota-tools package 25 When user exceeds a softlimit, runs out of grace time or reaches hardlimit, 40 Currently, the interface supports only one message type QUOTA_NL_C_WARNING. 46 - type of quota being exceeded (one of USRQUOTA, GRPQUOTA) [all …]
|
/linux-6.12.1/Documentation/accounting/ |
D | psi.rst | 4 PSI - Pressure Stall Information 14 either play it safe and under-utilize their hardware resources, or 19 such resource crunches and the time impact it has on complex workloads 23 scarcity aids users in sizing workloads to hardware--or provisioning 38 respective file in /proc/pressure/ -- cpu, memory, and io. 45 The "some" line indicates the share of time in which at least some 48 The "full" line indicates the share of time in which all non-idle 51 extended time in this state is considered to be thrashing. This has 54 still doing productive work. As such, time spent in this subset of the 62 as well as medium and long term trends. The total absolute stall time [all …]
|
/linux-6.12.1/block/ |
D | bfq-wf2q.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later 3 * Hierarchical Budget Worst-case Fair Weighted Fair Queueing 4 * (B-WF2Q+): hierarchical scheduling algorithm by which the BFQ I/O 9 #include "bfq-iosched.h" 12 * bfq_gt - compare two timestamps. 20 return (s64)(a - b) > 0; in bfq_gt() 25 struct rb_node *node = tree->rb_node; in bfq_root_active_entity() 34 return bfqq ? bfqq->ioprio_class - 1 : in bfq_class_idx() 35 BFQ_DEFAULT_GRP_CLASS - 1; in bfq_class_idx() 40 return bfqd->busy_queues[0] + bfqd->busy_queues[1] + in bfq_tot_busy_queues() [all …]
|
D | bfq-iosched.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */ 12 #include "blk-cgroup-rwstat.h" 29 * Soft real-time applications are extremely more latency sensitive 30 * than interactive ones. Over-raise the weight of the former to 38 * per-actuator data. The current value is hopefully a good upper 46 * struct bfq_service_tree - per ioprio_class service tree. 48 * Each service tree represents a B-WF2Q+ scheduler on its own. Each 64 /* scheduler virtual time */ 71 * struct bfq_sched_data - multi-class scheduler. 81 * queue requests are served according to B-WF2Q+. [all …]
|
/linux-6.12.1/include/linux/can/ |
D | bittiming.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */ 2 /* Copyright (c) 2020 Pengutronix, Marc Kleine-Budde <kernel@pengutronix.de> 15 #define CAN_BITRATE_UNKNOWN (-1U) 21 * struct can_tdc - CAN FD Transmission Delay Compensation parameters 27 * To solve this issue, ISO 11898-1 introduces in section 11.3.3 29 * equal to the distance from the start of the bit time on the TX pin 34 * -+----------- one bit ----------+-- TX pin 35 * |<--- Sample Point --->| 37 * --+----------- one bit ----------+-- RX pin 38 * |<-------- TDCV -------->| [all …]
|
/linux-6.12.1/Documentation/networking/ |
D | timestamping.rst | 1 .. SPDX-License-Identifier: GPL-2.0 15 monotonic) system time. Reports the timestamp via recvmsg() in a 43 ------------------------------------------------------------- 59 ------------------------------------------------------------------- 72 ---------------------------------------------------------------------- 96 calls, one to enable timestamp generation and one to disable it. 123 difference between this timestamp and one taken at 138 over-report measurement, because the timestamp is generated when all 181 is derived from a per-socket u32 counter (that wraps). For datagram 186 The counter starts at zero. It is initialized the first time that [all …]
|
/linux-6.12.1/tools/power/cpupower/man/ |
D | cpupower-monitor.1 | 1 .TH CPUPOWER\-MONITOR "1" "22/02/2011" "" "cpupower Manual" 3 cpupower\-monitor \- Report processor frequency and idle statistics 7 .RB "\-l" 10 .RB [ -c ] [ "\-m <mon1>," [ "<mon2>,..." ] ] 11 .RB [ "\-i seconds" ] 14 .RB [ -c ][ "\-m <mon1>," [ "<mon2>,..." ] ] 18 \fBcpupower-monitor \fP reports processor topology, frequency and idle power 22 \fBcpupower-monitor \fP implements independent processor sleep state and 24 directly reading out hardware registers. Use \-l to get an overview which are 29 \-l [all …]
|
/linux-6.12.1/drivers/net/dsa/sja1105/ |
D | sja1105_tas.c | 1 // SPDX-License-Identifier: GPL-2.0 10 #define SJA1105_GATE_MASK GENMASK_ULL(SJA1105_NUM_TC - 1, 0) 19 struct sja1105_tas_data *tas_data = &priv->tas_data; in sja1105_tas_set_runtime_params() 20 struct sja1105_gating_config *gating_cfg = &tas_data->gating_cfg; in sja1105_tas_set_runtime_params() 21 struct dsa_switch *ds = priv->ds; in sja1105_tas_set_runtime_params() 28 tas_data->enabled = false; in sja1105_tas_set_runtime_params() 30 for (port = 0; port < ds->num_ports; port++) { in sja1105_tas_set_runtime_params() 33 offload = tas_data->offload[port]; in sja1105_tas_set_runtime_params() 37 tas_data->enabled = true; in sja1105_tas_set_runtime_params() 39 if (max_cycle_time < offload->cycle_time) in sja1105_tas_set_runtime_params() [all …]
|
/linux-6.12.1/drivers/md/ |
D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only 20 # after relevant mdadm enhancements - to make "names=yes" 21 # the default - are widely available. 24 This driver lets you combine several hard disk partitions into one 25 logical block device. This can be used to simply append one 26 partition to another one or to combine several redundant hard disks 34 Software RAID mini-HOWTO, available from 49 a several-second delay in the boot time due to various 65 tristate "RAID-0 (striping) mode" 69 use the so-called raid0 mode, i.e. it will combine the hard disk [all …]
|