Home
last modified time | relevance | path

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

/linux-4.1.27/drivers/net/
Dsb1000.c125 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.1.27/tools/perf/tests/
Dhists_output.c119 #define PID(he) (he->thread->tid) macro
266 CPU(he) == 1 && PID(he) == 100 && he->stat.period == 300); in test2()
271 CPU(he) == 0 && PID(he) == 100 && he->stat.period == 100); in test2()
502 CPU(he) == 0 && PID(he) == 100 && in test5()
509 CPU(he) == 2 && PID(he) == 200 && in test5()
516 CPU(he) == 1 && PID(he) == 300 && in test5()
523 CPU(he) == 0 && PID(he) == 300 && in test5()
530 CPU(he) == 3 && PID(he) == 300 && in test5()
537 CPU(he) == 1 && PID(he) == 100 && in test5()
544 CPU(he) == 2 && PID(he) == 100 && in test5()
[all …]
Dhists_cumulate.c153 #define PID(he) (he->thread->tid) macro
/linux-4.1.27/arch/avr32/include/asm/
Dswitch_to.h20 ocd_write(PID, prev->pid); \
21 ocd_write(PID, current->pid); \
/linux-4.1.27/Documentation/namespaces/
Dcompatibility-list.txt10 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.1.27/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-4.1.27/Documentation/trace/
Dmmiotrace.txt133 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
Dtracepoint-analysis.txt191 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
Dftrace.txt561 # TASK-PID CPU# |||| TIMESTAMP FUNCTION
583 PID "1977", the CPU that it was running on "000", the latency format
654 pid: The PID of that process.
833 context-info - Show only the event data. Hides the comm, PID,
876 # TASK-PID CPU# TIMESTAMP FUNCTION
1487 Notice that the recorded task is 'sleep' with the PID of 2389
1684 # TASK-PID CPU# |||| TIMESTAMP FUNCTION
1735 # TASK-PID CPU# TIMESTAMP FUNCTION
1747 # TASK-PID CPU# TIMESTAMP FUNCTION
1975 # CPU TASK/PID DURATION FUNCTION CALLS
[all …]
Duprobetracer.txt150 # TASK-PID CPU# TIMESTAMP FUNCTION
Dkprobetrace.txt159 # TASK-PID CPU# TIMESTAMP FUNCTION
/linux-4.1.27/tools/testing/selftests/ftrace/samples/
Dunresolved.tc4 kill -INT $PID
/linux-4.1.27/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
Dgadget_configfs.txt76 Each gadget needs to have its vendor id <VID> and product id <PID> specified:
79 $ echo <PID> > idProduct
Dgadget-testing.txt558 echo VID PID >/sys/bus/usb-serial/drivers/generic/new_id
/linux-4.1.27/Documentation/security/
DYama.txt34 work), or with CAP_SYS_PTRACE (i.e. "gdb --pid=PID", and "strace -p PID"
62 an allowed debugger PID to call PTRACE_ATTACH on the inferior.
Dcredentials.txt307 longer permitted to take any PID other than the one of the current process.
/linux-4.1.27/Documentation/vm/
Dsoft-dirty.txt8 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
Dtranshuge.txt192 necessary to read /proc/PID/smaps and count the AnonHugePages fields
/linux-4.1.27/include/linux/
Dif_frad.h41 __be16 PID; member
/linux-4.1.27/include/linux/usb/
Dr8a66597.h363 #define PID 0x0003 /* b1-0: Response PID */ macro
408 #define PID 0x0003 /* b1-0: Response PID */ macro
/linux-4.1.27/arch/arm/mm/
Dproc-v6.S110 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
Dproc-sa1100.S179 mrc p15, 0, r5, c13, c0, 0 @ PID
195 mcr p15, 0, r5, c13, c0, 0 @ PID
Dproc-v7-2level.S54 lsr r2, r2, #8 @ extract the PID
Dproc-mohawk.S358 mrc p15, 0, r6, c13, c0, 0 @ PID
376 mcr p15, 0, r6, c13, c0, 0 @ PID
Dproc-arm920.S393 mrc p15, 0, r4, c13, c0, 0 @ PID
405 mcr p15, 0, r4, c13, c0, 0 @ PID
Dproc-arm926.S408 mrc p15, 0, r4, c13, c0, 0 @ PID
420 mcr p15, 0, r4, c13, c0, 0 @ PID
Dproc-xsc3.S421 mrc p15, 0, r6, c13, c0, 0 @ PID
439 mcr p15, 0, r6, c13, c0, 0 @ PID
Dproc-xscale.S536 mrc p15, 0, r6, c13, c0, 0 @ PID
552 mcr p15, 0, r6, c13, c0, 0 @ PID
Dproc-feroceon.S523 mrc p15, 0, r4, c13, c0, 0 @ PID
535 mcr p15, 0, r4, c13, c0, 0 @ PID
Dproc-v7.S99 mrc p15, 0, r4, c13, c0, 0 @ FCSE/PID
123 mcr p15, 0, r4, c13, c0, 0 @ FCSE/PID
/linux-4.1.27/arch/unicore32/kernel/
Dsleep.S24 movc r3, p0.c7, #0 @ PID
174 movc p0.c7, r3, #0 @ PID
/linux-4.1.27/drivers/hid/usbhid/
DKconfig28 bool "PID device support"
30 Say Y here if you have a PID-compliant device and wish to enable force
/linux-4.1.27/Documentation/arm/
Dswp_emulation13 /proc/cpu/swp_emulation holds some statistics/information, including the PID of
/linux-4.1.27/arch/arm64/
DKconfig.debug36 bool "Write the current PID to the CONTEXTIDR register"
38 Enabling this option causes the kernel to write the current PID to
/linux-4.1.27/Documentation/dvb/
Dfaq.txt109 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
Dci.txt25 (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.1.27/drivers/media/common/b2c2/
Dflexcop_ibi_value_be.h280 u32 PID :13; member
375 u32 PID :13; member
Dflexcop_ibi_value_le.h277 u32 PID :13; member
368 u32 PID :13; member
Dflexcop-hw-filter.c151 vpid.pid_n_reg_314.PID = onoff ? pid : 0x1fff; in flexcop_pid_control()
/linux-4.1.27/drivers/net/wan/
Ddlci.c91 hdr.PID = htons(type); in dlci_header()
153 skb->protocol = hdr->PID; in dlci_receive()
/linux-4.1.27/tools/testing/selftests/ftrace/
Dftracetest226 (cd $TRACING_DIR; read PID _ < /proc/self/stat ; set -e; set -x; . $1)
/linux-4.1.27/tools/thermal/tmon/
DREADME29 pid.c : a proportional-integral-derivative (PID) controller
/linux-4.1.27/arch/cris/arch-v32/kernel/
Dkgdb.c316 BZ, VR, PID, SRS, enumerator
557 } else if (regno == PID) { in write_register()
604 } else if (regno == PID) { in read_register()
/linux-4.1.27/tools/testing/selftests/rcutorture/bin/
Dkvm-test-1-run.sh219 echo "!!! PID $qemu_pid hung at $kruntime vs. $seconds seconds" >> $resdir/Warnings 2>&1
/linux-4.1.27/Documentation/devicetree/bindings/nios2/
Dnios2.txt22 identifier (PID).
/linux-4.1.27/Documentation/cgroups/
Dcgroups.txt190 - 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
664 in containers and systemd for assorted meta data like main PID in a cgroup
677 put only ONE PID.
Dcpusets.txt813 # /bin/echo PID > tasks
815 Note that it is PID, not PIDs. You can only attach ONE task at a time.
/linux-4.1.27/Documentation/sysctl/
Dkernel.txt191 and core_uses_pid is set, then .PID will be appended to
197 %P global pid (init PID namespace)
199 %I global tid (init PID namespace)
242 core_uses_pid to 1, the coredump filename becomes core.PID.
244 and core_uses_pid is set, then .PID will be appended to
618 PID allocation wrap value. When the kernel's next PID value
619 reaches this value, it wraps back to a minimum PID value.
/linux-4.1.27/arch/powerpc/boot/dts/fsl/
De500mc_power_isa.dtsi44 power-isa-e.pd; // Embedded.External PID
De5500_power_isa.dtsi44 power-isa-e.pd; // Embedded.External PID
De6500_power_isa.dtsi44 power-isa-e.pd; // Embedded.External PID
/linux-4.1.27/arch/powerpc/platforms/
DKconfig.cputype295 bool "icswx requires direct PID management"
299 The PID register in server is used explicitly for ICSWX. In
300 embedded systems PID management is done by the system.
/linux-4.1.27/Documentation/filesystems/
Dproc.txt121 process running on the system, which is named after the process ID (PID).
154 read the file /proc/PID/status:
196 file /proc/PID/status. It fields are described in table 1-2.
220 TracerPid PID of process tracing this process (0 if not)
313 0 (place holder, used to be the wchan address, use /proc/PID/wchan instead)
333 The /proc/PID/maps file containing the currently mapped memory regions and
384 The /proc/PID/task/TID/maps is a view of the virtual memory from the viewpoint
387 content of /proc/PID/maps, where you will see all mappings that are being used
389 map, i.e. /proc/PID/task/TID/maps for thread 1001 will look like this:
412 The /proc/PID/smaps is an extension based on maps, showing the memory
[all …]
Doverlayfs.txt196 Symlinks in /proc/PID/ and /proc/PID/fd which point to a non-directory
Dramfs-rootfs-initramfs.txt91 checks to see if rootfs contains a file "init", and if so it executes it as PID
/linux-4.1.27/Documentation/thermal/
Dintel_powerclamp.txt130 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.1.27/drivers/usb/host/
Dr8a66597-hcd.c469 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.1.27/tools/perf/Documentation/
Dperf-timechart.txt52 Select the processes to display, by name or PID
/linux-4.1.27/Documentation/filesystems/pohmelfs/
Dinfo.txt72 # cat /proc/$PID/mountstats
/linux-4.1.27/drivers/media/i2c/soc_camera/
Dov772x.c47 #define PID 0x0A /* Product ID Number MSB */ macro
949 pid = ov772x_read(client, PID); in ov772x_video_probe()
Dov2640.c181 #define PID 0x0A /* Product ID Number MSB */ macro
978 pid = i2c_smbus_read_byte_data(client, PID); in ov2640_video_probe()
/linux-4.1.27/Documentation/
Dgdb-kernel-debugging.txt153 function lx_task_by_pid -- Find Linux task by PID and return the task_struct variable
Dkasan.txt80 CPU: 0 PID: 1689 Comm: modprobe Tainted: G B 3.18.0-rc1-mm1+ #98
Dworkqueue.txt42 rising, some systems saturated the default 32k PID space just booting
Dkernel-parameters.txt3788 the form VID:PID:Flags where VID and PID are Vendor
Ddevices.txt3310 be the PID of the locking process as an ASCII number.
/linux-4.1.27/arch/avr32/
DKconfig219 enabling Nexus-compliant debuggers to keep track of the PID of the
/linux-4.1.27/tools/perf/
Dbuiltin-script.c221 if ((PRINT_FIELD(PID) || PRINT_FIELD(TID)) && in perf_evsel__check_attr()
356 if (PRINT_FIELD(PID) && PRINT_FIELD(TID)) in print_sample_start()
358 else if (PRINT_FIELD(PID)) in print_sample_start()
/linux-4.1.27/drivers/usb/gadget/udc/
Dr8a66597-udc.c110 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.1.27/Documentation/hid/
Dhidraw.txt78 vendor ID (VID), and product ID (PID) of the device. The bus type can be one
/linux-4.1.27/fs/
DKconfig.binfmt62 the /proc/PID/coredump_filter pseudo-file; this setting is
/linux-4.1.27/drivers/media/platform/ti-vpe/
Dvpdma.c277 DUMPREG(PID); in vpdma_dump_regs()
Dvpe.c930 DUMPREG(PID); in vpe_dump_regs()
/linux-4.1.27/drivers/usb/misc/
DKconfig209 VID/PID pairs. This driver then initiates a corresponding test mode on
/linux-4.1.27/Documentation/RCU/
Dstallwarn.txt87 and that the tasks will be indicated by PID, for example, "P3421".
/linux-4.1.27/arch/arm/
DKconfig.debug1578 bool "Write the current PID to the CONTEXTIDR register"
1581 Enabling this option causes the kernel to write the current PID to
/linux-4.1.27/Documentation/sound/alsa/
DHD-Audio.txt620 # TASK-PID CPU# TIMESTAMP FUNCTION
/linux-4.1.27/drivers/platform/x86/
Dsony-laptop.c723 SNC_HANDLE(PID, snc_PID_get, NULL, NULL, 1),
/linux-4.1.27/Documentation/laptops/
Dthinkpad-acpi.txt1404 0x8000 Disclose PID of userspace programs
/linux-4.1.27/init/
DKconfig1200 bool "PID Namespaces"
/linux-4.1.27/arch/x86/
DKconfig632 Calculate simpler /proc/<PID>/wchan values. If this option