Searched full:context (Results 1 – 25 of 281) sorted by relevance
12345678910>>...12
| /Documentation/block/ |
| D | inline-encryption.rst | 22 with an encryption context (key, algorithm, data unit size, etc.) at any time.
24 device will en/decrypt the data using the encryption context programmed into
26 the same encryption context share the same keyslot.
28 - We need a way for filesystems to specify an encryption context to use for
30 to use that encryption context when it processes the bio.
40 encryption context, because we need to be able to pass this encryption
41 context from the FS layer to the device driver to act upon.
44 knowledge of keyslots - it simply wants to specify an encryption context to
53 the device's struct request_queue to translate an encryption context into
64 encryption context programmed, or there are no in-flight struct bios
[all …]
|
| /Documentation/filesystems/ |
| D | mount_api.txt | 9 (2) The filesystem context.
11 (3) The filesystem context operations.
13 (4) Filesystem context security.
15 (5) VFS filesystem context API.
30 (1) Create a filesystem context.
32 (2) Parse the parameters and attach them to the context. Parameters are
36 (3) Validate and pre-process the context.
42 (6) Return an error message attached to the context.
44 (7) Destroy the context.
52 context, including the additional space, and the second points to the
[all …]
|
| /Documentation/devicetree/bindings/iommu/ |
| D | qcom,iommu.txt | 5 and optionally requiring additional configuration to route context irqs
27 - #iommu-cells : Must be 1. Index identifies the context-bank #.
29 - ranges : Base address and size of the iommu context banks.
33 - List of sub-nodes, one per translation context bank. Each sub-node
37 - "qcom,msm-iommu-v1-ns" : non-secure context bank
38 - "qcom,msm-iommu-v1-sec" : secure context bank
39 - reg : Base address and size of context bank within the iommu
40 - interrupts : The context fault irq.
46 for routing of context bank irq's to secure vs non-
48 context banks)
|
| /Documentation/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
139 master context and /dev/cxl/afu0.0s will correspond to a slave
[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 …]
|
| /Documentation/infiniband/ |
| D | core_locking.rst | 10 Sleeping and interrupt context
27 which may not sleep and must be callable from any context.
41 are therefore safe to call from any context.
48 the midlayer is also safe to call from any context.
95 The context in which completion event and asynchronous event
97 may be process context, softirq context, or interrupt context.
109 ib_unregister_device() from process context. It must not hold any
|
| /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 | 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/networking/ |
| D | netdevices.txt | 52 Context: process
56 Context: process
61 Context: process
65 Context: nominally process, but don't sleep inside an rwlock
77 Context: Process with BHs disabled or BH (timer),
88 Context: BHs disabled
93 Context: BHs disabled
103 Context: softirq
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | sifive,plic-1.0.0.txt | 9 A hart context is a privilege mode in a hardware execution thread. For example,
13 Each interrupt can be enabled on per-context basis. Any context can claim
17 serviced first. Each context can specify a priority threshold. Interrupts
19 interrupt line leading to the context.
38 with "-1" specifying that a context is not present. Each node pointed
|
| /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/devicetree/bindings/misc/ |
| D | qcom,fastrpc.txt | 31 Each subnode of the Fastrpc represents compute context banks available
33 - All Compute context banks MUST contain the following properties:
43 Definition: Context Bank ID.
49 context bank. Defaults to 1 when this property
|
| /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.
119 a process-context acquisition of this lock must use something
124 If the process-context code were to simply use spin_lock(),
125 then, since RCU callbacks can be invoked from softirq context,
127 the process-context critical section. This would result in
|
| /Documentation/doc-guide/ |
| D | kernel-doc.rst | 77 * Context: Describes whether the function can sleep, what locks it takes,
118 Function context
121 The context in which a function can be called should be described in a
122 section named ``Context``. This should include whether the function
123 sleeps or can be called from interrupt context, as well as what locks
128 * Context: Any context.
129 * Context: Any context. Takes and releases the RCU lock.
130 * Context: Any context. Expects <lock> to be held by caller.
131 * Context: Process context. May sleep if @gfp flags permit.
132 * Context: Process context. Takes and releases <mutex>.
[all …]
|
| /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/vm/ |
| D | active_mm.rst | 28 user-level page tables at all, so when we do a context switch into an
70 more. "init_mm" should be considered just a "lazy context when no other
71 context is available", and in fact it is mainly used just at bootup when
81 we have a user context", and is generally done by the page fault handler
87 ugliest context switch codes - unlike the other architectures where the MM
|
| D | page_frags.rst | 31 main difference between these two calls is the context in which they may be
32 called. The "netdev" prefixed functions are usable in any context as these
34 only usable within the softirq context.
|
| /Documentation/locking/ |
| D | lockdep-design.rst | 45 - 'ever held in STATE context'
46 - 'ever held as readlock in STATE context'
75 '.' acquired while irqs disabled and not in irq context
76 '-' acquired in irq context
78 '?' acquired in irq context with irqs enabled.
85 ||| \-> softirq disabled and not in softirq context
86 || \--> acquired in softirq context
87 | \---> hardirq disabled and not in hardirq context
88 \----> acquired in hardirq context
92 context and whether that STATE is enabled yields four possible cases as
[all …]
|
| /Documentation/translations/it_IT/doc-guide/ |
| D | kernel-doc.rst | 107 * Context: Describes whether the function can sleep, what locks it takes,
153 sezione chiamata ``Context``. Questo dovrebbe informare sulla possibilità
160 * Context: Any context.
161 * Context: Any context. Takes and releases the RCU lock.
162 * Context: Any context. Expects <lock> to be held by caller.
163 * Context: Process context. May sleep if @gfp flags permit.
164 * Context: Process context. Takes and releases <mutex>.
165 * Context: Softirq or process context. Takes and releases <lock>, BH-safe.
166 * Context: Interrupt context.
365 * Context: Locking context.
|
| /Documentation/devicetree/bindings/powerpc/ |
| D | ibm,vas.txt | 11 window context start and length, OS/User window context start and length,
|
| /Documentation/crypto/ |
| D | crypto_engine.rst | 12 You must put, at the start of your transform context your_tfm_ctx, the structure
24 has access to the transform structure. It is not possible to access the context
36 Before transferring any request, you have to fill the context enginectx by
|
| /Documentation/security/ |
| D | credentials.rst | 40 3. The objective context.
43 indicates the 'objective context' of that object. This may or may not be
47 The objective context is used as part of the security calculation that is
61 the file struct will have a subjective context too.
63 5. The subjective context.
66 of its credentials forms the 'subjective context'. The subjective context
72 from the real UID and GID that normally form the objective context of the
87 involves taking the subjective context, the objective context and the
134 derived from Windows). These (mostly) define the objective context of
142 EUID/EGID/GROUPS will be used as the subjective context, and real UID/GID
[all …]
|
| /Documentation/features/time/context-tracking/ |
| D | arch-support.txt | 2 # Feature name: context-tracking
4 # description: arch supports context tracking for NO_HZ_FULL
|
12345678910>>...12