Home
last modified time | relevance | path

Searched refs:PID (Results 1 – 25 of 156) sorted by relevance

1234567

/linux-5.19.10/Documentation/userspace-api/media/dvb/
Ddmx-get-pes-pids.rst34 This ioctl allows to query a DVB device to return the first PID used
39 PID element position content
41 pids[DMX_PES_AUDIO] 0 first audio PID
42 pids[DMX_PES_VIDEO] 1 first video PID
43 pids[DMX_PES_TELETEXT] 2 first teletext PID
44 pids[DMX_PES_SUBTITLE] 3 first subtitle PID
45 pids[DMX_PES_PCR] 4 first Program Clock Reference PID
50 A value equal to 0xffff means that the PID was not filled by the
Ddmx-remove-pid.rst29 PID of the PES filter to be removed.
34 This ioctl call allows to remove a PID when multiple PIDs are set on a
/linux-5.19.10/tools/testing/selftests/arm64/fp/
DREADME29 PID: 1573
32 PID: 1575
35 PID: 1577
38 PID: 1579
41 PID: 1581
44 PID: 1583
47 PID: 1585
50 PID: 1587
53 PID: 1589
/linux-5.19.10/tools/perf/tests/shell/
Dtest_arm_callgraph_fp.sh47 PID=$!
49 echo " + Recording (PID=$PID)..."
53 kill $PID
54 wait $PID
/linux-5.19.10/Documentation/devicetree/bindings/usb/
Dusb-device.yaml33 "usbVID,PID", where VID is the vendor id and PID the product id.
34 The textual representation of VID and PID shall be in lower case
38 for "usbVID,PID".
64 "usbifVID,PID.configCN.IN", where VID is the vendor id, PID is
66 number. The textual representation of VID, PID, CN and IN shall be
70 all except for "usbifVID,PID.configCN.IN".
/linux-5.19.10/tools/testing/selftests/net/
Dgre_gso.sh19 PID=
70 [ -n "$PID" ] && kill $PID
124 PID=$!
137 kill $PID
138 PID=
Dfin_ack_lat.sh22 PID=$!
/linux-5.19.10/drivers/net/
Dsb1000.c122 short PID[]);
124 const short PID[]);
626 sb1000_get_PIDs(const int ioaddr[], const char* name, short PID[]) in sb1000_get_PIDs() argument
642 PID[0] = st[1] << 8 | st[2]; in sb1000_get_PIDs()
646 PID[1] = st[1] << 8 | st[2]; in sb1000_get_PIDs()
650 PID[2] = st[1] << 8 | st[2]; in sb1000_get_PIDs()
654 PID[3] = st[1] << 8 | st[2]; in sb1000_get_PIDs()
661 sb1000_set_PIDs(const int ioaddr[], const char* name, const short PID[]) in sb1000_set_PIDs() argument
677 p = PID[0]; in sb1000_set_PIDs()
684 p = PID[1]; in sb1000_set_PIDs()
[all …]
/linux-5.19.10/tools/testing/selftests/ftrace/test.d/ftrace/
Dfunc-filter-notrace-pid.tc16 read PID _ < /proc/self/stat
44 echo $PID > set_ftrace_notrace_pid
76 echo $PID > set_ftrace_pid
Dfunc-filter-pid.tc17 read PID _ < /proc/self/stat
44 echo $PID > set_ftrace_pid
/linux-5.19.10/tools/perf/tests/
Dhists_output.c122 #define PID(he) (he->thread->tid) macro
269 CPU(he) == 1 && PID(he) == 100 && he->stat.period == 300); in test2()
274 CPU(he) == 0 && PID(he) == 100 && he->stat.period == 100); in test2()
505 CPU(he) == 0 && PID(he) == 100 && in test5()
512 CPU(he) == 2 && PID(he) == 200 && in test5()
519 CPU(he) == 1 && PID(he) == 300 && in test5()
526 CPU(he) == 0 && PID(he) == 300 && in test5()
533 CPU(he) == 3 && PID(he) == 300 && in test5()
540 CPU(he) == 1 && PID(he) == 100 && in test5()
547 CPU(he) == 2 && PID(he) == 100 && in test5()
[all …]
/linux-5.19.10/Documentation/admin-guide/namespaces/
Dcompatibility-list.rst13 - UTS IPC VFS PID User Net
18 PID 1 1 X
23 1. Both the IPC and the PID namespaces provide IDs to address
/linux-5.19.10/arch/arm64/
DKconfig.debug4 bool "Write the current PID to the CONTEXTIDR register"
6 Enabling this option causes the kernel to write the current PID to
/linux-5.19.10/Documentation/trace/
Dmmiotrace.rst152 read event R width, timestamp, map id, physical, value, PC, PID
153 write event W width, timestamp, map id, physical, value, PC, PID
154 ioremap event MAP timestamp, map id, physical, virtual, length, PC, PID
155 iounmap event UNMAP timestamp, map id, PC, PID
160 unk. opcode UNKNOWN timestamp, map id, physical, data, PC, PID
165 used in an operation. PC is the program counter and PID is process id. PC is
166 zero if it is not recorded. PID is always zero as tracing MMIO accesses
/linux-5.19.10/drivers/bcma/
DREADME5 AMBA standard fields like CID and PID.
9 as standard AMBA device. Reading it's CID or PID can cause machine lockup.
/linux-5.19.10/Documentation/driver-api/thermal/
Dpower_allocator.rst19 PID Controller
23 Proportional-Integral-Derivative controller (PID controller) with
103 The implementation of the PID controller in the power allocator
128 Focusing on the proportional and feed forward values of the PID
165 `k_i` configures the PID loop's integral term constant. This term
166 allows the PID controller to compensate for long term drift and for
177 `k_d` configures the PID loop's derivative term constant. It's
266 The power allocator governor's PID controller works best if there is a
/linux-5.19.10/Documentation/translations/zh_CN/admin-guide/mm/damon/
Dreclaim.rst183 DAMON线程的PID
185 如果DAMON_RECLAIM被启用,这将成为工作线程的PID。否则,为-1。
/linux-5.19.10/Documentation/ABI/testing/
Dsysfs-bus-i3c70 PID stands for Provisional ID and is used to uniquely identify
71 a device on a bus. This PID contains information about the
75 This entry describes the PID of the master controller driving
126 PID stands for Provisional ID and is used to uniquely identify
127 a device on a bus. This PID contains information about the
Dsysfs-class-thermal122 The derivative term of the power allocator governor's PID
130 The integral term of the power allocator governor's PID
131 controller. This term allows the PID controller to compensate
139 The proportional term of the power allocator governor's PID
149 The proportional term of the power allocator governor's PID
161 governor's PID controller starts accumulating errors. For
/linux-5.19.10/tools/testing/selftests/ftrace/samples/
Dunresolved.tc4 kill -INT $PID
/linux-5.19.10/tools/testing/selftests/rcutorture/bin/
Dkvm-test-1-run-qemu.sh36 echo ' ---' `date`: Starting kernel, PID $$
172 echo "!!! PID $qemu_pid hung at $kruntime vs. $seconds seconds `date`" >> $resdir/Warnings 2>&1
/linux-5.19.10/Documentation/translations/zh_CN/admin-guide/
Dtainted-kernels.rst29 在进程ID(“PID:”)和触发事件命令的缩写名称(“Comm:”)之后::
33 CPU: 0 PID: 4424 Comm: insmod Tainted: P W O 4.20.0-0.rc6.fc30 #1
/linux-5.19.10/Documentation/translations/zh_TW/admin-guide/
Dtainted-kernels.rst32 在進程ID(「PID:」)和觸發事件命令的縮寫名稱(「Comm:」)之後::
36 CPU: 0 PID: 4424 Comm: insmod Tainted: P W O 4.20.0-0.rc6.fc30 #1
/linux-5.19.10/Documentation/usb/
Dlinux-cdc-acm.inf82 ; When developing your USB device, the VID and PID used in the PC side
84 ; Modify the below line to use your VID and PID. Use the format as shown
/linux-5.19.10/Documentation/admin-guide/LSM/
DYama.rst34 work), or with ``CAP_SYS_PTRACE`` (i.e. "gdb --pid=PID", and "strace -p PID"
64 an allowed debugger PID to call ``PTRACE_ATTACH`` on the inferior.

1234567