Home
last modified time | relevance | path

Searched refs:process (Results 1 – 25 of 848) sorted by relevance

12345678910>>...34

/Linux-v4.19/drivers/gpu/drm/amd/amdkfd/
Dkfd_process.c206 struct kfd_process *process; in kfd_create_process() local
224 process = find_process(thread); in kfd_create_process()
225 if (process) in kfd_create_process()
228 process = create_process(thread, filep); in kfd_create_process()
232 return process; in kfd_create_process()
237 struct kfd_process *process; in kfd_get_process() local
246 process = find_process(thread); in kfd_get_process()
247 if (!process) in kfd_get_process()
250 return process; in kfd_get_process()
255 struct kfd_process *process; in find_process_by_mm() local
[all …]
Dkfd_doorbell.c129 int kfd_doorbell_mmap(struct kfd_dev *dev, struct kfd_process *process, in kfd_doorbell_mmap() argument
142 address = kfd_get_process_doorbells(dev, process); in kfd_doorbell_mmap()
229 struct kfd_process *process, in kfd_doorbell_id_to_offset() argument
239 process->doorbell_index in kfd_doorbell_id_to_offset()
255 struct kfd_process *process) in kfd_get_process_doorbells() argument
258 process->doorbell_index * kfd_doorbell_process_slice(dev); in kfd_get_process_doorbells()
261 int kfd_alloc_process_doorbells(struct kfd_process *process) in kfd_alloc_process_doorbells() argument
266 process->doorbell_index = r; in kfd_alloc_process_doorbells()
271 void kfd_free_process_doorbells(struct kfd_process *process) in kfd_free_process_doorbells() argument
273 if (process->doorbell_index) in kfd_free_process_doorbells()
[all …]
Dkfd_dbgmgr.c136 if (pmgr->pasid != wac_info->process->pasid) { in kfd_dbgmgr_wave_control()
138 wac_info->process->pasid); in kfd_dbgmgr_wave_control()
149 if (pmgr->pasid != adw_info->process->pasid) { in kfd_dbgmgr_address_watch()
151 adw_info->process->pasid); in kfd_dbgmgr_address_watch()
/Linux-v4.19/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-v4.19/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/
Dgt215.c31 u32 process, u32 message, u32 data0, u32 data1) in gt215_pmu_send() argument
55 pmu->recv.process = process; in gt215_pmu_send()
66 nvkm_wr32(device, 0x10a1c4, process); in gt215_pmu_send()
77 wait_event(pmu->recv.wait, (pmu->recv.process == 0)); in gt215_pmu_send()
91 u32 process, message, data0, data1; in gt215_pmu_recv() local
106 process = nvkm_rd32(device, 0x10a1c4); in gt215_pmu_recv()
116 if (pmu->recv.process) { in gt215_pmu_recv()
117 if (process == pmu->recv.process && in gt215_pmu_recv()
121 pmu->recv.process = 0; in gt215_pmu_recv()
131 (char)((process & 0x000000ff) >> 0), in gt215_pmu_recv()
[all …]
/Linux-v4.19/tools/perf/util/
Dheader.h103 int (*process)(struct perf_file_section *section,
112 perf_event__handler_t process);
116 perf_event__handler_t process,
125 perf_event__handler_t process);
128 perf_event__handler_t process);
131 perf_event__handler_t process);
134 perf_event__handler_t process);
137 perf_event__handler_t process);
140 perf_event__handler_t process);
150 perf_event__handler_t process);
[all …]
Devent.c94 perf_event__handler_t process) in perf_tool__process_synth_event() argument
106 return process(tool, event, &synth_sample, machine); in perf_tool__process_synth_event()
222 perf_event__handler_t process, in perf_event__synthesize_comm() argument
230 if (perf_tool__process_synth_event(tool, event, machine, process) != 0) in perf_event__synthesize_comm()
252 perf_event__handler_t process, in perf_event__synthesize_namespaces() argument
282 if (perf_tool__process_synth_event(tool, event, machine, process) != 0) in perf_event__synthesize_namespaces()
291 perf_event__handler_t process, in perf_event__synthesize_fork() argument
314 if (perf_tool__process_synth_event(tool, event, machine, process) != 0) in perf_event__synthesize_fork()
323 perf_event__handler_t process, in perf_event__synthesize_mmap_events() argument
448 if (perf_tool__process_synth_event(tool, event, machine, process) != 0) { in perf_event__synthesize_mmap_events()
[all …]
Devent.h671 perf_event__handler_t process,
676 perf_event__handler_t process,
680 perf_event__handler_t process,
683 perf_event__handler_t process,
688 perf_event__handler_t process,
692 perf_event__handler_t process,
699 perf_event__handler_t process,
703 perf_event__handler_t process,
706 perf_event__handler_t process,
756 perf_event__handler_t process);
[all …]
/Linux-v4.19/tools/memory-model/litmus-tests/
DREADME26 variable by a different process? This litmus test is forbidden
34 variable by a different process?
38 litmus test is visible to an external process whose accesses are
39 separated by smp_mb(). This addition of an external process to
52 load-buffering litmus test, where each process reads from one
57 litmus test, where each process reads from one of two variables then
69 in one process, and use an acquire load followed by a pair of
70 spin_is_locked() calls in the other process.
73 Protect the access with a lock in one process, and use an
75 in the other process.
[all …]
/Linux-v4.19/Documentation/security/keys/
Drequest-key.rst9 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
78 2) request_key() searches the process's subscribed keyrings to see if there's
80 and callout_info is not set, an error is returned. Otherwise the process
88 b) An authorisation key V that refers to key U and notes that process A
104 This will permit it to then search the keyrings of process A with the
105 UID, GID, groups and security info of process A as if it was process A,
121 context specified by auth key X will still be process A, as it was in auth key
124 This is because process A's keyrings can't simply be attached to
[all …]
/Linux-v4.19/Documentation/translations/ko_KR/
Dhowto.rst2 This is a version of Documentation/process/howto.rst translated into korean
15 Documentation/process/howto.rst
107 :ref:`Documentation/process/changes.rst <changes>`
111 :ref:`Documentation/process/coding-style.rst <codingstyle>`
117 …:ref:`Documentation/process/submitting-patches.rst <submittingpatches>` 와 :ref:`Documentation/proc…
138 :ref:`Documentation/process/stable-api-nonsense.rst <stable_api_nonsense>`
155 :ref:`Documentation/process/management-style.rst <managementstyle>`
163 :ref:`Documentation/process/stable-kernel-rules.rst <stable_kernel_rules>`
168 :ref:`Documentation/process/kernel-docs.rst <kernel_docs>`
173 :ref:`Documentation/process/applying-patches.rst <applying_patches>`
[all …]
/Linux-v4.19/Documentation/translations/ja_JP/
Dhowto.rst2 This is a version of Documentation/process/howto.rst translated into Japanese.
15 Documentation/process/howto.rst
112 :ref:`Documentation/process/changes.rst <changes>`
117 :ref:`Documentation/process/coding-style.rst <codingstyle>`
124 …:ref:`Documentation/process/submitting-patches.rst <codingstyle>` と :ref:`Documentation/process/su…
144 :ref:`Documentation/process/stable-api-nonsense.rst <stable_api_nonsense>`
161 :ref:`Documentation/process/management-style.rst <managementstyle>`
168 :ref:`Documentation/process/stable-kernel-rules.rst <stable_kernel_rules>`
173 :Ref:`Documentation/process/kernel-docs.rst <kernel_docs>`
178 :ref:`Documentation/process/applying-patches.rst <applying_patches>`
[all …]
/Linux-v4.19/Documentation/
Dnumastat.txt10 numa_hit A process wanted to allocate memory from this node,
13 numa_miss A process wanted to allocate memory from another node,
16 numa_foreign A process wanted to allocate on this node,
19 local_node A process ran on this node and got memory from it.
21 other_node A process ran on this node and got memory from another node.
/Linux-v4.19/Documentation/admin-guide/LSM/
DYama.rst14 malware. One particularly troubling weakness of the Linux process
32 parent to a child process (i.e. direct "gdb EXE" and "strace EXE" still
37 between a debugging process and its inferior (crash handlers, etc),
39 other process (and its descendants) are allowed to call ``PTRACE_ATTACH``
40 against it. Only one such declared debugging process can exists for
43 to ptrace each other. If a process wishes to entirely disable these ptrace
45 so that any otherwise allowed process (even those in external pid namespaces)
51 a process can ``PTRACE_ATTACH`` to any other
52 process running under the same uid, as long as it is dumpable (i.e.
58 a process must have a predefined relationship
/Linux-v4.19/Documentation/translations/zh_CN/
DHOWTO1 Chinese translated version of Documentation/process/howto.rst
12 Documentation/process/howto.rst 的中文翻译
96 Documentation/process/changes.rst
99 Documentation/process/coding-style.rst
104 Documentation/process/submitting-patches.rst
105 Documentation/process/submitting-drivers.rst
119 Documentation/process/stable-api-nonsense.rst
132 Documentation/process/management-style.rst
137 Documentation/process/stable-kernel-rules.rst
140 Documentation/process/kernel-docs.rst
[all …]
/Linux-v4.19/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-v4.19/drivers/soc/ux500/
Dux500-soc-id.c32 u8 process; member
119 dbx500_id.process = asicid >> 24; in ux500_setup_id()
153 if (dbx500_id.process == 0x00) in ux500_get_process()
156 return sprintf(buf, "%02xnm\n", dbx500_id.process); in ux500_get_process()
190 __ATTR(process, S_IRUGO, ux500_get_process, NULL);
/Linux-v4.19/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-v4.19/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/fuc/
Dkernel.fuc30 process(PROC_KERN, 0, 0)
137 // $r14 - process
140 // read process' timer status, skip if not enabled
145 // subtract last timer's value from process' timer,
156 // process' timer is the soonest
168 // update process' timer status, and advance
317 // request the current process be sent a message after a timeout expires
329 // if current process already has a timer set, bail
377 // send message to another process
380 // $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!
/Linux-v4.19/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:
/Linux-v4.19/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.
/Linux-v4.19/Documentation/userspace-api/
Dunshare.rst29 as multiple execution contexts within a process. These kernels provide
48 shared resources without creating a new process. unshare() is a natural
50 the concept of process/thread as a virtual machine.
56 where creating a new process to control sharing/unsharing of process
58 when creating a new process using fork or clone, unshare() can benefit
67 the kernel's per-process namespace mechanism. Polyinstantiated directories,
85 decide what needs to be shared at the time of creating the process
89 ability to unshare() after the process was created can be very
126 unshare - disassociate parts of the process execution context
134 unshare() allows a process to disassociate parts of its execution
[all …]
/Linux-v4.19/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 …]

12345678910>>...34