Searched full:process (Results 1 – 25 of 900) sorted by relevance
12345678910>>...36
| /Documentation/security/keys/ |
| D | request-key.rst | 9 The process starts by either the kernel requesting a service by calling
63 The userspace interface links the key to a keyring associated with the process
73 The Process
78 1) Process A calls request_key() [the userspace syscall calls the kernel
81 2) request_key() searches the process's subscribed keyrings to see if there's
83 and callout_info is not set, an error is returned. Otherwise the process
91 b) An authorisation key V that refers to key U and notes that process A
107 This will permit it to then search the keyrings of process A with the
108 UID, GID, groups and security info of process A as if it was process A,
124 context specified by auth key X will still be process A, as it was in auth key
[all …]
|
| /Documentation/arch/x86/ |
| D | sva.rst | 39 executed in the hardware by SWQ interface, SIOV uses Process Address Space
53 record, and the PASID (process address space ID) of the current process.
64 Process Address Space Tagging
76 - Allocate the PASID, and program the process page-table (%cr3 register) in the
92 The kernel must allocate a PASID on behalf of each process which will use
93 ENQCMD and program it into the new MSR to communicate the process identity to
95 from this process. When a user submits a work descriptor to a device using the
100 entry in IOMMU with the process address used by the CPU (e.g. %cr3 register in
105 process share the same page tables, thus the same MSR value.
110 PASID is initialized as IOMMU_PASID_INVALID (-1) when a process is created.
[all …]
|
| /Documentation/locking/ |
| D | rt-mutex-design.rst | 24 Priority inversion is when a lower priority process executes while a higher
25 priority process wants to run. This happens for several reasons, and
26 most of the time it can't be helped. Anytime a high priority process wants
27 to use a resource that a lower priority process has (a mutex for example),
28 the high priority process must wait until the lower priority process is done
31 priority process is prevented from running by a lower priority process for
36 priority process, C is the lowest, and B is in between. A tries to grab a lock
39 but by doing so, it is in fact preempting A which is a higher priority process.
64 PI is where a process inherits the priority of another process if the other
65 process blocks on a lock owned by the current process. To make this easier
[all …]
|
| /Documentation/admin-guide/LSM/ |
| D | Yama.rst | 14 malware. One particularly troubling weakness of the Linux process
33 parent to a child process (i.e. direct "gdb EXE" and "strace EXE" still
38 between a debugging process and its inferior (crash handlers, etc),
40 other process (and its descendants) are allowed to call ``PTRACE_ATTACH``
41 against it. Only one such declared debugging process can exists for
44 to ptrace each other. If a process wishes to entirely disable these ptrace
46 so that any otherwise allowed process (even those in external pid namespaces)
52 a process can ``PTRACE_ATTACH`` to any other
53 process running under the same uid, as long as it is dumpable (i.e.
59 a process must have a predefined relationship
|
| /Documentation/gpu/amdgpu/ |
| D | flashing.rst | 10 used for the flash process.
12 The IFWI flash process is:
16 3. "Read" from the `psp_vbflash` sysfs file to initiate the flash process.
17 4. Poll the `psp_vbflash_status` sysfs file to determine when the flash process completes.
21 On GPUs that support flashing an updated USB-C PD firmware image, the process
25 …irmware payload stored in `/lib/firmware/amdgpu` to the sysfs file will initiate the flash process.
|
| /Documentation/translations/zh_TW/ |
| D | index.rst | 28 process/development-process
29 process/submitting-patches
30 行爲準則 <process/code-of-conduct>
31 完整開發流程文檔 <process/index>
57 process/license-rules
|
| /Documentation/userspace-api/ |
| D | lsm.rst | 18 process.
24 ``LSM_ATTR_EXEC`` is the security context of the process at the time the
30 ``LSM_ATTR_FSCREATE`` is the security context of the process used when
35 ``LSM_ATTR_KEYCREATE`` is the security context of the process used when
40 ``LSM_ATTR_PREV`` is the security context of the process at the time the
46 ``LSM_ATTR_SOCKCREATE`` is the security context of the process used when
54 Set a security attribute of the current process
60 Get the specified security attributes of the current process
|
| D | unshare.rst | 29 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 …]
|
| /Documentation/accounting/ |
| D | taskstats.rst | 7 per-process statistics from the kernel to userspace.
22 "tgid", "process" and "thread group" are used interchangeably and refer to the
23 tasks that share an mm_struct i.e. the traditional Unix process. Despite the
25 leader - a process is deemed alive as long as it has any task belonging to it.
33 statistics for all tasks of the process (if tgid is specified).
49 send commands and process responses, listen for per-tid/tgid exit data,
81 the task/process for which userspace wants statistics.
112 e) TASKSTATS_TYPE_TGID: contains tgid of process to which task belongs
113 f) TASKSTATS_TYPE_STATS: contains the per-tgid stats for exiting task's process
119 Taskstats provides per-process stats, in addition to per-task stats, since
[all …]
|
| /Documentation/trace/postprocess/ |
| D | trace-pagealloc-postprocess.pl | 10 # --read-procstat If the trace lacks process info, get it from /proc
161 die("Failed to math stat line for process name :: $statline");
176 die("Failed to match stat line process ppid:: $statline");
202 my $process = $1;
207 if ($opt_read_procstat && $process eq '') {
302 # Dump per-process stats
306 # Get the maximum process name
317 …"Process", "Pages", "Pages", "Pages", "Pages", "PCPU", "PCPU", "PCPU", "Fragment", "F…
355 my $process;
359 $process = $process_pid;
[all …]
|
| D | trace-vmscan-postprocess.pl | 8 # --read-procstat If the trace lacks process info, get it from /proc
252 die("Failed to math stat line for process name :: $statline");
283 my $process = $1;
286 if ($process eq "") {
287 $process = $last_procmap{$pid};
288 $process_pid = "$process-$pid";
290 $last_procmap{$pid} = $process;
294 if ($opt_read_procstat && $process eq '') {
461 # Dump per-process stats
465 # Get the maximum process name
[all …]
|
| /Documentation/admin-guide/ |
| D | numastat.rst | 14 Usually preferred node is the one local to the CPU where the process executes,
25 numa_hit A process wanted to allocate memory from this node,
28 numa_miss A process wanted to allocate memory from another node,
31 numa_foreign A process wanted to allocate on this node,
34 local_node A process ran on this node's CPU,
37 other_node A process ran on a different node's CPU
50 heavily. In the current kernel implementation, if a process prefers a
|
| /Documentation/translations/zh_CN/ |
| D | index.rst | 39 process/development-process
40 process/submitting-patches
41 行为准则 <process/code-of-conduct>
43 完整开发流程文档 <process/index>
66 process/license-rules
|
| /Documentation/arch/powerpc/ |
| D | dexcr.rst | 33 state for a process.
42 A process can control its own userspace DEXCR value using the
117 * The status returned by ``PR_PPC_GET_DEXCR`` represents what value the process
122 * The aspect state when starting a process is copied from the parent's state on
127 * The ``*_ONEXEC`` controls do not change the current process's DEXCR.
169 - The process does not have sufficient privilege to perform the operation.
170 For example, clearing NPHIE on exec is a privileged operation (a process
173 This interface allows a process to control its own DEXCR aspects, and also set
174 the initial DEXCR value for any children in its process tree (up to the next
189 ``NT_PPC_HASHKEYR`` is available and exposes the HASHKEYR value of the process
[all …]
|
| D | pmu-ebb.rst | 29 When a PMU EBB occurs it is delivered to the currently running process. As such
34 events, however unless the target process enables EBBs (via mtspr(BESCR)) no
37 This makes it possible for a process to enable EBBs for itself, but not
38 actually configure any events. At a later time another process can come along
39 and attach an EBB event to the process, which will then cause EBBs to be
40 delivered to the first process. It's not clear if this is actually useful.
44 user process. This means once an EBB event is scheduled on the PMU, no non-EBB
48 It is however safe to run 'perf' commands on a process which is using EBBs. The
110 meaningless. Because interrupts are being delivered to the user process the
136 EBB events are not inherited across fork. If the child process wishes to use
|
| /Documentation/translations/zh_CN/process/ |
| D | 5.Posting.rst | 3 :Original: :ref:`Documentation/process/5.Posting.rst <development_posting>`
22 :ref:`Documentation/translations/zh_CN/process/submitting-patches.rst <cn_submittingpatches>`
23 和 :ref:`Documentation/translations/zh_CN/process/submit-checklist.rst <cn_submitchecklist>`。
154 :ref:`Documentation/translations/zh_CN/process/submitting-patches.rst <cn_submittingpatches>`
165 :ref:`Documentation/translations/zh_CN/process/submitting-patches.rst <cn_submittingpatches>`
172 :ref:`Documentation/translations/zh_CN/process/submitting-patches.rst <cn_submittingpatches>`
180 :ref:`Documentation/translations/zh_CN/process/submitting-patches.rst <cn_submittingpatches>`
197 :ref:`Documentation/translations/zh_CN/process/email-clients.rst <cn_email_clients>`
|
| D | development-process.rst | 3 :Original: :ref:`Documentation/process/development-process.rst <development_process_main>`
19 2.Process
|
| D | howto.rst | 5 :Original: :ref:`Documentation/process/howto.rst <process_howto>`
67 :ref:`Documentation/translations/zh_CN/process/license-rules.rst <cn_kernel_licensing>`
90 :ref:`Documentation/process/changes.rst <changes>`
93 :ref:`Documentation/translations/zh_CN/process/coding-style.rst <cn_codingstyle>`
98 :ref:`Documentation/translations/zh_CN/process/submitting-patches.rst <cn_submittingpatches>`
117 :ref:`Documentation/translations/zh_CN/process/stable-api-nonsense.rst <cn_stable_api_nonsense>`
128 :ref:`Documentation/process/security-bugs.rst <securitybugs>`
132 :ref:`Documentation/translations/zh_CN/process/management-style.rst <cn_managementstyle>`
138 :ref:`Documentation/process/stable-kernel-rules.rst <stable_kernel_rules>`
141 :ref:`Documentation/process/kernel-docs.rst <kernel_docs>`
[all …]
|
| /Documentation/translations/zh_TW/process/ |
| D | 5.Posting.rst | 5 :Original: :ref:`Documentation/process/5.Posting.rst <development_posting>`
25 :ref:`Documentation/translations/zh_CN/process/submitting-patches.rst <tw_submittingpatches>`
26 和 :ref:`Documentation/translations/zh_CN/process/submit-checklist.rst <tw_submitchecklist>`。
157 :ref:`Documentation/translations/zh_CN/process/submitting-patches.rst <tw_submittingpatches>`
168 :ref:`Documentation/translations/zh_CN/process/submitting-patches.rst <tw_submittingpatches>`
175 :ref:`Documentation/translations/zh_CN/process/submitting-patches.rst <tw_submittingpatches>`
183 :ref:`Documentation/translations/zh_CN/process/submitting-patches.rst <tw_submittingpatches>`
200 :ref:`Documentation/translations/zh_CN/process/email-clients.rst <tw_email_clients>`
|
| D | howto.rst | 7 :Original: :ref:`Documentation/process/howto.rst <process_howto>`
70 :ref:`Documentation/translations/zh_TW/process/license-rules.rst <tw_kernel_licensing>`
93 :ref:`Documentation/process/changes.rst <changes>`
96 :ref:`Documentation/translations/zh_TW/process/coding-style.rst <tw_codingstyle>`
101 :ref:`Documentation/translations/zh_TW/process/submitting-patches.rst <tw_submittingpatches>`
120 :ref:`Documentation/translations/zh_TW/process/stable-api-nonsense.rst <tw_stable_api_nonsense>`
131 :ref:`Documentation/process/security-bugs.rst <securitybugs>`
135 :ref:`Documentation/translations/zh_TW/process/management-style.rst <tw_managementstyle>`
141 :ref:`Documentation/process/stable-kernel-rules.rst <stable_kernel_rules>`
144 :ref:`Documentation/process/kernel-docs.rst <kernel_docs>`
[all …]
|
| /Documentation/mm/ |
| D | page_migration.rst | 6 nodes in a NUMA system while the process is running. This means that the
7 virtual addresses that the process sees do not change. However, the
14 by moving pages near to the processor where the process accessing that memory
17 Page migration allows a process to manually relocate the node on which its
19 a new memory policy via mbind(). The pages of a process can also be relocated
20 from another process using the sys_migrate_pages() function call. The
22 process that are located on the from nodes to the destination nodes.
28 pages of a process are located. See also the numa_maps documentation in the
32 a process to a processor on a distant node. A batch scheduler or an
33 administrator may detect the situation and move the pages of the process
[all …]
|
| /Documentation/ |
| D | index.rst | 25 Development process <process/development-process>
26 Submitting patches <process/submitting-patches>
27 Code of conduct <process/code-of-conduct>
29 All development-process docs <process/index>
54 Licensing rules <process/license-rules>
|
| /Documentation/driver-api/rapidio/ |
| D | rapidio.rst | 126 several methods to initiate an enumeration and/or discovery process:
128 (a) Statically linked enumeration and discovery process can be started
138 expires the discovery process is terminated without obtaining RapidIO network
139 information. NOTE: a timed out discovery process may be restarted later using
143 (b) Statically linked enumeration and discovery process can be started by
146 endpoints have been successfully booted, an enumeration process shall be
148 completed a discovery process can be started on all remaining endpoints.
150 (c) Modular enumeration and discovery process can be started by a command from
152 process can be started by issuing a user-space command.
155 (d) Modular enumeration and discovery process can be started by a module
[all …]
|
| /Documentation/block/ |
| D | ioprio.rst | 9 The io priority feature enables users to io nice processes or process groups,
18 determine how io is 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::
|
| /Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-image-process.rst | 3 .. _image-process-controls:
6 Image Process Control Reference
9 The Image Process control class is intended for low-level control of
15 .. _image-process-control-id:
17 Image Process Control IDs
|
12345678910>>...36