Searched refs:PI (Results 1 – 25 of 37) sorted by relevance
12
| /Linux-v4.19/Documentation/ |
| D | futex-requeue-pi.txt | 2 Futex Requeue PI
5 Requeueing of tasks from a non-PI futex to a PI futex requires
7 left without an owner if it has waiters; doing so would break the PI
11 "PI".
51 previously mentioned PI-boosting algorithms.
53 In order to support PI-aware pthread_condvar's, the kernel needs to
54 be able to requeue tasks to PI futexes. This support implies that
56 user space already holding the PI futex. The glibc implementation
81 The actual glibc implementation will likely test for PI and make the
83 calls for the PI cases. Similar changes are needed for
[all …]
|
| D | pi-futex.txt | 2 Lightweight PI-futexes
7 - in the user-space fastpath a PI-enabled futex involves no kernel work
8 (or any other PI complexity) at all. No registration, no extra kernel
14 - the in-kernel PI implementation is streamlined around the mutex
23 The short reply: user-space PI helps achieving/improving determinism for
25 determinism and well-bound latencies. Even in the worst-case, PI will
66 Currently (without PI), if a high-prio and a low-prio task shares a lock
78 As mentioned before, the userspace fastpath of PI-enabled pthread
94 own TID into the futex value], and attaches a 'PI state' structure to
95 the futex-queue. The pi_state includes an rt-mutex, which is a PI-aware,
[all …]
|
| D | 00-INDEX | 162 - info on requeueing of tasks from a non-PI futex to a PI futex
|
| /Linux-v4.19/arch/m68k/fpsp040/ |
| D | stan.S | 83 |--N*PI/2, -32 <= N <= 32, IN A LEADING TERM IN EXT. AND TRAILING
84 |--TERM IN SGL. NOTE THAT PI IS 64-BIT LONG, THUS N*PI/2 IS AT
181 cmpil #0x4004BC7E,%d0 | ...|X| < 15 PI?
187 |--THIS IS THE USUAL CASE, |X| <= 15 PI.
190 fmuld TWOBYPI,%fp1 | ...X*2/PI
193 leal PITBL+0x200,%a1 | ...TABLE OF N*PI/2, N = -32,...,32
292 |--IF |X| > 15PI, WE USE THE GENERAL ARGUMENT REDUCTION.
322 | ;create 2**16383*PI/2
327 | ;PI/2 at FP_SCR3
340 |--ON ENTRY, FP0 IS X, ON RETURN, FP0 IS X REM PI/2, |X| <= PI/4.
[all …]
|
| D | sacos.S | 48 PI: .long 0x40000000,0xC90FDAA2,0x2168C235,0x00000000 label
57 |--ACOS(X) = PI/2 FOR DENORMALIZED X
|
| D | ssin.S | 194 cmpil #0x4004BC7E,%d0 | ...|X| < 15 PI?
199 |--THIS IS THE USUAL CASE, |X| <= 15 PI.
202 fmuld TWOBYPI,%fp1 | ...X*2/PI
205 lea PITBL+0x200,%a1 | ...TABLE OF N*PI/2, N = -32,...,32
459 addil #0x00003FFF,%d2 | ...BIASED EXPO OF 2**L * (PI/2)
548 cmpil #0x4004BC7E,%d0 | ...|X| < 15 PI?
554 |--THIS IS THE USUAL CASE, |X| <= 15 PI.
557 fmuld TWOBYPI,%fp1 | ...X*2/PI
560 lea PITBL+0x200,%a1 | ...TABLE OF N*PI/2, N = -32,...,32
|
| D | do_func.S | 57 PPIBY2: .long 0x3FFF0000,0xC90FDAA2,0x2168C235 |+PI/2
58 MPIBY2: .long 0xbFFF0000,0xC90FDAA2,0x2168C235 |-PI/2
504 |**Returns +PI/2
510 |**Returns -PI/2
|
| D | sasin.S | 92 |--|X| = 1, ASIN(X) = +- PI/2.
|
| D | satan.S | 402 |--IF |X| > 2^(100), RETURN SIGN(X)*(PI/2 - TINY). OTHERWISE,
403 |--RETURN SIGN(X)*PI/2 + ATAN(-1/X).
|
| /Linux-v4.19/Documentation/locking/ |
| D | rt-mutex-design.txt | 16 inheritance (PI) algorithm that is used, as well as reasons for the
17 decisions that were made to implement PI in the manner that was done.
57 Priority Inheritance (PI)
61 for this document. Here we only discuss PI.
63 PI is where a process inherits the priority of another process if the other
76 the design that is used to implement PI.
78 PI chain - The PI chain is an ordered series of locks and processes that cause
84 PI and spin locks that are used in the PI code, from now on
85 the PI locks will be called a mutex.
88 referring to spin locks that are used to protect parts of the PI
[all …]
|
| D | rt-mutex.txt | 1 RT-mutex subsystem with PI support
4 RT-mutexes with priority inheritance are used to support PI-futexes,
7 about PI-futexes.]
|
| D | 00-INDEX | 12 - desc. of RT-mutex subsystem with PI (Priority Inheritance) support.
|
| /Linux-v4.19/drivers/scsi/pm8001/ |
| D | pm8001_defs.h | 100 #define PI (OB + PM8001_MAX_SPCV_OUTB_NUM) macro
101 #define USI_MAX_MEMCNT (PI + PM8001_MAX_SPCV_OUTB_NUM)
|
| D | pm8001_init.c | 303 pm8001_ha->memoryMap.region[PI+i].num_elements = 1; in pm8001_alloc()
304 pm8001_ha->memoryMap.region[PI+i].element_size = 4; in pm8001_alloc()
305 pm8001_ha->memoryMap.region[PI+i].total_len = 4; in pm8001_alloc()
306 pm8001_ha->memoryMap.region[PI+i].alignment = 4; in pm8001_alloc()
|
| /Linux-v4.19/Documentation/devicetree/bindings/powerpc/nintendo/ |
| D | gamecube.txt | 25 1.b) The Processor Interface (PI) node
33 - reg : should contain the PI registers location and length
39 the PI node.
|
| D | wii.txt | 34 1.b) The Processor Interface (PI) node
42 - reg : should contain the PI registers location and length
48 the PI node.
|
| /Linux-v4.19/drivers/staging/vc04_services/ |
| D | Kconfig | 9 by the Raspberry PI.
|
| /Linux-v4.19/arch/arm/boot/dts/ |
| D | cros-adc-thermistors.dtsi | 6 * Exynos5800 based Peach PI.
|
| D | sun7i-a20-i12-tvbox.dts | 96 /* This controls VCC-PI, must be always on! */
|
| D | sun7i-a20-bananapi.dts | 248 /* PI */
|
| /Linux-v4.19/Documentation/devicetree/bindings/mmc/ |
| D | brcm,sdhci-iproc.txt | 12 Use brcm2835-sdhci for Rasperry PI.
|
| /Linux-v4.19/drivers/net/wireless/realtek/rtl818x/ |
| D | Kconfig | 27 TrendNET TEW-288PI
|
| /Linux-v4.19/Documentation/scheduler/ |
| D | sched-rt-group.txt | 177 the biggest challenge as the current linux PI infrastructure is geared towards
182 This means the whole PI machinery will have to be reworked - and that is one of
|
| /Linux-v4.19/Documentation/media/v4l-drivers/ |
| D | si476x.rst | 152 0x30 rdspi RDS PI code
|
| D | si4713.rst | 132 - rds_pi - Sets the RDS PI field for transmission.
|
12
