often (full) in projects: openbmc - OpenGrok search results

Searched full:often (Results 1 – 25 of 1328) sorted by relevance

/openbmc/linux/Documentation/maintainer/
H A D	rebasing-and-merging.rst	9 features; as is often the case with such tools, there are right and wrong 11 of rebasing and merging. Maintainers often get in trouble when they use 20 merging a little too often. 72 as the new base. The kernel is often in a relatively unstable state 85 patch series that has clearly been reparented, often to a random commit, 144 type of merge is often called a "back merge". Back merges can help to make 154 hide interactions with other trees that should not be happening (often) in 172 resolution - often better than the developers involved. 194 Often, though, dependency issues indicate that a change of approach is
/openbmc/linux/Documentation/ABI/testing/
H A D	sysfs-mce	`9 machine check (often with panic), corrected ones cause a 45 How often to poll for corrected machine check errors, in 48 (poll more often) on the polling interval. When the poller 50 (poll less often) on the polling interval. The check_interval`
/openbmc/linux/Documentation/sound/designs/
H A D	powersave.rst	`35 state. Also, it often takes certain time to wake up from the 36 power-down to the active state. These are often hardly to fix, so 43 Try to turn it off when you experience such a thing too often.`
/openbmc/u-boot/drivers/block/
H A D	Kconfig	`9 devices often have a partition table which allows the device to 26 devices often have a partition table which allows the device to 38 devices often have a partition table which allows the device to`
/openbmc/linux/Documentation/userspace-api/
H A D	sysfs-platform_profile.rst	`6 hardware related characteristics are often dynamically configurable. The 7 platform configuration is often automatically adjusted to the current 11 These auto platform adjustment mechanisms often can be configured with`
/openbmc/linux/tools/memory-model/Documentation/
H A D	simple.txt	`6 (LKMM) is quite complex, with subtle differences in code often having 14 will often have special requirements or idioms. For example, developers 15 of MMIO-based device drivers will often need to use mb(), rmb(), and 75 being completely single-threaded, it is often possible to use library 194 Reading code using these primitives is often also quite helpful. 200 When using locking, there often comes a time when it is necessary 230 controlling how often RCU scans for idle CPUs.`
/openbmc/linux/Documentation/admin-guide/
H A D	quickly-build-trimmed-linux.rst	103 * Install all software required to build a Linux kernel. Often you will need: 171 * In case you want to apply a kernel patch, do so now. Often a command like 208 Using this make target is fine for everybody else, too -- but you often can 223 it is often negligible if such features are missing. But you should keep that 266 Often all left for you to do afterwards is a ``reboot``, as many commodity 473 safe side, so often you will need less. 553 People new to compiling Linux often assume downloading an archive via the 557 be the case, but in practice it often will turn out to be a wrong assumption. 559 That's because when reporting or debugging an issue developers will often ask to 570 A shallow clone therefore is often the better choice. If you nevertheless want [all …]
H A D	reporting-issues.rst	72 will often be needed anyway to hunt down and fix issues. 282 will often be needed anyway to hunt down and fix issues.* 287 easily happen when it comes to the kernel and often leads to frustration on both 291 kernel.org: these kernels from these vendors are often ancient from the point of 292 Linux development or heavily modified, often both. 301 upstream or forward the report there. In practice that often does not work out 312 example often holds true for the mainline kernels shipped by Debian GNU/Linux 315 its only slightly modified; that for example is often the case for Arch Linux, 323 those often get rejected or ignored, so consider yourself warned. But it's still 336 Reporting an issue that someone else already brought forward is often a waste of [all …]
H A D	reporting-regressions.rst	139 this, but often it's required. 145 own. But for them that's often impossible to do with reasonable effort, as quite 148 system's configuration, or application. That's why in the end it's often up to 257 affected area and often Linus Torvalds himself try very hard to fix security 267 Sadly these things happen, but luckily not very often; if they occur, expert 279 5.15-rc1. All these changes often can simply be reverted and the regression thus 289 It is, but often it's hard to fix such regressions due to the aspects outlined 318 The staging developers nevertheless often adhere to the "no regressions" rule, 320 deal with (often negligible) regressions when a WiFi driver from the staging 332 interfaces often abused by malware, which at the same time are required to run a
/openbmc/linux/tools/perf/pmu-events/arch/x86/haswell/
H A D	hsw-metrics.json	73 …"BriefDescription": "This metric estimates how often memory load accesses were aliased by precedin… 78 …often memory load accesses were aliased by preceding stores (in program order) with a 4K address o… 191 …"BriefDescription": "This metric estimates how often the CPU was stalled on accesses to external m… 197 …"PublicDescription": "This metric estimates how often the CPU was stalled on accesses to external … 237 …"BriefDescription": "This metric roughly estimates how often CPU was handling synchronizations due… 242 …"PublicDescription": "This metric roughly estimates how often CPU was handling synchronizations du… 246 …"BriefDescription": "This metric does a rough estimation of how often L1D Fill Buffer unavailabi… 252 …often L1D Fill Buffer unavailability limited additional L1D miss memory access requests to proceed… 622 …"BriefDescription": "This metric estimates how often the CPU was stalled without loads missing the… 627 …"PublicDescription": "This metric estimates how often the CPU was stalled without loads missing th… [all …]
/openbmc/linux/drivers/media/test-drivers/vidtv/
H A D	vidtv_mux.h	`37 * @pcr_period_usecs: How often we should send PCR packets. 38 * @si_period_usecs: How often we should send PSI packets. 150 * @pcr_period_usecs: How often we should send PCR packets. 151 * @si_period_usecs: How often we should send PSI packets.`
/openbmc/linux/tools/perf/pmu-events/arch/x86/ivytown/
H A D	ivt-metrics.json	73 …"BriefDescription": "This metric estimates how often memory load accesses were aliased by precedin… 78 …often memory load accesses were aliased by preceding stores (in program order) with a 4K address o… 191 …"BriefDescription": "This metric estimates how often the CPU was stalled on accesses to external m… 197 …"PublicDescription": "This metric estimates how often the CPU was stalled on accesses to external … 237 …"BriefDescription": "This metric roughly estimates how often CPU was handling synchronizations due… 242 …"PublicDescription": "This metric roughly estimates how often CPU was handling synchronizations du… 246 …"BriefDescription": "This metric does a rough estimation of how often L1D Fill Buffer unavailabi… 252 …often L1D Fill Buffer unavailability limited additional L1D miss memory access requests to proceed… 684 …"BriefDescription": "This metric estimates how often the CPU was stalled without loads missing the… 689 …"PublicDescription": "This metric estimates how often the CPU was stalled without loads missing th… [all …]
/openbmc/linux/Documentation/networking/devlink/
H A D	devlink-info.rst	`32 This is usually the serial number of the ASIC, also often available 50 This is usually the serial number of the board, often available in 71 These versions often only update after a reboot, sometimes device reset. 152 Overall firmware version, often representing the collection of`
/openbmc/linux/Documentation/admin-guide/aoe/
H A D	udev-install.sh	`7 # find udev.conf, often /etc/udev/udev.conf 22 # find the directory where udev rules are stored, often`
/openbmc/linux/tools/perf/pmu-events/arch/x86/ivybridge/
H A D	ivb-metrics.json	73 …"BriefDescription": "This metric estimates how often memory load accesses were aliased by precedin… 78 …often memory load accesses were aliased by preceding stores (in program order) with a 4K address o… 191 …"BriefDescription": "This metric estimates how often the CPU was stalled on accesses to external m… 197 …"PublicDescription": "This metric estimates how often the CPU was stalled on accesses to external … 237 …"BriefDescription": "This metric roughly estimates how often CPU was handling synchronizations due… 242 …"PublicDescription": "This metric roughly estimates how often CPU was handling synchronizations du… 246 …"BriefDescription": "This metric does a rough estimation of how often L1D Fill Buffer unavailabi… 252 …often L1D Fill Buffer unavailability limited additional L1D miss memory access requests to proceed… 683 …"BriefDescription": "This metric estimates how often the CPU was stalled without loads missing the… 688 …"PublicDescription": "This metric estimates how often the CPU was stalled without loads missing th… [all …]
/openbmc/linux/fs/efs/
H A D	file.c	`24 * i have no idea why this happens as often as it does in efs_get_block() 48 * i have no idea why this happens as often as it does in efs_bmap()`
/openbmc/linux/Documentation/process/
H A D	3.Early-stage.rst	`132 subsystem list, posting there is often preferable to posting on 181 posted by others. Beyond that, high-level designs often hide problems 207 considering whether the secrecy is really necessary; there is often no real 215 best option is often to hire an outside developer to review the plans under 222 This kind of review is often enough to avoid serious problems later on`
/openbmc/linux/tools/perf/pmu-events/arch/x86/sandybridge/
H A D	snb-metrics.json	134 …"BriefDescription": "This metric estimates how often the CPU was stalled on accesses to external m… 140 …"PublicDescription": "This metric estimates how often the CPU was stalled on accesses to external … 398 …"BriefDescription": "This metric estimates how often the CPU was stalled due to loads accesses to … 404 …"PublicDescription": "This metric estimates how often the CPU was stalled due to loads accesses to… 423 …cently optimized software running on Intel Core/Xeon products. While this often indicates efficien… 472 …ss some operation modes (like in Floating Point assists). These cases can often be avoided. Sample… 481 …all programs injected into the execution stream). Switching to the MS too often can negatively imp… 491 …ng contiguous instructions would manifest in this metric - such cases are often referred to as low… 501 …ocode Assists are categorized under Retiring. They often indicate suboptimal performance and can o… 505 …"BriefDescription": "This metric estimates how often CPU was stalled due to RFO store memory acce… [all …]
/openbmc/linux/tools/perf/pmu-events/arch/x86/jaketown/
H A D	jkt-metrics.json	134 …"BriefDescription": "This metric estimates how often the CPU was stalled on accesses to external m… 140 …"PublicDescription": "This metric estimates how often the CPU was stalled on accesses to external … 399 …"BriefDescription": "This metric estimates how often the CPU was stalled due to loads accesses to … 405 …"PublicDescription": "This metric estimates how often the CPU was stalled due to loads accesses to… 424 …cently optimized software running on Intel Core/Xeon products. While this often indicates efficien… 473 …ss some operation modes (like in Floating Point assists). These cases can often be avoided. Sample… 482 …all programs injected into the execution stream). Switching to the MS too often can negatively imp… 492 …ng contiguous instructions would manifest in this metric - such cases are often referred to as low… 502 …ocode Assists are categorized under Retiring. They often indicate suboptimal performance and can o… 506 …"BriefDescription": "This metric estimates how often CPU was stalled due to RFO store memory acce… [all …]
/openbmc/linux/tools/perf/pmu-events/arch/x86/haswellx/
H A D	hsx-metrics.json	275 …"BriefDescription": "This metric estimates how often memory load accesses were aliased by precedin… 280 …often memory load accesses were aliased by preceding stores (in program order) with a 4K address o… 393 …"BriefDescription": "This metric estimates how often the CPU was stalled on accesses to external m… 399 …"PublicDescription": "This metric estimates how often the CPU was stalled on accesses to external … 439 …"BriefDescription": "This metric roughly estimates how often CPU was handling synchronizations due… 444 …"PublicDescription": "This metric roughly estimates how often CPU was handling synchronizations du… 448 …"BriefDescription": "This metric does a rough estimation of how often L1D Fill Buffer unavailabi… 454 …often L1D Fill Buffer unavailability limited additional L1D miss memory access requests to proceed… 825 …"BriefDescription": "This metric estimates how often the CPU was stalled without loads missing the… 830 …"PublicDescription": "This metric estimates how often the CPU was stalled without loads missing th… [all …]
/openbmc/linux/Documentation/devicetree/bindings/hwmon/
H A D	ntc-thermistor.yaml	`13 vary in resistance in an often non-linear way in relation to temperature. 16 temperature is non-linear, software drivers most often need to use a look 19 When used in practice, a thermistor is often connected between ground, a`
/openbmc/linux/tools/perf/pmu-events/arch/x86/broadwell/
H A D	bdw-metrics.json	73 …"BriefDescription": "This metric estimates how often memory load accesses were aliased by precedin… 78 …often memory load accesses were aliased by preceding stores (in program order) with a 4K address o… 200 …"BriefDescription": "This metric estimates how often the CPU was stalled on accesses to external m… 206 …"PublicDescription": "This metric estimates how often the CPU was stalled on accesses to external … 246 …"BriefDescription": "This metric roughly estimates how often CPU was handling synchronizations due… 251 …"PublicDescription": "This metric roughly estimates how often CPU was handling synchronizations du… 255 …"BriefDescription": "This metric does a rough estimation of how often L1D Fill Buffer unavailabi… 261 …often L1D Fill Buffer unavailability limited additional L1D miss memory access requests to proceed… 787 …"BriefDescription": "This metric estimates how often the CPU was stalled without loads missing the… 792 …"PublicDescription": "This metric estimates how often the CPU was stalled without loads missing th… [all …]
/openbmc/linux/Documentation/userspace-api/media/v4l/
H A D	colorspaces.rst	`48 The Y value in the CIE XYZ colorspace corresponds to luminance. Often 113 in the CIE XYZ colorspace. Also note that Y'CbCr is often called YCbCr 147 colorspace standards correctly define all four, quite often the 149 standards for the missing pieces. The fact that colorspaces are often a`
/openbmc/linux/Documentation/driver-api/gpio/
H A D	legacy.rst	25 often have a few such pins to help with pin scarcity on SOCs; and there are 42 - Inputs can often be used as IRQ signals, often edge triggered but 62 is not the main issue; GPIOs are often used for the kind of board-specific 133 One of the next things to do with a GPIO, often in board setup code when 254 several hundred potential GPIOs, but often only a dozen are used on any 370 or free_irq(). They will often be stored into IRQ resources for platform 509 Most often a gpio_chip is part of an instance-specific structure with state 545 available, from arch_initcall() or earlier; they can often serve as IRQs. 551 function devices, FPGAs or CPLDs -- most often board-specific code handles 553 numbers to use with gpiochip_add(). Their numbers often start right after
/openbmc/linux/tools/perf/pmu-events/arch/x86/broadwellde/
H A D	bdwde-metrics.json	73 …"BriefDescription": "This metric estimates how often memory load accesses were aliased by precedin… 78 …often memory load accesses were aliased by preceding stores (in program order) with a 4K address o… 200 …"BriefDescription": "This metric estimates how often the CPU was stalled on accesses to external m… 206 …"PublicDescription": "This metric estimates how often the CPU was stalled on accesses to external … 246 …"BriefDescription": "This metric does a rough estimation of how often L1D Fill Buffer unavailabi… 252 …often L1D Fill Buffer unavailability limited additional L1D miss memory access requests to proceed… 766 …"BriefDescription": "This metric estimates how often the CPU was stalled without loads missing the… 771 …"PublicDescription": "This metric estimates how often the CPU was stalled without loads missing th… 775 …"BriefDescription": "This metric estimates how often the CPU was stalled due to L2 cache accesses … 780 …"PublicDescription": "This metric estimates how often the CPU was stalled due to L2 cache accesses… [all …]

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

Project(s)

Full Search
Definition
Symbol
File Path
History
Type