generally (full) in projects: Linux-v6.1

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:generally (Results 1 – 25 of 811) sorted by relevance

12 3 4 5 6 7 8 9 10 >>...33

/Linux-v6.1/tools/perf/pmu-events/arch/x86/ivytown/
D	uncore-interconnect.json	134 …he BGF and into the Egress. This is a latency optimization, and should generally be the common ca… 305 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 315 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 326 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 337 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 348 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 359 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 370 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 381 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 392 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… [all …]
D	uncore-other.json	28 …p but have not yet returned their data to the uncore. These writes are generally queued up in the… 38 …p but have not yet returned their data to the uncore. These writes are generally queued up in the… 350 …/freeze delays. However, because the R2PCIe is close to the Ubox, they generally should not diver… 729 …is used is dependent on the system programming. Thereofore, one should generally set both the UP … 739 …is used is dependent on the system programming. Thereofore, one should generally set both the UP … 749 …is used is dependent on the system programming. Thereofore, one should generally set both the UP … 948 …eeze delays. However, because the QPI Agent is close to the Ubox, they generally should not diver… 1607 …is used is dependent on the system programming. Thereofore, one should generally set both the UP … 1617 …is used is dependent on the system programming. Thereofore, one should generally set both the UP … 1627 …is used is dependent on the system programming. Thereofore, one should generally set both the UP … [all …]
/Linux-v6.1/Documentation/driver-api/media/
D	camera-sensor.rst	`15 divisors. The clock tree is generally configured by the driver based on a few 17 and the link frequency. The two parameters generally are obtained from system 64 Register list based drivers generally, instead of able to configure the device 115 level interface natively, generally use the concept of frame interval (or frame`
/Linux-v6.1/Documentation/power/
D	suspend-and-interrupts.rst	`12 Device interrupt request lines (IRQs) are generally disabled during system 61 System wakeup interrupts generally need to be configured to wake up the system 72 After wakeup, it generally is better to disable that input to prevent the 128 interrupt source and an IRQF_NO_SUSPEND interrupt source does not generally`
D	freezing-of-tasks.rst	`36 kernel/freezer.c & include/linux/freezer.h). User space processes are generally 104 Generally speaking, there is a couple of reasons to use the freezing of tasks: 123 devices are deactivated, because we generally need them for swapping out. 206 tasks, since it generally exists anyway.`
/Linux-v6.1/tools/perf/pmu-events/arch/x86/jaketown/
D	uncore-interconnect.json	94 …he BGF and into the Egress. This is a latency optimization, and should generally be the common ca… 199 …ription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is tr… 381 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … 391 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … 401 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … 411 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … 421 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … 431 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … 441 …"PublicDescription": "Number of allocations into the QPI Rx Flit Buffer. Generally, when data is … 450 …on": "Accumulates the number of elements in the QPI RxQ in each cycle. Generally, when data is tr… [all …]
D	uncore-other.json	28 …p but have not yet returned their data to the uncore. These writes are generally queued up in the… 38 …p but have not yet returned their data to the uncore. These writes are generally queued up in the… 340 …/freeze delays. However, because the R2PCIe is close to the Ubox, they generally should not diver… 559 …is used is dependent on the system programming. Thereofore, one should generally set both the UP … 691 …eeze delays. However, because the QPI Agent is close to the Ubox, they generally should not diver… 910 …is used is dependent on the system programming. Thereofore, one should generally set both the UP … 1104 …iled to acquire either a VNA or VN0 credit and is delayed. This should generally be a rare situat… 1114 …iled to acquire either a VNA or VN0 credit and is delayed. This should generally be a rare situat… 1124 …iled to acquire either a VNA or VN0 credit and is delayed. This should generally be a rare situat… 1134 …iled to acquire either a VNA or VN0 credit and is delayed. This should generally be a rare situat… [all …]
/Linux-v6.1/Documentation/mm/
D	active_mm.rst	`76 should generally just do 81 we have a user context", and is generally done by the page fault handler`
/Linux-v6.1/Documentation/admin-guide/pm/
D	cpufreq.rst	42 the utilization of the system generally changes over time, that has to be done 160 scheduler tick or generally whenever the CPU utilization may change (from the 215 and their behavior generally does not depend on what scaling driver is in use 388 generally is regarded as a part of the CPU scheduler, so it can access the 430 This governor generally is regarded as a replacement for the older `ondemand`_ 460 It generally selects CPU frequencies proportional to the estimated load, so that 644 The frequency boost mechanism is generally intended to help to achieve optimum 655 conditions. Generally, the processor's energy consumption increases
D	intel_pstate.rst	81 names of some of those governors. Moreover, confusingly enough, they generally 182 registers of the CPU. It generally selects P-states proportional to the 266 In turn, the P-states below the turbo threshold generally are sustainable. In 273 but the maximum P-state that can be set for them generally depends on the number 291 generally causes turbo P-states to be set more often when ``intel_pstate`` is 320 Generally, ways to obtain that information are specific to the processor model 455 as the current scaling driver and it generally depends on the driver's 707 diagnostics. One of them is the ``cpu_frequency`` trace event generally used 713 their output (if the kernel is generally configured to support event tracing)::
D	cpuidle.rst	19 Modern processors are generally able to enter states in which the execution of 24 generally allows power drawn by the processor to be reduced and, in consequence, 40 physically. Generally, three different cases can be consider here. 153 (in particular, before the closest timer triggers) and it generally is not known 255 generally regarded as more energy-efficient than the systems running kernels in 487 hierarchy of units in the processor, and it generally is hard to obtain idle 492 The number in the :file:`time` file generally may be greater than the total time 506 Generally, an interrupt received when trying to enter an idle state causes the
/Linux-v6.1/Documentation/i2c/busses/
D	i2c-ali15x3.rst	`61 - Gigabyte GA-5AX (Generally doesn't work because the BIOS doesn't 121 SMBus. Therefore the SMBus hangs can generally be avoided`
/Linux-v6.1/Documentation/virt/hyperv/
D	overview.rst	`17 generally the same on both architectures unless noted otherwise. 25 returns control to the guest. This behavior is generally invisible 64 on sharing memory. Such sharing is generally accomplished as`
/Linux-v6.1/Documentation/process/
D	volatile-considered-harmful.rst	`71 waiting is generally an anti-social act to begin with. 104 Patches to remove volatile variables are generally welcome - as long as`
/Linux-v6.1/drivers/thermal/ti-soc-thermal/
D	TODO	`9 generally:`
/Linux-v6.1/kernel/power/
D	Kconfig	`192 Hardware support is generally required for this functionality to work 297 Generally, if you don't have a battery in your machine, there isn't 315 Per-cpu workqueues are generally preferred because they show`
/Linux-v6.1/Documentation/driver-api/pm/
D	devices.rst	57 However, devices are not generally independent of each other (for 200 by the bus type (or generally subsystem) code using :c:func:`pm_runtime_allow()` 401 vectors, like PCI, generally need it; otherwise a driver might encounter 432 generally means undoing the actions of the ``suspend_noirq`` phase. If 445 of the resume methods. This generally involves undoing the actions of 449 state, so that it can perform normal I/O. This generally involves 654 been thawed. Generally speaking, the PM notifiers are suitable for performing 698 cases it generally is not possible to put devices into low-power states 820 the case generally depends on the state of the device before the given system 842 ``DPM_FLAG_MAY_SKIP_RESUME`` flag is necessary, but generally not sufficient,
/Linux-v6.1/arch/x86/include/uapi/asm/
D	posix_types_64.h	`6 * This file is generally used by user-level software, so you need to`
D	posix_types_x32.h	`10 * These types should generally match the ones used by the 64-bit kernel,`
D	posix_types_32.h	`6 * This file is generally used by user-level software, so you need to`
/Linux-v6.1/arch/alpha/include/uapi/asm/
D	posix_types.h	`6 * This file is generally used by user-level software, so you need to`
/Linux-v6.1/arch/powerpc/include/uapi/asm/
D	posix_types.h	`6 * This file is generally used by user-level software, so you need to`
/Linux-v6.1/arch/parisc/include/uapi/asm/
D	posix_types.h	`6 * This file is generally used by user-level software, so you need to`
/Linux-v6.1/arch/m68k/include/uapi/asm/
D	posix_types.h	`6 * This file is generally used by user-level software, so you need to`
/Linux-v6.1/kernel/rcu/
D	Makefile	`3 # and is generally not a function of system call inputs.`

12 3 4 5 6 7 8 9 10 >>...33