Home
last modified time | relevance | path

Searched refs:process (Results 1 – 200 of 661) sorted by relevance

1234

/linux-4.4.14/drivers/gpu/drm/amd/amdkfd/
Dkfd_process.c80 struct kfd_process *process; in kfd_create_process() local
102 process = find_process(thread); in kfd_create_process()
103 if (process) in kfd_create_process()
106 if (!process) in kfd_create_process()
107 process = create_process(thread); in kfd_create_process()
113 return process; in kfd_create_process()
118 struct kfd_process *process; in kfd_get_process() local
127 process = find_process(thread); in kfd_get_process()
129 return process; in kfd_get_process()
134 struct kfd_process *process; in find_process_by_mm() local
[all …]
Dkfd_doorbell.c120 int kfd_doorbell_mmap(struct kfd_process *process, struct vm_area_struct *vma) in kfd_doorbell_mmap() argument
138 address = kfd_get_process_doorbells(dev, process); in kfd_doorbell_mmap()
220 struct kfd_process *process, in kfd_queue_id_to_doorbell() argument
229 process->pasid * (doorbell_process_allocation()/sizeof(u32)) + in kfd_queue_id_to_doorbell()
244 struct kfd_process *process) in kfd_get_process_doorbells() argument
247 process->pasid * doorbell_process_allocation(); in kfd_get_process_doorbells()
Dkfd_chardev.c104 struct kfd_process *process; in kfd_open() local
120 process = kfd_create_process(current); in kfd_open()
121 if (IS_ERR(process)) in kfd_open()
122 return PTR_ERR(process); in kfd_open()
125 process->pasid, process->is_32bit_user_mode); in kfd_open()
576 aw_info.process = p; in kfd_ioctl_dbg_address_watch()
698 wac_info.process = p; in kfd_ioctl_dbg_wave_control()
716 wac_info.process, wac_info.operand, in kfd_ioctl_dbg_wave_control()
929 struct kfd_process *process; in kfd_ioctl() local
957 process = kfd_get_process(current); in kfd_ioctl()
[all …]
Dkfd_dbgmgr.c143 if (pmgr->pasid != wac_info->process->pasid) { in kfd_dbgmgr_wave_control()
145 wac_info->process->pasid); in kfd_dbgmgr_wave_control()
159 if (pmgr->pasid != adw_info->process->pasid) { in kfd_dbgmgr_address_watch()
161 adw_info->process->pasid); in kfd_dbgmgr_address_watch()
Dkfd_process_queue_manager.c63 pqm->process->pasid); in find_available_queue_slot()
83 pqm->process = p; in pqm_init()
126 kfd_queue_id_to_doorbell(dev, pqm->process, qid); in create_cp_queue()
137 (*q)->process = pqm->process; in create_cp_queue()
171 pdd = kfd_get_process_device_data(dev, pqm->process); in pqm_create_queue()
300 pdd = kfd_get_process_device_data(dev, pqm->process); in pqm_destroy_queue()
Dkfd_flat_memory.c296 int kfd_init_apertures(struct kfd_process *process) in kfd_init_apertures() argument
306 pdd = kfd_create_process_device_data(dev, process); in kfd_init_apertures()
316 if (process->is_32bit_user_mode) { in kfd_init_apertures()
Dkfd_device_queue_manager_vi.c130 if (qpd->pqm->process->is_32bit_user_mode) { in register_process_vi()
143 qpd->pqm->process->is_32bit_user_mode, temp, qpd->sh_mem_bases); in register_process_vi()
153 if (q->process->is_32bit_user_mode) in init_sdma_vm()
Dkfd_device_queue_manager_cik.c121 if (qpd->pqm->process->is_32bit_user_mode) { in register_process_cik()
131 qpd->pqm->process->is_32bit_user_mode, temp, qpd->sh_mem_bases); in register_process_cik()
141 if (q->process->is_32bit_user_mode) in init_sdma_vm()
Dkfd_priv.h383 struct kfd_process *process; member
410 struct kfd_process *process; member
577 int kfd_doorbell_mmap(struct kfd_process *process, struct vm_area_struct *vma);
584 struct kfd_process *process,
617 int kfd_init_apertures(struct kfd_process *process);
701 struct kfd_process *process);
715 int kfd_event_mmap(struct kfd_process *process, struct vm_area_struct *vma);
Dkfd_dbgmgr.h238 struct kfd_process *process; member
247 struct kfd_process *process; member
Dkfd_queue.c62 pr_debug("Queue Process Address: 0x%p\n", q->process); in print_queue()
Dkfd_dbgdev.c294 adw_info->process); in dbgdev_address_watch_nodiq()
496 adw_info->process->pasid, in dbgdev_address_watch_diq()
717 wac_info->process->pasid, in dbgdev_wave_control_diq()
743 pdd = kfd_get_process_device_data(dbgdev->dev, wac_info->process); in dbgdev_wave_control_nodiq()
/linux-4.4.14/Documentation/trace/postprocess/
Dtrace-pagealloc-postprocess.pl202 my $process = $1;
207 if ($opt_read_procstat && $process eq '') {
355 my $process;
359 $process = $process_pid;
360 $process =~ s/-([0-9])*$//;
361 if ($process eq '') {
362 $process = "NO_PROCESS_NAME";
365 $perprocess{$process}->{MM_PAGE_ALLOC} += $perprocesspid{$process_pid}->{MM_PAGE_ALLOC};
366 …$perprocess{$process}->{MM_PAGE_ALLOC_ZONE_LOCKED} += $perprocesspid{$process_pid}->{MM_PAGE_ALLOC…
367 $perprocess{$process}->{MM_PAGE_FREE} += $perprocesspid{$process_pid}->{MM_PAGE_FREE};
[all …]
Dtrace-vmscan-postprocess.pl284 my $process = $1;
287 if ($process eq "") {
288 $process = $last_procmap{$pid};
289 $process_pid = "$process-$pid";
291 $last_procmap{$pid} = $process;
295 if ($opt_read_procstat && $process eq '') {
666 my $process;
670 $process = $process_pid;
671 $process =~ s/-([0-9])*$//;
672 if ($process eq '') {
[all …]
/linux-4.4.14/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/
Dbase.c37 u32 process, u32 message, u32 data0, u32 data1) in nvkm_pmu_send() argument
59 pmu->recv.process = process; in nvkm_pmu_send()
70 nvkm_wr32(device, 0x10a1c4, process); in nvkm_pmu_send()
81 wait_event(pmu->recv.wait, (pmu->recv.process == 0)); in nvkm_pmu_send()
96 u32 process, message, data0, data1; in nvkm_pmu_recv() local
111 process = nvkm_rd32(device, 0x10a1c4); in nvkm_pmu_recv()
121 if (pmu->recv.process) { in nvkm_pmu_recv()
122 if (process == pmu->recv.process && in nvkm_pmu_recv()
126 pmu->recv.process = 0; in nvkm_pmu_recv()
136 (char)((process & 0x000000ff) >> 0), in nvkm_pmu_recv()
[all …]
/linux-4.4.14/Documentation/security/
Dkeys-request-key.txt9 The process starts by either the kernel requesting a service by calling
56 The two async in-kernel calls may return keys that are still in the process of
60 The userspace interface links the key to a keyring associated with the process
79 (2) request_key() searches the process's subscribed keyrings to see if there's
81 and callout_info is not set, an error is returned. Otherwise the process
89 (b) An authorisation key V that refers to key U and notes that process A
105 This will permit it to then search the keyrings of process A with the
106 UID, GID, groups and security info of process A as if it was process A,
122 context specified by auth key X will still be process A, as it was in auth key
125 This is because process A's keyrings can't simply be attached to
[all …]
DYama.txt13 malware. One particularly troubling weakness of the Linux process
31 parent to a child process (i.e. direct "gdb EXE" and "strace EXE" still
36 between a debugging process and its inferior (crash handlers, etc),
38 other process (and its descendants) are allowed to call PTRACE_ATTACH
39 against it. Only one such declared debugging process can exists for
42 to ptrace each other. If a process wishes to entirely disable these ptrace
44 so that any otherwise allowed process (even those in external pid namespaces)
49 0 - classic ptrace permissions: a process can PTRACE_ATTACH to any other
50 process running under the same uid, as long as it is dumpable (i.e.
55 1 - restricted ptrace: a process must have a predefined relationship
DSmack.txt44 smackaccess - report if a process with one label has access
67 name space. A process must have CAP_MAC_ADMIN to change any of these
75 of the process that created it.
77 The Smack label of a process that execs a program file with
80 Don't allow the file to be mmapped by a process whose Smack
81 label does not allow all of the access permitted to a process
90 creating process. If the object being created is a directory
106 A process can see the Smack label it is running with by
107 reading /proc/self/attr/current. A process with CAP_MAC_ADMIN
108 can set the process Smack by writing there.
[all …]
Dkeys.txt72 are used to control what a process may do to a key from userspace, and
152 (*) Each process subscribes to three keyrings: a thread-specific keyring, a
153 process-specific keyring, and a session-specific keyring.
159 The process-specific keyring is replaced with an empty one in the child on
161 shared. execve also discards the process's process keyring and creates a
166 process can, however, replace its current session keyring with a new one
177 When a process changes its real UID, if it used to have no session key, it
180 If a process attempts to access its session key when it doesn't have one,
204 userspace to request a key that can't be found in a process's keyrings.
241 keyring to a key, a process must have Write permission on the keyring and
[all …]
Dcredentials.txt180 The permitted capabilities are those caps that the process might grant
209 be searched for the desired key. Each process may subscribe to a number
213 Per-process keyring
216 When a process accesses a key, if not already present, it will normally be
269 privilege escalation bits come into play, and may allow the resulting process
307 longer permitted to take any PID other than the one of the current process.
309 attachment to process-specific keyrings in the requesting process as the
310 instantiating process may need to create them.
334 A task being able to alter only its own credentials permits the current process
368 process's current set of credentials:
[all …]
/linux-4.4.14/drivers/staging/lustre/lustre/llite/
Dlproc_llite.c1303 struct ll_rw_process_info *process; in ll_rw_stats_tally() local
1311 process = sbi->ll_rw_process_info; in ll_rw_stats_tally()
1348 if (process[i].rw_pid == pid) { in ll_rw_stats_tally()
1349 if (process[i].rw_last_file != file) { in ll_rw_stats_tally()
1350 process[i].rw_range_start = pos; in ll_rw_stats_tally()
1351 process[i].rw_last_file_pos = pos + count; in ll_rw_stats_tally()
1352 process[i].rw_smallest_extent = count; in ll_rw_stats_tally()
1353 process[i].rw_largest_extent = count; in ll_rw_stats_tally()
1354 process[i].rw_offset = 0; in ll_rw_stats_tally()
1355 process[i].rw_last_file = file; in ll_rw_stats_tally()
[all …]
/linux-4.4.14/Documentation/
Dnumastat.txt8 numa_hit A process wanted to allocate memory from this node,
11 numa_miss A process wanted to allocate memory from another node,
14 numa_foreign A process wanted to allocate on this node,
17 local_node A process ran on this node and got memory from it.
19 other_node A process ran on this node and got memory from another node.
Dunshare.txt28 as multiple execution contexts within a process. These kernels provide
47 shared resources without creating a new process. unshare is a natural
49 the concept of process/thread as a virtual machine.
54 where creating a new process to control sharing/unsharing of process
56 when creating a new process using fork or clone, unshare can benefit
64 the kernel's per-process namespace mechanism. Polyinstantiated directories,
81 decide what needs to be shared at the time of creating the process
85 ability to unshare after the process was created can be very
119 unshare - disassociate parts of the process execution context
127 unshare allows a process to disassociate parts of its execution
[all …]
DCodeOfConflict4 The Linux kernel development effort is a very personal process compared
10 the overall success of Linux. This development process has been proven
16 uncomfortable due to this process, that is not acceptable. If so,
26 be high on both sides of the process. Try to keep in mind the immortal
Drobust-futexes.txt27 process exits prematurely while holding a pthread_mutex_t lock that is
28 also shared with some other process (e.g. yum segfaults while holding a
69 This is very much noticeable even for normal process sys_exit_group()
74 into this process's address space).
95 is empty. If the thread/process crashed or terminated in some incorrect
106 instructions window for the thread (or process) to die there, leaving
147 I have benchmarked the time needed for the kernel to process a list of 1
Dhwspinlock.txt25 appropriate user process.
42 Should be called from a process context (might sleep).
49 Should be called from a process context (might sleep).
59 Should be called from a process context (might sleep).
65 Should be called from a process context (might sleep).
244 numerous locks). Should be called from a process context (this function
252 Should be called from a process context (this function might sleep).
Drpmsg.txt75 The function can only be called from a process context (for now).
92 The function can only be called from a process context (for now).
110 The function can only be called from a process context (for now).
122 The function can only be called from a process context (for now).
136 The function can only be called from a process context (for now).
151 The function can only be called from a process context (for now).
174 is invoked to process it.
Drtc.txt63 built in locking so that only one process is allowed to have the /dev/rtc
66 A user process can monitor these interrupts by doing a read(2) or a
67 select(2) on /dev/rtc -- either will block/stop the user process until
72 At high frequencies, or under high loads, the user process should check
91 the process of doing this, the kernel briefly turns off RTC periodic
Dlocal_ops.txt57 - This CPU can use local ops from any context (process, irq, softirq, nmi, ...)
60 process context to make sure the process won't be migrated to a
DHOWTO21 know to achieve this by describing the process you need to go through,
215 The development process
218 Linux kernel development process currently consists of a few different
231 process is as follows:
252 process should last around 6 weeks.
286 how the release process works.
314 process is tracked with the tool patchwork. Patchwork offers a web
510 should also be introduced very early in the development process, so that
543 reviewers do not want to see the thought process behind the
549 unfinished work. Therefore it is good to get early in the process to
[all …]
/linux-4.4.14/tools/perf/util/
Dheader.h96 int (*process)(struct perf_file_section *section,
104 perf_event__handler_t process);
107 perf_event__handler_t process);
113 perf_event__handler_t process);
120 perf_event__handler_t process,
Devent.c173 perf_event__handler_t process, in perf_event__synthesize_comm() argument
181 if (process(tool, event, &synth_sample, machine) != 0) in perf_event__synthesize_comm()
190 perf_event__handler_t process, in perf_event__synthesize_fork() argument
213 if (process(tool, event, &synth_sample, machine) != 0) in perf_event__synthesize_fork()
222 perf_event__handler_t process, in perf_event__synthesize_mmap_events() argument
339 if (process(tool, event, &synth_sample, machine) != 0) { in perf_event__synthesize_mmap_events()
353 perf_event__handler_t process, in perf_event__synthesize_modules() argument
397 if (process(tool, event, &synth_sample, machine) != 0) { in perf_event__synthesize_modules()
411 perf_event__handler_t process, in __event__synthesize_thread() argument
426 process, machine); in __event__synthesize_thread()
[all …]
Devent.h395 perf_event__handler_t process,
399 perf_event__handler_t process,
403 perf_event__handler_t process,
407 perf_event__handler_t process,
484 perf_event__handler_t process,
490 perf_event__handler_t process,
Dthread-stack.c59 int (*process)(struct call_return *cr, void *data); member
219 return crp->process(&cr, crp->data); in thread_stack__call_return()
441 call_return_processor__new(int (*process)(struct call_return *cr, void *data), in call_return_processor__new()
452 crp->process = process; in call_return_processor__new()
Dheader.c1913 int (*process)(struct perf_file_section *section, member
1923 .process = process_##func }
1926 .process = process_##func, .full_only = true }
2176 int (*process)(struct perf_file_section *section, in perf_header__process_sections()
2203 err = process(sec++, header, feat, fd, data); in perf_header__process_sections()
2417 if (!feat_ops[feat].process) in perf_file_section__process()
2420 return feat_ops[feat].process(section, ph, fd, data); in perf_file_section__process()
2657 perf_event__handler_t process) in perf_event__synthesize_attr() argument
2680 err = process(tool, ev, NULL, NULL); in perf_event__synthesize_attr()
2691 perf_event__handler_t process) in perf_event__synthesize_attrs() argument
[all …]
Dthread-stack.h103 call_return_processor__new(int (*process)(struct call_return *cr, void *data),
Dmachine.h118 machine__process_t process, void *data);
234 perf_event__handler_t process, bool data_mmap,
Dsession.h137 perf_event__handler_t process,
/linux-4.4.14/Documentation/locking/
Drt-mutex-design.txt23 Priority inversion is when a lower priority process executes while a higher
24 priority process wants to run. This happens for several reasons, and
25 most of the time it can't be helped. Anytime a high priority process wants
26 to use a resource that a lower priority process has (a mutex for example),
27 the high priority process must wait until the lower priority process is done
30 priority process is prevented from running by a lower priority process for
35 priority process, C is the lowest, and B is in between. A tries to grab a lock
38 but by doing so, it is in fact preempting A which is a higher priority process.
63 PI is where a process inherits the priority of another process if the other
64 process blocks on a lock owned by the current process. To make this easier
[all …]
/linux-4.4.14/Documentation/accounting/
Dtaskstats.txt6 per-process statistics from the kernel to userspace.
21 "tgid", "process" and "thread group" are used interchangeably and refer to the
22 tasks that share an mm_struct i.e. the traditional Unix process. Despite the
24 leader - a process is deemed alive as long as it has any task belonging to it.
32 statistics for all tasks of the process (if tgid is specified).
48 send commands and process responses, listen for per-tid/tgid exit data,
80 the task/process for which userspace wants statistics.
111 e) TASKSTATS_TYPE_TGID: contains tgid of process to which task belongs
112 f) TASKSTATS_TYPE_STATS: contains the per-tgid stats for exiting task's process
118 Taskstats provides per-process stats, in addition to per-task stats, since
[all …]
/linux-4.4.14/Documentation/ABI/stable/
Dsysfs-devices-system-cpu19 for any process that has not set the DSCR itself.
20 If a process ever sets the DSCR (via direct access to the
21 SPR) that value will be persisted for that process and used
24 If set by a process it will be inherited by child processes.
Dfirewire-cdev81 and map it into the process address space. The arguments should
92 Unmap the isochronous I/O buffer from the process address space.
/linux-4.4.14/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/fuc/
Dkernel.fuc30 process(PROC_KERN, 0, 0)
140 // $r14 - process
143 // read process' timer status, skip if not enabled
148 // subtract last timer's value from process' timer,
159 // process' timer is the soonest
171 // update process' timer status, and advance
327 // request the current process be sent a message after a timeout expires
339 // if current process already has a timer set, bail
387 // send message to another process
390 // $r14 - process
[all …]
Didle.fuc26 process(PROC_IDLE, #idle, #idle_recv)
60 // keep looping while there's pending messages for any process
65 // process the process' messages until there's none left
74 // next process!
Dhost.fuc26 process(PROC_HOST, #host_init, #host_recv)
62 // HOST->PWR comms - dequeue message(s) for process(es) from FIFO
76 // read message data, and pass to appropriate process
94 // $r14 - process
Dperf.fuc26 process(PROC_PERF, #perf_init, #perf_recv)
43 // $r14 - sender process name
Dtest.fuc26 process(PROC_TEST, #test_init, #test_recv)
42 // $r14 - sender process name
Dmemx.fuc26 process(PROC_MEMX, #memx_init, #memx_recv)
363 // $r14 - sender process name
404 // $r14 - sender process name
429 // $r14 - sender process name
/linux-4.4.14/Documentation/block/
Dioprio.txt10 processes or process groups, similar to what has been possible with cpu
18 served for a process.
23 care, one io RT process can starve the entire system. Within the RT class,
25 process needs the disk for on each service. In the future this might change
30 for any process that hasn't set a specific io priority. The class data
31 determines how much io bandwidth the process will get, it's directly mappable
47 If pid isn't given, the current process is assumed. IO priority settings
48 are inherited on fork, so you can use ionice to start the process at a given
54 For a running process, you can give the pid instead:
Dcfq-iosched.txt7 CFQ maintains the per process queue for the processes which request I/O
10 process's I/O priority.
88 to recompute the slice time for each process based on the target_latency set
90 latency (setting it to 0) ignores target latency, allowing each process in the
97 This parameter is used to calculate the time slice for a process if cfq's
101 time for each process to issue I/O request before the cfq queue is switched.
207 process gets bigger time slice and lower priority process gets smaller time
226 on same queue after completion of a request. In this process CFQ will not
230 on rotational media. For example, if a process is doing dependent
281 scheduled for another second. A process doing small fsync, will suffer
/linux-4.4.14/Documentation/vm/
Dpage_migration5 nodes in a numa system while the process is running. This means that the
6 virtual addresses that the process sees do not change. However, the
10 by moving pages near to the processor where the process accessing that memory
13 Page migration allows a process to manually relocate the node on which its
15 a new memory policy via mbind(). The pages of process can also be relocated
16 from another process using the sys_migrate_pages() function call. The
18 process that are located on the from nodes to the destination nodes.
24 pages of a process are located. See also the numa_maps documentation in the
28 a process to a processor on a distant node. A batch scheduler or an
29 administrator may detect the situation and move the pages of the process
[all …]
Dactive_mm.txt32 - "tsk->mm" points to the "real address space". For an anonymous process,
33 tsk->mm will be NULL, for the logical reason that an anonymous process
40 The rule is that for a process with a real address space (ie tsk->mm is
44 For a anonymous process, tsk->mm == NULL, and tsk->active_mm is the
45 "borrowed" mm while the anonymous process is running. When the
46 anonymous process gets scheduled away, the borrowed address space is
Didle_page_tracking.txt28 process address space, page cache and buffer pages, swap cache pages. For other
45 /proc/pid/pagemap if the workload is represented by a process, or by
62 considered referenced if it has been recently accessed via a process address
67 - a userspace process reads or writes a page using a system call (e.g. read(2)
71 because a process needs filesystem metadata stored in it (e.g. lists a
86 from a process address space. To avoid interference with the reclaimer, which,
Dhwpoison.txt17 * running process can just be killed directly instead. This implies
33 * for the mapping from a vma to a process. Since this case is expected
59 (can be controlled globally and per process)
61 This allows applications who can process memory errors in a gentle
88 the SIGBUS(BUS_MCEERR_AO) on behalf of the process, you should
102 Poison a page in the process for testing
Dpagemap.txt10 * /proc/pid/pagemap. This file lets a userspace process find out which
156 The general procedure for using pagemap to find out about a process' memory
169 memory that a process is using that is not shared with any other process,
170 you can go through every map in the process, find the PFNs, look those up
Dbalance18 a proactive process.
71 and all process contexts are sleeping. For 2.3, kswapd does not really
76 Page stealing from process memory and shm is done if stealing the page would
/linux-4.4.14/Documentation/rapidio/
Drapidio.txt120 several methods to initiate an enumeration and/or discovery process:
122 (a) Statically linked enumeration and discovery process can be started
132 expires the discovery process is terminated without obtaining RapidIO network
133 information. NOTE: a timed out discovery process may be restarted later using
137 (b) Statically linked enumeration and discovery process can be started by
140 endpoints have been successfully booted, an enumeration process shall be
142 completed a discovery process can be started on all remaining endpoints.
144 (c) Modular enumeration and discovery process can be started by a command from
146 process can be started by issuing a user-space command.
149 (d) Modular enumeration and discovery process can be started by a module
[all …]
Dsysfs.txt70 set by the switch initialization routine during enumeration or discovery process.
100 scan - allows to trigger enumeration discovery process from user space. This
102 process on specific mport device, a user needs to write mport_ID (not
/linux-4.4.14/arch/arm/mach-ux500/
Dcpu.c109 if (dbx500_id.process == 0x00) in ux500_get_process()
112 return sprintf(buf, "%02xnm\n", dbx500_id.process); in ux500_get_process()
125 __ATTR(process, S_IRUGO, ux500_get_process, NULL);
Did.c111 dbx500_id.process = asicid >> 24; in ux500_setup_id()
Did.h20 u8 process; member
/linux-4.4.14/Documentation/powerpc/
Dpmu-ebb.txt28 When a PMU EBB occurs it is delivered to the currently running process. As such
33 events, however unless the target process enables EBBs (via mtspr(BESCR)) no
36 This makes it possible for a process to enable EBBs for itself, but not
37 actually configure any events. At a later time another process can come along
38 and attach an EBB event to the process, which will then cause EBBs to be
39 delivered to the first process. It's not clear if this is actually useful.
43 user process. This means once an EBB event is scheduled on the PMU, no non-EBB
47 It is however safe to run 'perf' commands on a process which is using EBBs. The
109 meaningless. Because interrupts are being delivered to the user process the
135 EBB events are not inherited across fork. If the child process wishes to use
Ddscr.txt34 gets used directly in the scheduler process context switch at all.
43 the current process has the dscr_inherit clear, it also writes the new
82 Any child of the process created after this event in the process inherits
Dcxlflash.txt158 such as a killed process. This design point is described in further
164 - These tokens are only valid for the process under which they
165 were created. The child of a forked process cannot continue
170 the process under which they were created. Once either is
245 As part of the release process for virtual LUNs, the virtual LUN
261 support maintaining user space access to storage after a process
262 forks. Upon success, the child process (which invoked the ioctl)
268 for the child process. This ioctl simplifies the state management
269 and playback required by a user in such a scenario. When a process
270 forks, child process can clone the parents context by first creating
[all …]
Dcxl.txt70 this mode, only one userspace process can use the accelerator at
123 AFU provides. Slave contexts have access to only the per process
126 For AFUs operating in dedicated process mode, the driver will
169 process. Once this ioctl is successfully executed, all memory
170 mapped into this process is accessible to this AFU context
220 Get the current context id, also known as the process element.
234 process MMIO space associated with the context. In dedicated
235 process mode the entire MMIO space can always be mapped.
/linux-4.4.14/Documentation/arm/
Dswp_emulation11 signalled to the triggering process.
14 the last process to trigger the emulation to be invocated. For example:
19 Last process: 314
Dmem_alignment32 0 A user process performing an unaligned memory access
34 process name, pid, pc, instruction, address, and the
37 1 The kernel will attempt to fix up the user process
42 2 The kernel will send a SIGBUS signal to the user process
DPorting67 The maximum size of a user process in bytes. Since user space
69 process can access+1. The user space stack grows down from this
72 Any virtual address below TASK_SIZE is deemed to be user process
73 area, and therefore managed dynamically on a process by process
Dkernel_user_helpers.txt37 performed only once at process startup time, and execution aborted early
39 process is running on.
71 during the lifetime of any single process. This means that this
/linux-4.4.14/Documentation/filesystems/caching/
Dcachefiles.txt318 behalf of a process, and running in that process's context, and that includes a
320 because the files in the cache are inaccessible to that process, or because if
321 the process creates a file in the cache, that file may be inaccessible to other
325 fsgid and actor security label) that the process acts as - without changing the
326 security context of the process when it the target of an operation performed by
327 some other process (so signalling and suchlike still work correctly).
338 (2) Finds the security label of the process which issued the bind request
351 type_transition <daemon's-ID> kernel_t : process <module's-ID>;
355 type_transition cachefilesd_t kernel_t : process cachefiles_kernel_t;
411 when it acts on behalf of another process, in that process's context.
[all …]
/linux-4.4.14/scripts/kconfig/
Dstreamline_config.pl275 my $process = "";
283 $process .= $start . $vars{$var};
285 $process .= $start . $variable;
289 $process .= $line;
291 return $process;
/linux-4.4.14/Documentation/infiniband/
Duser_verbs.txt40 This also allows the kernel to clean up when a process exits and
41 prevent one process from touching another process's resources.
49 amount of memory pinned in the process's locked_vm, and checks that
54 number of pages pinned by a process.
Dcore_locking.txt94 may be process context, softirq context, or interrupt context.
105 ib_unregister_device() from process context. It must not hold any
/linux-4.4.14/Documentation/filesystems/
Dmandatory-locking.txt17 A process may then see file data change even while a mandatory
21 read has actually completed, and the reading process may see
34 normally a process' responsibility to check for locks on a file it wishes to
47 block attempts by a process to write to a file that another process holds a
49 file that a process holds a "write " -or- "exclusive" lock on.
90 another process has outstanding mandatory locks. This is in direct
122 2. If a process has locked a region of a file with a mandatory read lock, then
125 released, unless the process has opened the file with the O_NONBLOCK
129 3. If a process has locked a region of a file with a mandatory write lock, all
131 unless a process has opened the file with the O_NONBLOCK flag in which case
Dproc.txt121 process running on the system, which is named after the process ID (PID).
123 The link self points to the process reading the file system. Each process
135 exe Link to the executable of this process
138 mem Memory held by this process
139 root Link to the root directory of this process
153 For example, to get the status information of a process, all you have to do is
196 information. But you get a more detailed view of the process by reading the
199 The statm file contains more detailed information about the process
201 contains details information about the process itself. Its fields are
219 Pid process id
[all …]
Dhfsplus.txt22 Default: user/group id of the mounting process.
27 Default: umask of the mounting process.
Dinotify.txt26 select()-able. Yes, root can bump the per-process fd limit and yes, users
65 need not be a one-fd-per-process mapping; it is one-fd-per-queue and a
66 process can easily want more than one queue.
Ddirectory-locking72 Now consider the minimal deadlock. Each process is blocked on
75 not contended, since any process blocked on it is not holding any locks.
78 By (3), any process holding a non-directory lock can only be
80 the process holding the "largest" such lock can always make progress, and
Dfuse.txt7 userspace process. The filesystem can be accessed normally through
12 The process(es) providing the data and metadata of the filesystem.
151 If a process issuing a FUSE filesystem request is interrupted, the
286 system process to eat up diskspace, memory or other
292 mount owner can ptrace a process, it can do all of the above
294 ptrace can be used to check if a process is allowed to access
299 privilege to send signal to the process accessing the
Dhfs.txt25 Default: user/group id of the mounting process.
29 files and directories. Defaults to the umask of the mounting process.
Dvfat.txt12 The default is the uid of current process.
15 The default is the gid of current process.
18 The default is the umask of current process.
21 The default is the umask of current process.
24 The default is the umask of current process.
28 20 - If current process is in group of file's group ID,
35 Normally utime(2) checks current process is owner of
Dautomount-support.txt50 with a pointer to this list. This will process the list, marking every
78 mountpoint (though some will be rejected - the current process's idea of the
Dcoda.txt159 service the request for the process. Venus manages a persistent
197 a process PP which accessing a Coda file. It makes a system call which
224 returns to the process.
241 between a user process and Venus, called the pioctl interface. The
245 the calling process and passes the information on to Venus. When
272 on behalf of a process P, creates messages for Venus, awaits replies
295 the OS. This notification is done in the upcall context of the process
296 P. When the message is on the pending queue, process P cannot proceed
319 Venus. The process P will be scheduled at some point and continues
345 at the flags field. If the message is not yet READ, the process P can
[all …]
/linux-4.4.14/tools/perf/Documentation/
Djit-interface.txt4 The JIT has to write a /tmp/perf-%d.map (%d = pid of process) file
15 The ownership of the file has to match the process.
Dperf-trace.txt48 Record events on existing process ID (comma separated list).
96 Show process COMM right beside its ID, on by default, disable with --no-comm.
163 As you can see, there was major pagefault in python process, from
DBuild.txt4 The perf build process consists of several separated building blocks,
/linux-4.4.14/drivers/connector/
DKconfig15 bool "Report process events to userspace"
19 Provide a connector that reports process events to userspace. Send
/linux-4.4.14/arch/um/os-Linux/
DMakefile6 obj-y = aio.o execvp.o file.o helper.o irq.o main.o mem.o process.o \
13 main.o mem.o process.o registers.o sigio.o signal.o start_up.o time.o \
/linux-4.4.14/arch/arm/mach-omap2/
Domap-secure.h64 extern u32 omap_smc3(u32 id, u32 process, u32 flag, u32 pargs);
68 extern u32 rx51_secure_dispatcher(u32 idx, u32 process, u32 flag, u32 nargs,
Domap-secure.c89 u32 rx51_secure_dispatcher(u32 idx, u32 process, u32 flag, u32 nargs, in rx51_secure_dispatcher() argument
109 ret = omap_smc3(idx, process, flag, __pa(param)); in rx51_secure_dispatcher()
/linux-4.4.14/Documentation/usb/
Ddwc3.txt31 reads the event and tries to process it. Everything that requires
34 We probably have to pay attention not to process events once we
35 handed something to thread so we don't process event X prio Y
/linux-4.4.14/Documentation/RCU/
DUP.txt17 elements A, B, and C in process context, and can delete elements from
18 this same list in softirq context. Suppose that the process-context scan
36 from process context. However, this can fail in a similar manner.
39 elements A, B, and C in process contexts, but that it invokes a function
112 RCU callback, then a process-context acquisition of this
116 If the process-context code were to simply use spin_lock(),
119 the process-context critical section. This would result in
/linux-4.4.14/drivers/gpu/drm/nouveau/include/nvkm/subdev/
Dpmu.h20 u32 process; member
26 int nvkm_pmu_send(struct nvkm_pmu *, u32 reply[2], u32 process,
/linux-4.4.14/security/keys/
DKconfig13 associated with a process so that network filesystems, encryption
17 a searchable sequence of keys. Each process is equipped with access
19 process and thread.
33 it is or by a process with administrative privileges. The active
/linux-4.4.14/drivers/android/
DKconfig18 This means one Android process can call a method/routine in another
19 Android process, using Binder to identify, invoke and pass arguments
/linux-4.4.14/drivers/net/wan/
Ddlci.c108 int process, header; in dlci_receive() local
118 process = 0; in dlci_receive()
154 process = 1; in dlci_receive()
160 process = 1; in dlci_receive()
178 if (process) in dlci_receive()
/linux-4.4.14/arch/mn10300/mm/
Dcache-inv-by-tag.S184 # process the way 0 slot
198 # process the way 1 slot
212 # process the way 2 slot
226 # process the way 3 slot
/linux-4.4.14/Documentation/cgroups/
Dpids.txt7 The process number controller is used to allow a cgroup hierarchy to stop any
27 creation of a new process would cause a cgroup policy to be violated.
80 # /bin/echo "We can't even spawn a single process now."
83 # /bin/echo "We can't even spawn a single process now."
/linux-4.4.14/Documentation/development-process/
D1.Intro8 there is some technical material here, this is very much a process-oriented
15 The rest of this section covers the scope of the kernel development process
23 Section 2 introduces the development process, the kernel release cycle, and
33 Section 4 is about the coding process; several pitfalls which have been
38 Section 5 talks about the process of posting patches for review. To be
46 development process; this section offers a number of tips on how to avoid
82 process. But, if anything, the kernel is even more open than most other
93 surprising that Linux kernel development process differs greatly from
96 The kernel's development process may come across as strange and
102 who will not listen or who do not care about the development process.
[all …]
D2.Process8 how the process works is required in order to be an effective part of it.
13 The kernel developers use a loosely time-based release process, with a new
41 and staged ahead of time. How that process works will be described in
66 At that point the whole process starts over again.
134 process designed to ensure that each patch is reviewed for quality and that
136 This process can happen quickly for minor fixes, or, in the case of large
138 comes from a lack of understanding of this process or from attempts to
143 describes the process in a somewhat idealized way. A much more detailed
156 process should turn up any major problems with a patch if all goes
164 process works, this step leads to more extensive review of the patch and
[all …]
D8.Conclusion11 distributions runs into internal limits and fails to process the documents
54 Linux kernel is developed and how you can participate in that process.
D7.AdvancedTopics3 At this point, hopefully, you have a handle on how the development process
6 regular part of the Linux kernel development process.
25 fits into the kernel development process in particular. Developers who
127 importantly, do not use a git tree to bypass the review process. Post an
151 looking at code you can make a significant contribution to the process as a
/linux-4.4.14/Documentation/timers/
Dtimer_stats.txt20 - the pid of the task(process) which initialized the timer
21 - the name of the process which initialized the timer
64 column is the name of the process. The forth column shows the function which
/linux-4.4.14/Documentation/ABI/testing/
Ddebugfs-pfo-nx-crypto22 - The process ID of the process who received the most recent error from the
Dsysfs-devices-soc43 What: /sys/devices/socX/process
48 the process by which the silicon chip was manufactured.
Dsysfs-bus-fcoe13 process.
27 The FCoE Controller now has a three stage creation process.
/linux-4.4.14/Documentation/networking/
Dnetdevices.txt52 Context: process
56 Context: process
61 Context: process
65 Context: nominally process, but don't sleep inside an rwlock
Dpacket_mmap.txt24 In Linux 2.4/2.6/3.x if PACKET_MMAP is not enabled, the capture process is very
38 transmission process, but it isn't everything. At least, if you are capturing
47 + How to use mmap() to improve capture process
67 + How to use mmap() directly to improve capture process
71 the following process:
78 user process
107 also the mapping of the circular buffer in the user process and
111 + How to use mmap() directly to improve transmission process
113 Transmission process is similar to capture as shown below.
120 user process
[all …]
Dsecid.txt10 derived from other sources such as process context, device, etc., in special
Dnetlink_mmap.txt22 The TX ring is used to process messages directly from user-space memory, the
150 process. These values correspond to the data available using SOCK_PASSCRED in
171 to process the message and release the frame back to
287 /* No more messages to process, continue polling */
/linux-4.4.14/drivers/gpu/drm/radeon/
Dradeon_asic.c217 .process = &r100_irq_process,
285 .process = &r100_irq_process,
381 .process = &r100_irq_process,
449 .process = &r100_irq_process,
517 .process = &r100_irq_process,
585 .process = &r100_irq_process,
653 .process = &rs600_irq_process,
721 .process = &rs600_irq_process,
789 .process = &rs600_irq_process,
857 .process = &rs600_irq_process,
[all …]
/linux-4.4.14/arch/um/os-Linux/skas/
DMakefile6 obj-y := mem.o process.o
/linux-4.4.14/Documentation/target/
Dtcmu-design.txt52 If the target is a userspace process, supporting these is easy. tgt,
106 the ring to still work if the user process dies and is restarted with
201 <subtype> will be a userspace-process-unique string to identify the
203 will be an additional handler-specific string for the user process to
229 Userspace handler process never attaches:
234 Userspace handler process is killed:
240 Userspace handler process hangs:
244 Userspace handler process is malicious:
246 - The process can trivially break the handling of devices it controls,
254 A user process handing a TCMU device must support the following:
/linux-4.4.14/arch/um/kernel/skas/
DMakefile6 obj-y := clone.o mmu.o process.o syscall.o uaccess.o
/linux-4.4.14/arch/score/kernel/
DMakefile7 obj-y += entry.o irq.o process.o ptrace.o \
/linux-4.4.14/Documentation/isdn/
DREADME.concap5 drivers that need to process an encapsulation protocol.
36 traditional linux network device drivers used to process the
98 - process (xmit) data handed down by upper protocol layer
100 - process connect indication from lower (hardware) layer
101 - process disconnect indication from lower (hardware) layer
128 /* process a frame handed down to us by upper layer */
135 Protocols that don't process these primitives might fill in
DHiSax.cert46 some validation checks that are made during the make process. The HiSax main
55 message confirming this is then displayed during the hisax init process.
/linux-4.4.14/lib/
Dklist.c177 struct task_struct *process; member
199 wake_up_process(waiter->process); in klist_release()
244 waiter.process = current; in klist_remove()
/linux-4.4.14/arch/openrisc/kernel/
DMakefile7 obj-y := setup.o or32_ksyms.o process.o dma.o \
/linux-4.4.14/arch/m32r/kernel/
DMakefile7 obj-y := process.o entry.o traps.o align.o irq.o setup.o time.o \
/linux-4.4.14/arch/cris/kernel/
DMakefile9 obj-y := process.o traps.o irq.o ptrace.o setup.o time.o sys_cris.o
/linux-4.4.14/arch/cris/arch-v32/kernel/
DMakefile9 process.o ptrace.o setup.o signal.o traps.o time.o \
/linux-4.4.14/arch/c6x/kernel/
DMakefile7 obj-y := process.o traps.o irq.o signal.o ptrace.o
/linux-4.4.14/arch/cris/arch-v10/kernel/
DMakefile9 process.o setup.o signal.o traps.o time.o ptrace.o \
/linux-4.4.14/kernel/power/
DMakefile7 obj-$(CONFIG_FREEZER) += process.o
/linux-4.4.14/arch/h8300/kernel/
DMakefile7 obj-y := process.o traps.o ptrace.o \
/linux-4.4.14/Documentation/sysctl/
Dvm.txt72 That should provide enough for the admin to log in and kill a process,
144 Contains the amount of dirty memory at which a process generating disk writes
170 and reclaimable pages, the number of pages at which a process which is
287 the kernel to allow process memory to be allocated from the "lowmem"
373 This file contains the maximum number of memory map areas a process
401 0: Only unmap the corrupted page from all processes and only kill a process
453 The process of reclaiming slab memory is currently not node specific
477 This file indicates the amount of address space which a user process will
680 If this is set to 0, the kernel will kill some rogue process,
685 However, if a process limits using nodes by mempolicy/cpusets,
[all …]
Dabi.txt9 When a process is executed, it's linked to an exec_domain whose
Dkernel.txt98 If BSD-style process accounting is enabled these values control
223 application to gather data about the crashing process from its
225 for the collecting process to exit, so as not to remove the crashing
227 possibility that a misbehaving userspace collecting process can block
228 the reaping of a crashed process simply by never exiting. This sysctl
235 process is not guaranteed access to /proc/<crashing pid>/). This
700 This option can be used to select the type of process address
704 0 - Turn the process address space randomization off. This is the
725 with CONFIG_COMPAT_BRK enabled, which excludes the heap from process
786 process can consume, via setrlimit(2). Unfortunately, shared memory
[all …]
/linux-4.4.14/arch/avr32/kernel/
DMakefile10 obj-y += signal.o process.o time.o
/linux-4.4.14/kernel/
DKconfig.preempt29 low priority process to voluntarily preempt itself even if it
44 permitting a low priority process to be preempted involuntarily
/linux-4.4.14/arch/nios2/kernel/
DMakefile13 obj-y += process.o
/linux-4.4.14/Documentation/kbuild/
D00-INDEX2 - this file: info on the kernel build process
/linux-4.4.14/arch/hexagon/kernel/
DMakefile6 obj-y += process.o trampoline.o reset.o ptrace.o vdso.o
/linux-4.4.14/arch/arc/
DKconfig.debug9 kernel stack attached to each process/thread. The default is 8K.
/linux-4.4.14/Documentation/prctl/
Dseccomp_filter.txt7 A large number of system calls are exposed to every userland process
8 with many of them going unused for the entire lifetime of the process.
15 Seccomp filtering provides a means for a process to specify a filter for
78 execution of a process.
206 currently emulated call. Any other change MAY terminate the process.
209 rip or rsp. (Do not rely on other changes terminating the process.
Dno_new_privs.txt12 /etc/passwd to be replaced from the point of view of a process that
18 new, generic mechanism to make it safe for a process to modify its
/linux-4.4.14/net/nfc/hci/
DKconfig7 implementation. This is mostly needed for devices that only process
/linux-4.4.14/arch/unicore32/kernel/
DMakefile6 obj-y := dma.o elf.o entry.o process.o ptrace.o
/linux-4.4.14/arch/microblaze/kernel/
DMakefile19 platform.o process.o prom.o ptrace.o \
/linux-4.4.14/arch/frv/kernel/
DMakefile11 process.o traps.o ptrace.o signal.o dma.o \
/linux-4.4.14/drivers/gpu/drm/amd/amdgpu/
Damdgpu_irq.h51 int (*process)(struct amdgpu_device *adev, member
/linux-4.4.14/arch/xtensa/kernel/
DMakefile7 obj-y := align.o coprocessor.o entry.o irq.o pci-dma.o platform.o process.o \
/linux-4.4.14/drivers/staging/iio/Documentation/
Dsysfs-bus-iio-light-tsl258320 It is used in the process of calibrating the device accuracy.
/linux-4.4.14/arch/m68k/kernel/
DMakefile16 obj-y := entry.o irq.o m68k_ksyms.o module.o process.o ptrace.o
/linux-4.4.14/kernel/debug/kdb/
Dkdb_cmds3 # processes. Commands that require process data (including stack or
/linux-4.4.14/arch/metag/kernel/
DMakefile16 obj-y += process.o
/linux-4.4.14/arch/nios2/
DKconfig.debug15 This option will slow down process creation somewhat.
/linux-4.4.14/arch/um/kernel/
DMakefile14 physmem.o process.o ptrace.o reboot.o sigio.o \
/linux-4.4.14/arch/arc/kernel/
DMakefile11 obj-y := arcksyms.o setup.o irq.o time.o reset.o ptrace.o process.o devtree.o
/linux-4.4.14/drivers/power/avs/
DKconfig8 static factors (chip manufacturing process) and dynamic factors
/linux-4.4.14/arch/blackfin/kernel/
DMakefile8 entry.o process.o bfin_ksyms.o ptrace.o setup.o signal.o \
/linux-4.4.14/Documentation/devicetree/bindings/media/
Drenesas,jpu.txt4 and decoding function conforming to the JPEG baseline process, so that the JPU
/linux-4.4.14/Documentation/virtual/kvm/devices/
Dvm.txt60 -ENOMEM if not enough memory is available to process the ioctl
84 -ENOMEM if not enough memory is available to process the ioctl
/linux-4.4.14/tools/perf/
Ddesign.txt227 code, even after the mapping (or even the whole process) is gone,
230 The 'comm' bit allows tracking of process comm data on process creation.
434 A process can enable or disable all the counter groups that are
441 This applies to all counters on the current process, whether created
442 by this process or by another, and doesn't affect any counters that
443 this process has created on other processes. It only enables or
/linux-4.4.14/arch/mn10300/kernel/
DMakefile9 obj-y := process.o signal.o entry.o traps.o irq.o \
/linux-4.4.14/Documentation/i2c/busses/
Di2c-amd811133 Supported. Both PEC and block process call support is implemented. Slave
/linux-4.4.14/Documentation/devicetree/bindings/i2c/
Di2c-sunxi-p2wi.txt23 process to switch from I2C to P2WI mode
/linux-4.4.14/arch/tile/kernel/
DMakefile7 pci-dma.o proc.o process.o ptrace.o reboot.o \
/linux-4.4.14/arch/parisc/kernel/
DMakefile11 process.o processor.o pdc_cons.o pdc_chassis.o unwind.o \
/linux-4.4.14/arch/sh/
DKconfig.debug36 kernel stack attached to each process/thread. This facilitates
47 overflowing the process kernel stacks.
/linux-4.4.14/Documentation/filesystems/nfs/
Dfault_injection.txt23 process the first n items it finds. So if you want to forget 5 locks, echo '5'
64 This script has been created to ease the fault injection process. This script
/linux-4.4.14/Documentation/mic/
Dscif_overview.txt24 process in a SCIF node initiates a SCIF connection to a peer process on a
/linux-4.4.14/Documentation/DocBook/
Dw1.xml.db8 API-w1-process-callbacks
/linux-4.4.14/Documentation/thermal/
Dcpu-cooling-api.txt144 The temperature, operating voltage and process 'grade' (slow to fast)
149 process as well as the type, number and size of transistors in both
161 arbitrary process grade, voltage and temperature point. These values
163 process grade, the current temperature and the operating voltage.
/linux-4.4.14/drivers/net/wireless/mwifiex/
DREADME157 cmd_resp_received = <0/1, no cmd response to process/response received and yet to process>
158 event_received = <0/1, no event to process/event received and yet to process>
/linux-4.4.14/fs/bfs/
DKconfig7 files during the boot process. It is usually mounted under /stand
/linux-4.4.14/Documentation/video4linux/bttv/
DREADME.freeze30 for each process using sysrq-t (see Documentation/sysrq.txt).
31 This way it is possible to figure where *exactly* some process in "D"
/linux-4.4.14/arch/x86/tools/
Drelocs.c645 static void walk_relocs(int (*process)(struct section *sec, Elf_Rel *rel, in walk_relocs()
672 process(sec, rel, sym, symname); in walk_relocs()
1070 # define process process_64 macro
1072 # define process process_32 macro
1075 void process(FILE *fp, int use_real_mode, int as_text, in process() function
/linux-4.4.14/Documentation/power/
Dpm_qos_interface.txt73 cleanup of a process, the interface requires the process to register its
76 To register the default pm_qos target for the specific parameter, the process
79 As long as the device node is held open that process has a registered
82 To change the requested target value the process needs to write an s32 value to
Dfreezing-of-tasks.txt20 freeze_processes() (defined in kernel/power/process.c) is called. A system-wide
30 to as 'the freezer' (these functions are defined in kernel/power/process.c,
124 process running on a second CPU while we are suspending devices may, for
157 to achieve without the freezing of tasks. Consider, for example, a process
159 disable nonboot CPUs during the hibernation, if this process is not frozen, it
190 fail, because the user land process that should respond to the request is frozen
/linux-4.4.14/arch/metag/
DKconfig.debug14 kernel stack attached to each process/thread. This facilitates
/linux-4.4.14/arch/cris/boot/compressed/
DREADME4 This can be slightly confusing because it's a process with many steps.
/linux-4.4.14/arch/sh/kernel/
DMakefile16 machvec.o nmi_debug.o process.o \
/linux-4.4.14/drivers/staging/fsl-mc/
DTODO13 in process upstream, see [1] and [2].
/linux-4.4.14/Documentation/connector/
Dconnector.txt23 netlink based networking for inter-process communication in a significantly
127 driver or userspace process can ask connector to notify it when
140 be lost due to memory pressure or process' receiving queue overflowed,
/linux-4.4.14/arch/s390/kernel/
DMakefile42 obj-y := traps.o time.o process.o base.o early.o setup.o idle.o vtime.o
/linux-4.4.14/drivers/target/
DKconfig39 process to handle requests. This is version 2 of the ABI; version 1
/linux-4.4.14/arch/m68k/fpsp040/
Dx_store.S140 beqs get_mant |if positive, go process mantissa
143 bras get_mant |go process mantissa
Dbugfix.S254 | exceptional, we choose to kill the process.
342 | fpsp_fmt_error and allow the kernel to kill the process.
376 | exceptional, we choose to kill the process.
482 | to the entry point used to kill a process.
/linux-4.4.14/arch/sh/kernel/cpu/sh5/
Dswitchto.S72 ! the point where the process is left in suspended animation, i.e. current
135 ! go to save_pc for a reschedule, or the initial thread.pc for a new process
/linux-4.4.14/Documentation/driver-model/
Dbinding.txt4 Driver binding is the process of associating a device with a device
81 The process is almost identical for when a new driver is added.
/linux-4.4.14/arch/arm/nwfpe/
DChangeLog50 embedded in the process task structure. Thus we were scribbling
68 flush_thread() in arch/arm/process.c. The change to
/linux-4.4.14/Documentation/serial/
Dtty.txt60 read() - (optional) A process requests reading data from
63 If not defined, the process will receive an EIO
66 write() - (optional) A process requests writing data to the
69 process will receive an EIO error. May sleep.
204 reception when it is ready to process more data.
/linux-4.4.14/security/smack/
DKconfig23 intention is that a process can be granted a wide set
/linux-4.4.14/Documentation/namespaces/
Dcompatibility-list.txt20 process group with pid.
/linux-4.4.14/arch/arm64/kernel/
DMakefile15 entry-fpsimd.o process.o ptrace.o setup.o signal.o \
/linux-4.4.14/Documentation/virtual/uml/
DUserModeLinux-HOWTO.txt6 Linux: a port of the Linux kernel as a normal Intel Linux process.
191 3. You can debug the User Mode Linux like any normal process.
342 You can also get the kernel build process to install them as follows:
514 down and the process will exit.
553 because UML occupies the upper .5G of the 3G process address space
566 load itself in the top .5G of that smaller process address space,
1654 Slip is another, less general, mechanism for a process to communicate
2106 files just like any other process and make them available inside the
2472 Since the user-mode kernel runs as a normal Linux process, it is
2473 possible to debug it with gdb almost like any other process. It is
[all …]
/linux-4.4.14/Documentation/scheduler/
Dsched-stats.txt144 the same information on a per-process level. There are three fields in
145 this file correlating for that process to:
151 report on how well a particular process or set of processes is faring
/linux-4.4.14/Documentation/early-userspace/
DREADME18 midway through the kernel boot process.
25 archive to be used as the image or have the kernel build process build
38 The kernel build process can also build an early userspace image from
/linux-4.4.14/Documentation/trace/
Dmmiotrace.txt58 The 'cat' process should stay running (sleeping) in the background.
71 The 'cat' process exits. If it does not, kill it by issuing 'fg' command and
146 used in an operation. PC is the program counter and PID is process id. PC is
/linux-4.4.14/drivers/net/ethernet/intel/fm10k/
Dfm10k_mbx.c771 mbx->ops.process(hw, mbx); in fm10k_mbx_enqueue_tx()
786 mbx->ops.process(hw, mbx); in fm10k_mbx_enqueue_tx()
1417 mbx->ops.process(hw, mbx); in fm10k_mbx_disconnect()
1626 mbx->ops.process = fm10k_mbx_process; in fm10k_pfvf_mbx_init()
1760 mbx->ops.process(hw, mbx); in fm10k_sm_mbx_disconnect()
2171 mbx->ops.process = fm10k_sm_mbx_process; in fm10k_sm_mbx_init()
Dfm10k_mbx.h239 s32 (*process)(struct fm10k_hw *, struct fm10k_mbx_info *); member
/linux-4.4.14/Documentation/blockdev/drbd/
Ddrbd-connection-state-overview.dot48 …cluster_resync [ shape=record,label="{<any>resynchronisation process running\l'concurrent' applica…
/linux-4.4.14/Documentation/devicetree/bindings/media/xilinx/
Dvideo.txt4 Xilinx video IP cores process video streams by acting as video sinks and/or
/linux-4.4.14/arch/ia64/kernel/
DMakefile12 irq_lsapic.o ivt.o machvec.o pal.o patch.o process.o perfmon.o ptrace.o sal.o \
/linux-4.4.14/Documentation/sound/alsa/
DJack-Controls.txt14 can be read by any process.
/linux-4.4.14/Documentation/parisc/
Dregisters11 CR 8 (Protection ID) per-process value*
39 SR3 used for userspace accesses (current process)
/linux-4.4.14/arch/x86/crypto/sha-mb/
Dsha1_mb_mgr_flush_avx2.S208 # process completed job "idx"
276 # process completed job "idx"
/linux-4.4.14/Documentation/ia64/
Dmca.txt14 The complicated ia64 MCA process. All of this is mandated by Intel's
140 * i386 backtrace is not very sensitive to whether a process is running
141 or not. ia64 unwind is very, very sensitive to whether a process is
154 does not bother making the user space process look like a blocked task,

1234