| /linux-4.4.14/drivers/net/ |
| D | sb1000.c | 125 short PID[]);
127 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-4.4.14/tools/perf/tests/ |
| D | hists_output.c | 123 #define PID(he) (he->thread->tid) macro
270 CPU(he) == 1 && PID(he) == 100 && he->stat.period == 300); in test2()
275 CPU(he) == 0 && PID(he) == 100 && he->stat.period == 100); in test2()
506 CPU(he) == 0 && PID(he) == 100 && in test5()
513 CPU(he) == 2 && PID(he) == 200 && in test5()
520 CPU(he) == 1 && PID(he) == 300 && in test5()
527 CPU(he) == 0 && PID(he) == 300 && in test5()
534 CPU(he) == 3 && PID(he) == 300 && in test5()
541 CPU(he) == 1 && PID(he) == 100 && in test5()
548 CPU(he) == 2 && PID(he) == 100 && in test5()
[all …]
|
| D | hists_cumulate.c | 157 #define PID(he) (he->thread->tid) macro
|
| /linux-4.4.14/arch/avr32/include/asm/ |
| D | switch_to.h | 20 ocd_write(PID, prev->pid); \
21 ocd_write(PID, next->pid); \
|
| /linux-4.4.14/Documentation/namespaces/ |
| D | compatibility-list.txt | 10 UTS IPC VFS PID User Net
14 PID 1 1 X
18 1. Both the IPC and the PID namespaces provide IDs to address
|
| /linux-4.4.14/Documentation/thermal/ |
| D | power_allocator.txt | 18 PID Controller
22 Proportional-Integral-Derivative controller (PID controller) with
100 The implementation of the PID controller in the power allocator
125 Focusing on the proportional and feed forward values of the PID
160 `k_i` configures the PID loop's integral term constant. This term
161 allows the PID controller to compensate for long term drift and for
172 `k_d` configures the PID loop's derivative term constant. It's
240 The power allocator governor's PID controller works best if there is a
|
| D | sysfs-api.txt | 191 |---k_i: PID's integral term in the power allocator gov
192 |---k_d: PID's derivative term in the power allocator
331 The proportional term of the power allocator governor's PID
339 The proportional term of the power allocator governor's PID
347 The integral term of the power allocator governor's PID
348 controller. This term allows the PID controller to compensate
354 The derivative term of the power allocator governor's PID
362 governor's PID controller starts accumulating errors. For
|
| D | intel_powerclamp.txt | 130 PID-based thermal controller can use the powerclamp driver to
293 PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
304 device, a PID based userspace thermal controller can manage to
|
| /linux-4.4.14/drivers/bcma/ |
| D | README | 5 AMBA standard fields like CID and PID.
9 as standard AMBA device. Reading it's CID or PID can cause machine lockup.
|
| /linux-4.4.14/Documentation/trace/ |
| D | mmiotrace.txt | 133 read event R width, timestamp, map id, physical, value, PC, PID
134 write event W width, timestamp, map id, physical, value, PC, PID
135 ioremap event MAP timestamp, map id, physical, virtual, length, PC, PID
136 iounmap event UNMAP timestamp, map id, PC, PID
141 unk. opcode UNKNOWN timestamp, map id, physical, data, PC, PID
146 used in an operation. PC is the program counter and PID is process id. PC is
147 zero if it is not recorded. PID is always zero as tracing MMIO accesses
|
| D | tracepoint-analysis.txt | 191 o Reading information from /proc for the PID that triggered the event
207 o It can aggregate based on PID or individual process number
210 o When receiving an event about a PID, it can record who the parent was so
|
| D | ftrace.txt | 209 Have the events only trace a task with a PID listed in this file.
572 # TASK-PID CPU# |||| TIMESTAMP FUNCTION
594 PID "1977", the CPU that it was running on "000", the latency format
665 pid: The PID of that process.
846 context-info - Show only the event data. Hides the comm, PID,
889 # TASK-PID CPU# TIMESTAMP FUNCTION
1500 Notice that the recorded task is 'sleep' with the PID of 2389
1697 # TASK-PID CPU# |||| TIMESTAMP FUNCTION
1748 # TASK-PID CPU# TIMESTAMP FUNCTION
1760 # TASK-PID CPU# TIMESTAMP FUNCTION
[all …]
|
| D | uprobetracer.txt | 150 # TASK-PID CPU# TIMESTAMP FUNCTION
|
| D | kprobetrace.txt | 159 # TASK-PID CPU# TIMESTAMP FUNCTION
|
| D | events.txt | 291 5.4 PID filtering
296 PID listed in the set_event_pid file.
|
| /linux-4.4.14/tools/testing/selftests/ftrace/samples/ |
| D | unresolved.tc | 4 kill -INT $PID
|
| /linux-4.4.14/Documentation/usb/ |
| D | linux-cdc-acm.inf | 82 ; 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
|
| D | gadget_configfs.txt | 76 Each gadget needs to have its vendor id <VID> and product id <PID> specified:
79 $ echo <PID> > idProduct
|
| D | gadget-testing.txt | 556 echo VID PID >/sys/bus/usb-serial/drivers/generic/new_id
|
| /linux-4.4.14/Documentation/security/ |
| D | Yama.txt | 32 work), or with CAP_SYS_PTRACE (i.e. "gdb --pid=PID", and "strace -p PID"
60 an allowed debugger PID to call PTRACE_ATTACH on the inferior.
|
| D | credentials.txt | 307 longer permitted to take any PID other than the one of the current process.
|
| /linux-4.4.14/Documentation/vm/ |
| D | soft-dirty.txt | 8 This is done by writing "4" into the /proc/PID/clear_refs file of the
15 This is done by reading from the /proc/PID/pagemap. The bit 55 of the
|
| D | transhuge.txt | 202 necessary to read /proc/PID/smaps and count the AnonHugePages fields
|
| /linux-4.4.14/include/linux/ |
| D | if_frad.h | 41 __be16 PID; member
|
| /linux-4.4.14/include/linux/usb/ |
| D | r8a66597.h | 363 #define PID 0x0003 /* b1-0: Response PID */ macro
408 #define PID 0x0003 /* b1-0: Response PID */ macro
|
| /linux-4.4.14/arch/arm/mm/ |
| D | proc-v6.S | 110 bic r2, r2, #0xff @ extract the PID
142 mrc p15, 0, r4, c13, c0, 0 @ FCSE/PID
162 mcr p15, 0, r4, c13, c0, 0 @ FCSE/PID
|
| D | proc-sa1100.S | 179 mrc p15, 0, r5, c13, c0, 0 @ PID
195 mcr p15, 0, r5, c13, c0, 0 @ PID
|
| D | proc-v7-2level.S | 56 lsr r2, r2, #8 @ extract the PID
|
| D | proc-arm920.S | 393 mrc p15, 0, r4, c13, c0, 0 @ PID
405 mcr p15, 0, r4, c13, c0, 0 @ PID
|
| D | proc-mohawk.S | 358 mrc p15, 0, r6, c13, c0, 0 @ PID
376 mcr p15, 0, r6, c13, c0, 0 @ PID
|
| D | proc-arm926.S | 408 mrc p15, 0, r4, c13, c0, 0 @ PID
420 mcr p15, 0, r4, c13, c0, 0 @ PID
|
| D | proc-xsc3.S | 421 mrc p15, 0, r6, c13, c0, 0 @ PID
439 mcr p15, 0, r6, c13, c0, 0 @ PID
|
| D | proc-feroceon.S | 523 mrc p15, 0, r4, c13, c0, 0 @ PID
535 mcr p15, 0, r4, c13, c0, 0 @ PID
|
| D | proc-xscale.S | 536 mrc p15, 0, r6, c13, c0, 0 @ PID
552 mcr p15, 0, r6, c13, c0, 0 @ PID
|
| D | proc-v7.S | 99 mrc p15, 0, r4, c13, c0, 0 @ FCSE/PID
123 mcr p15, 0, r4, c13, c0, 0 @ FCSE/PID
|
| /linux-4.4.14/arch/unicore32/kernel/ |
| D | sleep.S | 24 movc r3, p0.c7, #0 @ PID
174 movc p0.c7, r3, #0 @ PID
|
| /linux-4.4.14/drivers/hid/usbhid/ |
| D | Kconfig | 28 bool "PID device support"
30 Say Y here if you have a PID-compliant device and wish to enable force
|
| /linux-4.4.14/drivers/media/platform/sti/c8sectpfe/ |
| D | Kconfig | 20 memdma engine, and HW PID filtering.
|
| /linux-4.4.14/Documentation/arm/ |
| D | swp_emulation | 13 /proc/cpu/swp_emulation holds some statistics/information, including the PID of
|
| /linux-4.4.14/arch/arm64/ |
| D | Kconfig.debug | 32 bool "Write the current PID to the CONTEXTIDR register"
34 Enabling this option causes the kernel to write the current PID to
|
| /linux-4.4.14/Documentation/cgroups/ |
| D | pids.txt | 11 place, PIDs are a fundamental resource. As such, PID exhaustion must be
30 all new cgroups (N.B. that PID limits are hierarchical, so the most stringent
|
| D | cgroups.txt | 190 - You can list all the tasks (by PID) attached to any cgroup.
233 - tasks: list of tasks (by PID) attached to that cgroup. This list
317 6) Attach that task to the new cgroup by writing its PID to the
427 # /bin/echo PID > tasks
429 Note that it is PID, not PIDs. You can only attach ONE task at a time.
442 threads in a threadgroup at once. Echoing the PID of any task in a
668 in containers and systemd for assorted meta data like main PID in a cgroup
681 put only ONE PID.
|
| D | cpusets.txt | 813 # /bin/echo PID > tasks
815 Note that it is PID, not PIDs. You can only attach ONE task at a time.
|
| D | unified-hierarchy.txt | 371 - /proc/PID/cgroup keeps reporting the cgroup that a zombie belonged
|
| /linux-4.4.14/Documentation/dvb/ |
| D | faq.txt | 109 into promiscuous mode so it accepts any packets from the PID
118 all then maybe the PID is wrong. If there are error packets,
119 then either the PID is wrong or the stream does not conform to
|
| D | ci.txt | 25 (b) a channels.conf containing a valid PMT PID
28 here 278 is a valid PMT PID. the rest of the values are the
|
| /linux-4.4.14/drivers/media/common/b2c2/ |
| D | flexcop_ibi_value_be.h | 280 u32 PID :13; member
375 u32 PID :13; member
|
| D | flexcop_ibi_value_le.h | 277 u32 PID :13; member
368 u32 PID :13; member
|
| D | flexcop-hw-filter.c | 155 vpid.pid_n_reg_314.PID = onoff ? pid : 0x1fff; in flexcop_pid_control()
|
| /linux-4.4.14/drivers/net/wan/ |
| D | dlci.c | 91 hdr.PID = htons(type); in dlci_header()
153 skb->protocol = hdr->PID; in dlci_receive()
|
| /linux-4.4.14/tools/testing/selftests/ftrace/ |
| D | ftracetest | 226 (cd $TRACING_DIR; read PID _ < /proc/self/stat ; set -e; set -x; . $1)
|
| /linux-4.4.14/tools/thermal/tmon/ |
| D | README | 29 pid.c : a proportional-integral-derivative (PID) controller
|
| /linux-4.4.14/arch/cris/arch-v32/kernel/ |
| D | kgdb.c | 316 BZ, VR, PID, SRS, enumerator
552 } else if (regno == PID) { in write_register()
604 } else if (regno == PID) { in read_register()
|
| /linux-4.4.14/tools/testing/selftests/rcutorture/bin/ |
| D | kvm-test-1-run.sh | 219 echo "!!! PID $qemu_pid hung at $kruntime vs. $seconds seconds" >> $resdir/Warnings 2>&1
|
| /linux-4.4.14/Documentation/devicetree/bindings/nios2/ |
| D | nios2.txt | 22 identifier (PID).
|
| /linux-4.4.14/arch/powerpc/boot/dts/fsl/ |
| D | e5500_power_isa.dtsi | 44 power-isa-e.pd; // Embedded.External PID
|
| D | e500mc_power_isa.dtsi | 44 power-isa-e.pd; // Embedded.External PID
|
| D | e6500_power_isa.dtsi | 44 power-isa-e.pd; // Embedded.External PID
|
| /linux-4.4.14/arch/powerpc/platforms/ |
| D | Kconfig.cputype | 284 bool "icswx requires direct PID management"
288 The PID register in server is used explicitly for ICSWX. In
289 embedded systems PID management is done by the system.
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | proc.txt | 121 process running on the system, which is named after the process ID (PID).
154 read the file /proc/PID/status:
197 file /proc/PID/status. It fields are described in table 1-2.
221 TracerPid PID of process tracing this process (0 if not)
316 0 (place holder, used to be the wchan address, use /proc/PID/wchan instead)
336 The /proc/PID/maps file containing the currently mapped memory regions and
387 The /proc/PID/task/TID/maps is a view of the virtual memory from the viewpoint
390 content of /proc/PID/maps, where you will see all mappings that are being used
392 map, i.e. /proc/PID/task/TID/maps for thread 1001 will look like this:
415 The /proc/PID/smaps is an extension based on maps, showing the memory
[all …]
|
| D | overlayfs.txt | 197 Symlinks in /proc/PID/ and /proc/PID/fd which point to a non-directory
|
| D | ramfs-rootfs-initramfs.txt | 91 checks to see if rootfs contains a file "init", and if so it executes it as PID
|
| /linux-4.4.14/Documentation/sysctl/ |
| D | kernel.txt | 192 and core_uses_pid is set, then .PID will be appended to
198 %P global pid (init PID namespace)
200 %I global tid (init PID namespace)
243 core_uses_pid to 1, the coredump filename becomes core.PID.
245 and core_uses_pid is set, then .PID will be appended to
630 PID allocation wrap value. When the kernel's next PID value
631 reaches this value, it wraps back to a minimum PID value.
|
| /linux-4.4.14/drivers/usb/host/ |
| D | r8a66597-hcd.c | 469 tmp = r8a66597_read(r8a66597, pipe->pipectr) & PID; in pipe_start()
471 r8a66597_mdfy(r8a66597, PID_NAK, PID, pipe->pipectr); in pipe_start()
472 r8a66597_mdfy(r8a66597, PID_BUF, PID, pipe->pipectr); in pipe_start()
480 tmp = r8a66597_read(r8a66597, pipe->pipectr) & PID; in pipe_stop()
482 r8a66597_mdfy(r8a66597, PID_STALL, PID, pipe->pipectr); in pipe_stop()
483 r8a66597_mdfy(r8a66597, PID_NAK, PID, pipe->pipectr); in pipe_stop()
1500 u16 pid = r8a66597_read(r8a66597, td->pipe->pipectr) & PID; in get_urb_error()
|
| /linux-4.4.14/tools/perf/Documentation/ |
| D | perf-timechart.txt | 52 Select the processes to display, by name or PID
|
| /linux-4.4.14/Documentation/filesystems/pohmelfs/ |
| D | info.txt | 72 # cat /proc/$PID/mountstats
|
| /linux-4.4.14/drivers/media/i2c/soc_camera/ |
| D | ov772x.c | 47 #define PID 0x0A /* Product ID Number MSB */ macro
962 pid = ov772x_read(client, PID); in ov772x_video_probe()
|
| D | ov2640.c | 181 #define PID 0x0A /* Product ID Number MSB */ macro
971 pid = i2c_smbus_read_byte_data(client, PID); in ov2640_video_probe()
|
| /linux-4.4.14/arch/avr32/ |
| D | Kconfig | 219 enabling Nexus-compliant debuggers to keep track of the PID of the
|
| /linux-4.4.14/Documentation/ |
| D | gdb-kernel-debugging.txt | 153 function lx_task_by_pid -- Find Linux task by PID and return the task_struct variable
|
| D | kasan.txt | 78 CPU: 0 PID: 1689 Comm: modprobe Tainted: G B 3.18.0-rc1-mm1+ #98
|
| D | workqueue.txt | 42 rising, some systems saturated the default 32k PID space just booting
|
| D | kernel-parameters.txt | 3908 the form VID:PID:Flags where VID and PID are Vendor
|
| D | devices.txt | 3310 be the PID of the locking process as an ASCII number.
|
| /linux-4.4.14/drivers/usb/gadget/udc/ |
| D | r8a66597-udc.c | 110 pid = r8a66597_read(r8a66597, DCPCTR) & PID; in control_reg_get_pid()
113 pid = r8a66597_read(r8a66597, offset) & PID; in control_reg_get_pid()
128 r8a66597_mdfy(r8a66597, pid, PID, DCPCTR); in control_reg_set_pid()
131 r8a66597_mdfy(r8a66597, pid, PID, offset); in control_reg_set_pid()
|
| /linux-4.4.14/Documentation/hid/ |
| D | hidraw.txt | 78 vendor ID (VID), and product ID (PID) of the device. The bus type can be one
|
| /linux-4.4.14/tools/perf/ |
| D | builtin-script.c | 248 if ((PRINT_FIELD(PID) || PRINT_FIELD(TID)) && in perf_evsel__check_attr()
406 if (PRINT_FIELD(PID) && PRINT_FIELD(TID)) in print_sample_start()
408 else if (PRINT_FIELD(PID)) in print_sample_start()
|
| /linux-4.4.14/fs/ |
| D | Kconfig.binfmt | 62 the /proc/PID/coredump_filter pseudo-file; this setting is
|
| /linux-4.4.14/drivers/media/platform/ti-vpe/ |
| D | vpdma.c | 277 DUMPREG(PID); in vpdma_dump_regs()
|
| D | vpe.c | 930 DUMPREG(PID); in vpe_dump_regs()
|
| /linux-4.4.14/drivers/usb/misc/ |
| D | Kconfig | 209 VID/PID pairs. This driver then initiates a corresponding test mode on
|
| /linux-4.4.14/Documentation/RCU/ |
| D | stallwarn.txt | 81 and that the tasks will be indicated by PID, for example, "P3421".
|
| /linux-4.4.14/arch/arm/ |
| D | Kconfig.debug | 1628 bool "Write the current PID to the CONTEXTIDR register"
1631 Enabling this option causes the kernel to write the current PID to
|
| /linux-4.4.14/init/ |
| D | Kconfig | 965 is fairly trivial to reach PID exhaustion before you reach even a
1211 bool "PID Namespaces"
|
| /linux-4.4.14/Documentation/sound/alsa/ |
| D | HD-Audio.txt | 620 # TASK-PID CPU# TIMESTAMP FUNCTION
|
| /linux-4.4.14/drivers/platform/x86/ |
| D | sony-laptop.c | 724 SNC_HANDLE(PID, snc_PID_get, NULL, NULL, 1),
|
| /linux-4.4.14/Documentation/laptops/ |
| D | thinkpad-acpi.txt | 1404 0x8000 Disclose PID of userspace programs
|
| /linux-4.4.14/arch/x86/ |
| D | Kconfig | 642 Calculate simpler /proc/<PID>/wchan values. If this option
|