taking (full) in projects: linux - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:taking (Results 1 – 25 of 805) sorted by relevance

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

/linux/arch/powerpc/include/asm/
H A D	dbell.h	`43 /* sync after taking message interrupt / 46 / sync is not required when taking messages from the same core / in ppc_msgsync() 73 / sync after taking message interrupt */`
H A D	pte-walk.h	`37 * physical address, without taking locks. This can be used in real-mode.`
/linux/Documentation/ABI/testing/
H A D	sysfs-class-bdi	`68 situations where we want to avoid one device taking all or 82 one device taking all or most of the write-back cache. For example 109 situations where we want to avoid one device taking all or`
/linux/fs/xfs/
H A D	xfs_hooks.h	`16 * code patching to eliminate the overhead of taking the rwsem in 21 * Note: Patching the kernel code requires taking the cpu hotplug lock. Other`
/linux/tools/perf/pmu-events/arch/x86/jaketown/
H A D	uncore-interconnect.json	532 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits80b/time. … 542 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits80b/time. … 552 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits80b/time. … 562 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits80b/time. … 572 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits80b/time. … 582 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits80b/time. … 592 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits80b/time. … 602 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits80b/time. … 612 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits80b/time. … 622 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits80b/time. … [all …]
/linux/drivers/macintosh/
H A D	windfarm_smu_sensors.c	`102 /* Ok, we have to scale & adjust, taking units into account / in smu_cputemp_get() 124 / Ok, we have to scale & adjust, taking units into account / in smu_cpuamp_get() 145 / Ok, we have to scale & adjust, taking units into account / in smu_cpuvolt_get() 166 / Ok, we have to scale & adjust, taking units into account */ in smu_slotspow_get()`
/linux/kernel/bpf/
H A D	reuseport_array.c	`117 * Hence, due to the above, taking "reuseport_lock" is not in reuseport_array_free() 132 * no one is reading it without taking the in reuseport_array_free() 269 /* Quick checks before taking reuseport_lock */ in bpf_fd_reuseport_array_update_elem()`
/linux/arch/x86/kvm/vmx/
H A D	posted_intr.c	`31 * CPU. IRQs must be disabled when taking this lock, otherwise deadlock will 96 * In addition to taking the wakeup lock for the regular/IRQ in vmx_vcpu_pi_load() 99 * this is taking the lock of the previous CPU, i.e. can race in vmx_vcpu_pi_load()`
/linux/drivers/misc/lkdtm/
H A D	cfi.c	`10 /* Function taking one argument, without a return value. / 16 / Function taking one argument, returning int. */`
/linux/Documentation/locking/
H A D	rt-mutex-design.rst	`417 Taking of a mutex (The walk through) 421 taking a mutex. 423 The first thing that is tried is the fast taking of the mutex. This is 424 done when we have CMPXCHG enabled (otherwise the fast taking automatically 518 CMPXCHG. Since the taking of a mutex on contention always sets the`
/linux/include/linux/
H A D	rational.h	`9 * pll configuration taking into account restricted register size`
H A D	call_once.h	`42 * efficiency the * function avoids taking it after the first call.`
/linux/sound/aoa/soundbus/i2sbus/
H A D	interface.h	`81 * It is derived by taking only every 'divisor' tick of the clock. 109 * derived from the MClk above by taking only every 'divisor' tick`
/linux/tools/testing/selftests/bpf/progs/
H A D	btf_dump_test_case_syntax.c	80 * - `fn_ptr2_t`: function, taking anonymous struct as a first arg and pointer 98 * - fn_ptr_arr2_t: array of const pointers to a function taking no arguments
/linux/Documentation/process/
H A D	management-style.rst	`223 best way of taking the blame: do it for someone else. You'll feel good 224 for taking the fall, they'll feel good about not getting blamed, and the 235 Taking the blame is also why you get to be manager in the first place.`
/linux/arch/sh/lib/
H A D	delay.c	`16 * normally taking two cycles each loop, as with all in __delay()`
/linux/Documentation/driver-api/tty/
H A D	tty_buffer.rst	`9 Here, we document functions for taking care of tty buffer and their flipping.`
/linux/arch/arm/kernel/
H A D	fiqasm.S	`21 * Taking an interrupt in FIQ mode is death, so both these functions`
/linux/Documentation/firmware-guide/acpi/
H A D	osi.rst	`30 Experience shows that taking untested paths through the BIOS 143 catastrophic failure resulting from the BIOS taking paths that`
/linux/include/linux/surface_aggregator/
H A D	controller.h	`380 * @spec, with the request taking an argument of type @atype and having no 421 * @spec, with the request taking no argument but having a return value of 481 * with the request taking an argument of type @atype and having a return value 581 * @spec, with the request taking an argument of type @atype and having no 624 * @spec, with the request taking no argument but having a return value of 686 * with the request taking an argument of type @atype and having a return value`
/linux/arch/sparc/include/asm/
H A D	machines.h	`3 * machines.h: Defines for taking apart the machine type value in the`
/linux/tools/testing/selftests/powerpc/copyloops/asm/
H A D	ppc_asm.h	`47 /* Default to taking the first of any alternative feature sections */`
/linux/Documentation/userspace-api/media/v4l/
H A D	dev-event.rst	`11 notified on certain conditions taking place on a device. This might`
/linux/net/can/j1939/
H A D	address-claim.c	`14 * - resolves NAME<=>SA taking into account the AC states of ECU's. 196 * Taking the above arguments into account, the 250 ms wait is in j1939_ac_process()`
/linux/tools/perf/pmu-events/arch/x86/ivytown/
H A D	uncore-interconnect.json	993 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits80b/time. … 1003 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits80b/time. … 1013 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits80b/time. … 1023 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits80b/time. … 1033 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits80b/time. … 1043 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits80b/time. … 1053 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits80b/time. … 1063 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits80b/time. … 1073 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits80b/time. … 1083 … of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits80b/time. … [all …]

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