Searched full:context (Results 1 – 25 of 399) sorted by relevance
12345678910>>...16
| /Documentation/arch/powerpc/ |
| D | cxlflash.rst | 56 concept of a master context. A master typically has special privileges
63 The CXL Flash Adapter Driver establishes a master context with the
69 | (per context) |
72 | 512 * 128 B per context |
83 areas in the MMIO Space shown above. The master context driver
92 This master context driver also provides a series of ioctls for this
153 This ioctl obtains, initializes, and starts a context using the CXL
154 kernel services. These services specify a context id (u16) by which
155 to uniquely identify the context and its allocated resources. The
165 There are a few important aspects regarding the "tokens" (context id
[all …]
|
| D | cxl.rst | 17 Coherent in this context means that the accelerator and CPUs can
62 the fault. The context to which this fault is serviced is based on
85 When using dedicated mode only one MMU context is supported. In
92 support fewer). In this mode, the AFU sends a 16 bit context ID
93 with each of its requests. This tells the PSL which context is
96 determine the userspace context associated with an operation.
104 just a per context portion. The hardware is self describing, hence
105 the kernel can determine the offset and size of the per context
123 The WED is a 64-bit parameter passed to the AFU when a context is
140 master context and /dev/cxl/afu0.0s will correspond to a slave
[all …]
|
| /Documentation/filesystems/ |
| D | mount_api.rst | 11 (2) The filesystem context.
13 (3) The filesystem context operations.
15 (4) Filesystem context security.
17 (5) VFS filesystem context API.
31 (1) Create a filesystem context.
33 (2) Parse the parameters and attach them to the context. Parameters are
37 (3) Validate and pre-process the context.
43 (6) Return an error message attached to the context.
45 (7) Destroy the context.
53 context, including the additional space, and the second points to the
[all …]
|
| /Documentation/userspace-api/ |
| D | unshare.rst | 63 2.1 Per-security context namespaces
68 such as per-user and/or per-security context instance of /tmp, /var/tmp or
69 per-security context instance of a user's home directory, isolate user
87 disassociate parts of the context during the servicing of the
115 allowed incremental context unsharing in future without an ABI change.
118 new context flags without requiring a rebuild of old applications.
119 If and when new context flags are added, unshare() design should allow
126 unshare - disassociate parts of the process execution context
135 context that are currently being shared with other processes. Part
136 of execution context, such as the namespace, is shared by default
[all …]
|
| D | lsm.rst | 17 ``LSM_ATTR_CURRENT`` is the current, active security context of the
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
41 current security context was set.
46 ``LSM_ATTR_SOCKCREATE`` is the security context of the process used when
|
| /Documentation/infiniband/ |
| D | core_locking.rst | 10 Sleeping and interrupt context
26 which may not sleep and must be callable from any context.
39 are therefore safe to call from any context.
46 the midlayer is also safe to call from any context.
93 The context in which completion event and asynchronous event
95 may be process context, softirq context, or interrupt context.
107 ib_unregister_device() from process context. It must not hold any
|
| /Documentation/trace/ |
| D | timerlat-tracer.rst | 34 # TASK-PID CPU# |||| TIMESTAMP ID CONTEXT LATENCY
36 <idle>-0 [000] d.h1 54.029328: #1 context irq timer_latency 932 ns
37 <...>-867 [000] .... 54.029339: #1 context thread timer_latency 11700 ns
38 <idle>-0 [001] dNh1 54.029346: #1 context irq timer_latency 2833 ns
39 <...>-868 [001] .... 54.029353: #1 context thread timer_latency 9820 ns
40 <idle>-0 [000] d.h1 54.030328: #2 context irq timer_latency 769 ns
41 <...>-867 [000] .... 54.030330: #2 context thread timer_latency 3070 ns
42 <idle>-0 [001] d.h1 54.030344: #2 context irq timer_latency 935 ns
43 <...>-868 [001] .... 54.030347: #2 context thread timer_latency 4351 ns
48 observed at the *hardirq* context before the activation of the thread.
[all …]
|
| /Documentation/core-api/ |
| D | gfp_mask-from-fs-io.rst | 4 GFP masks used from FS/IO context
17 transaction context).
31 Since 4.12 we do have a generic scope API for both NOFS and NOIO context
45 lock shared with the reclaim context or when a transaction context
48 explanation what is the reclaim context for easier maintenance.
66 any problems. Sometimes if the context is not really clear or there are
|
| D | entry.rst | 9 * RCU / Context tracking
51 Invoking non-instrumentable functions from instrumentable context has no
85 * RCU / Context tracking
99 * RCU / Context tracking
108 Do not nest syscalls. Nested systcalls will cause RCU and/or context tracking
139 interrupt is raised in the context of the CPU's idle task. Otherwise, RCU will
183 before it handles soft interrupts, whose handlers must run in BH context rather
184 than irq-disabled context. In addition, irqentry_exit() might schedule, which
201 interrupts, etc.) can hit any context and must be extra careful with
217 * RCU / Context tracking
[all …]
|
| D | local_ops.rst | 42 making sure that we modify it from within a preemption safe context. It is
68 * This CPU can use local ops from any context (process, irq, softirq, nmi, ...)
71 process context to make sure the process won't be migrated to a
74 * When using local ops in interrupt context, no special care must be
103 In preemptible context, use ``get_cpu_var()`` and ``put_cpu_var()`` around
110 If you are already in a preemption-safe context, you can use
156 /* Increment the counter from a non preemptible context */
161 * preemptible context (it disables preemption) :
|
| /Documentation/translations/zh_CN/doc-guide/ |
| D | kernel-doc.rst | 69 * Context: 描述函数是否可以休眠, 它需要、释放或期望持有什么锁.
107 可调用函数的上下文应该在 ``Context`` 节中描述。此节应该包括函数是休眠的还是
113 * Context: Any context.
114 * Context: Any context. Takes and releases the RCU lock.
115 * Context: Any context. Expects <lock> to be held by caller.
116 * Context: Process context. May sleep if @gfp flags permit.
117 * Context: Process context. Takes and releases <mutex>.
118 * Context: Softirq or process context. Takes and releases <lock>, BH-safe.
119 * Context: Interrupt context.
306 * Context: 锁（Locking）上下文.
|
| /Documentation/networking/ |
| D | netdevices.rst | 36 in context where ``rtnl_lock`` is not held (e.g. driver probe and remove paths).
89 Registering struct net_device while in context which already holds
214 Context: process
218 Context: process
223 Context: process
231 Context: process
238 Context: process
245 Context: process
252 Context: process
256 Context: atomic (can't sleep under RCU)
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | kcopyd.rst | 30 completion callback routine, and a pointer to some context data for the copy::
34 unsigned int flags, kcopyd_notify_fn fn, void *context);
37 void *context);
40 passing back the user's context pointer. It will also indicate if a read or
|
| D | dm-io.rst | 35 io_notify_fn fn, void *context);
46 io_notify_fn fn, void *context);
56 void *data, io_notify_fn fn, void *context);
59 callback routine and a pointer to some context data for the I/O::
61 typedef void (*io_notify_fn)(unsigned long error, void *context);
|
| /Documentation/RCU/ |
| D | UP.rst | 19 elements A, B, and C in process context, and can delete elements from
20 this same list in softirq context. Suppose that the process-context scan
38 from process context. However, this can fail in a similar manner.
41 elements A, B, and C in process context, but that it invokes a function
128 a process-context acquisition of this lock must use something
133 If the process-context code were to simply use spin_lock(),
134 then, since RCU callbacks can be invoked from softirq context,
136 the process-context critical section. This would result in
|
| /Documentation/filesystems/spufs/ |
| D | spu_create.rst | 9 spu_create - create a new spu context
26 Processor Units (SPUs). It creates a new logical context for an SPU in
35 pointing either inside of the context directory or to this file
36 descriptor is closed, the logical SPU context is destroyed.
67 EEXIST An SPU context already exists at the given path name.
88 context or the user specific limit for the number of SPU con-
|
| /Documentation/mhi/ |
| D | mhi.rst | 40 Event Doorbell array: Associated with event context array, the Event Doorbell
55 Channel context array: All channel configurations are organized in channel
56 context data array.
61 Event context array: All event configurations are organized in the event context
67 Command context array: All command configurations are organized in command
68 context data array.
105 channel context.
132 channel context.
195 * Allocates the MHI context for event, channel and command arrays.
196 * Initializes the context array, and prepares interrupts.
|
| /Documentation/driver-api/nfc/ |
| D | nfc-hci.rst | 23 context blocks waiting for response) or asynchronously (the response is returned
24 from HCI Rx context).
123 This must be done from a context that can sleep.
219 - Syscall context from a userspace call (SYSCALL)
232 The API must be invoked from a context that can sleep. Most of the time, this
233 will be the syscall context. skb will return the result that was received in
241 MSGTXWQ context will then be scheduled and invoke nfc_hci_msg_tx_work().
246 SMW context gets scheduled and invokes nfc_shdlc_sm_work(). This function
252 HCI Responses are dispatched immediately from this context to unblock
255 The completion callback will then wake the syscall context.
[all …]
|
| /Documentation/doc-guide/ |
| D | kernel-doc.rst | 83 * Context: Describes whether the function can sleep, what locks it takes,
124 Function context
127 The context in which a function can be called should be described in a
128 section named ``Context``. This should include whether the function
129 sleeps or can be called from interrupt context, as well as what locks
134 * Context: Any context.
135 * Context: Any context. Takes and releases the RCU lock.
136 * Context: Any context. Expects <lock> to be held by caller.
137 * Context: Process context. May sleep if @gfp flags permit.
138 * Context: Process context. Takes and releases <mutex>.
[all …]
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | sifive,plic-1.0.0.yaml | 17 A hart context is a privilege mode in a hardware execution thread. For example,
21 Each interrupt can be enabled on per-context basis. Any context can claim
25 serviced first. Each context can specify a priority threshold. Interrupts
27 interrupt line leading to the context.
95 that a context is not present. Each node pointed to should be a
|
| /Documentation/mm/ |
| D | active_mm.rst | 32 user-level page tables at all, so when we do a context switch into an
74 more. "init_mm" should be considered just a "lazy context when no other
75 context is available", and in fact it is mainly used just at bootup when
85 we have a user context", and is generally done by the page fault handler
91 ugliest context switch codes - unlike the other architectures where the MM
|
| D | page_frags.rst | 29 main difference between these two calls is the context in which they may be
30 called. The "netdev" prefixed functions are usable in any context as these
32 only usable within the softirq context.
|
| /Documentation/translations/it_IT/doc-guide/ |
| D | kernel-doc.rst | 110 * Context: Describes whether the function can sleep, what locks it takes,
156 sezione chiamata ``Context``. Questo dovrebbe informare sulla possibilità
163 * Context: Any context.
164 * Context: Any context. Takes and releases the RCU lock.
165 * Context: Any context. Expects <lock> to be held by caller.
166 * Context: Process context. May sleep if @gfp flags permit.
167 * Context: Process context. Takes and releases <mutex>.
168 * Context: Softirq or process context. Takes and releases <lock>, BH-safe.
169 * Context: Interrupt context.
368 * Context: Locking context.
|
| /Documentation/netlink/specs/ |
| D | binder.yaml | 25 name: context
27 doc: The binder context where the transaction occurred.
80 - context
|
| /Documentation/bpf/ |
| D | bpf_prog_run.rst | 20 can be used to unit test BPF programs against user-supplied context objects, and
43 When using the ``BPF_PROG_RUN`` command, userspace supplies an input context
79 - Userspace can supply an ifindex as part of the context object, just like in
81 packet arrived on this interface; i.e., the ``ingress_ifindex`` of the context
86 because the program execution is not happening in driver context, an
114 pointers (``data``, ``data_end`` and ``data_meta``) in the context object will
|
12345678910>>...16