| /linux-6.3-rc2/Documentation/filesystems/ |
| A D | idmappings.rst | 16 in userspace is::
81 ``(uid_t)-1`` or overflowgid ``(gid_t)-1`` to userspace.
126 of userspace ids into a range of kernel ids::
128 userspace-id:kernel-id:range
138 A userspace id on the other hand is an id that is reported to userspace by the
143 how userspace would specify them.
280 respective userspace idmapsets.
319 /* INVALID: Map the userspace id up into a userspace id in the second idmapping. */
330 /* Map the userspace id down into a kernel id. */
333 /* Map the kernel id up into a userspace id. */
[all …]
|
| /linux-6.3-rc2/Documentation/networking/ |
| A D | mac80211-auth-assoc-deauth.txt | 9 participant userspace
14 userspace->mac80211: authenticate
44 mac80211->userspace: RX auth frame
48 userspace->mac80211: associate
71 mac80211->userspace: associated
73 note left of userspace: associated now
76 note over userspace
80 userspace->mac80211: authorized
84 userspace->mac80211: deauthenticate/disassociate
95 mac80211->userspace: disconnected
|
| A D | operstates.rst | 22 Thanks to 802.1X, userspace must be granted the possibility to
26 and changeable from userspace under certain rules.
29 2. Querying from userspace
35 important for setting from userspace.
59 Interface is in unknown state, neither driver nor userspace has set
92 contains link policy. This is needed for userspace interaction
115 real hardware, it is possible to set this bit from userspace. One
145 IF_OPER_UP if userspace interaction is disabled. Otherwise
146 IF_OPER_DORMANT with the possibility for userspace to initiate the
150 4. Setting from userspace
[all …]
|
| A D | openvswitch.rst | 7 The Open vSwitch kernel module allows flexible userspace control over
16 table" that userspace populates with "flows" that map from keys based
24 no match, it queues the packet to userspace for processing (as part of
25 its processing, userspace will likely set up a flow to handle further
38 to Open vSwitch is designed to allow carefully written userspace
42 kernel module passes a packet to userspace, it also passes along the
52 headers but userspace stopped at the Ethernet type (because it
57 - If the userspace flow key includes more fields than the
58 kernel's, for example if userspace decoded an IPv6 header but
59 the kernel stopped at the Ethernet type, then userspace can
[all …]
|
| /linux-6.3-rc2/Documentation/admin-guide/device-mapper/ |
| A D | dm-init.rst | 8 The first is to build an initial ramdisk which boots to a minimal userspace
45 `cache` constrained, userspace should verify cache device
48 `era` constrained, userspace should verify metadata device
51 `log-writes` constrained, userspace should verify metadata device
52 `mirror` constrained, userspace should verify main/mirror device
53 `raid` constrained, userspace should verify metadata device
54 `snapshot` constrained, userspace should verify src/dst device
58 `switch` constrained, userspace should verify dev path
59 `thin` constrained, requires dm target message from userspace
60 `thin-pool` constrained, requires dm target message from userspace
[all …]
|
| A D | dm-log.rst | 25 userspace drivers/md/dm-log-userspace* include/linux/dm-log-userspace.h
40 The "userspace" log type
42 This log type simply provides a way to export the log API to userspace,
44 logging requests to userspace, where a daemon receives and processes the
47 The structure used for communication between kernel and userspace are
48 located in include/linux/dm-log-userspace.h. Due to the frequency,
50 kernel and userspace, 'connector' is used as the interface for
53 There are currently two userspace log implementations that leverage this
|
| /linux-6.3-rc2/Documentation/infiniband/ |
| A D | user_verbs.rst | 6 enables direct userspace access to IB hardware via "verbs," as
13 userspace driver for your InfiniBand hardware. For example, to use
15 libmthca userspace driver be installed.
23 directly to hardware registers mmap()ed into userspace, with no
30 Status is returned to userspace as the return value of the write()
38 of which resources are attached to a given userspace context. The
40 between kernel pointers and opaque userspace handles, so that kernel
41 pointers are never exposed to userspace and userspace cannot trick
50 Direct userspace I/O requires that memory regions that are potential
73 and so on. Since the InfiniBand userspace verbs should be safe for
|
| /linux-6.3-rc2/Documentation/networking/device_drivers/wwan/ |
| A D | t7xx.rst | 20 WWAN port userspace interfaces representing MBIM & AT control channels and does
21 not play any role in managing their functionality. It is the job of a userspace
24 Examples of few such userspace applications are:
44 The driver and userspace interfaces are described below. The MBIM protocol is
47 MBIM control channel userspace ABI
53 MBIM WWAN Port. The userspace end of the control channel pipe is a
59 The userspace application is responsible for all control message fragmentation
72 MBIM data channel userspace ABI
81 The userspace management application is responsible for creating new IP link
91 AT port userspace ABI
[all …]
|
| A D | iosm.rst | 19 userspace interface MBIM "WWAN PORT" representing MBIM control channel and does
20 not play any role in managing the functionality. It is the job of a userspace
23 Examples of few such userspace application are:
36 The driver and userspace interfaces are described below. The MBIM protocol is
39 MBIM control channel userspace ABI
45 MBIM WWAN Port. The userspace end of the control channel pipe is a
51 The userspace application is responsible for all control message fragmentation
64 MBIM data channel userspace ABI
74 The userspace management application is responsible for creating new IP link
|
| /linux-6.3-rc2/drivers/s390/crypto/ |
| A D | zcrypt_api.h | 79 long (*send_cprb)(bool userspace, struct zcrypt_queue *, struct ica_xcRB *,
81 long (*send_ep11_cprb)(bool userspace, struct zcrypt_queue *, struct ep11_urb *,
166 static inline unsigned long z_copy_from_user(bool userspace, in z_copy_from_user() argument
171 if (likely(userspace)) in z_copy_from_user()
177 static inline unsigned long z_copy_to_user(bool userspace, in z_copy_to_user() argument
182 if (likely(userspace)) in z_copy_to_user()
|
| /linux-6.3-rc2/Documentation/ABI/testing/ |
| A D | debugfs-scmi | 9 Users: Debugging, any userspace test suite
20 Users: Debugging, any userspace test suite
28 Users: Debugging, any userspace test suite
36 Users: Debugging, any userspace test suite
44 Users: Debugging, any userspace test suite
52 Users: Debugging, any userspace test suite
61 Users: Debugging, any userspace test suite
70 Users: Debugging, any userspace test suite
|
| /linux-6.3-rc2/Documentation/driver-api/ |
| A D | sync_file.rst | 13 to/from userspace. It enables userspace to do explicit fencing, where instead
15 driver) sends the fence related to the buffer to userspace via a sync_file.
23 Sync files allows userspace awareness on buffer sharing synchronization between
32 Sync files can go either to or from userspace. When a sync_file is sent from
33 the driver to userspace we call the fences it contains 'out-fences'. They are
40 userspace we call these fence(s) 'in-fences'. Receiving in-fences means that
47 When a driver needs to send an out-fence userspace it creates a sync_file.
63 The sync_file fd now can be sent to userspace.
71 When userspace needs to send an in-fence to the driver it passes file descriptor
|
| A D | dma-buf.rst | 12 sg_table and exposed to userspace as a file descriptor to allow passing
80 To avoid this problem, userspace must have a way to request O_CLOEXEC
83 userspace control setting of O_CLOEXEC flag passed in to dma_buf_fd().
217 The time this fence completes is entirely under userspace's control.
234 protect against malicious userspace:
255 userspace [label="userspace controlled fences"]
256 kernel -> userspace [label="memory management"]
257 userspace -> kernel [label="Future fence, fence proxy, ..."]
259 { rank=same; kernel userspace }
276 userspace is allowed to use userspace fencing or long running compute
[all …]
|
| /linux-6.3-rc2/drivers/dma-buf/ |
| A D | Kconfig | 10 userspace. It enables send/receive 'struct dma_fence' objects to/from
11 userspace via Sync File fds for synchronization between drivers via
12 userspace components. It has been ported from Android.
16 is attached to the buffer and is transferred via userspace, using Sync
31 drivers from userspace. Intended for test and debug only.
34 bool "userspace dmabuf misc driver"
39 A driver to let userspace turn memfd regions into dma-bufs.
49 problem where userspace is able to pin unrestricted amounts of memory
74 allows userspace to allocate dma-bufs that can be shared
|
| /linux-6.3-rc2/drivers/connector/ |
| A D | Kconfig | 4 tristate "Connector - unified userspace <-> kernelspace linker"
7 This is unified userspace <-> kernelspace connector working on top
16 bool "Report process events to userspace"
20 Provide a connector that reports process events to userspace. Send
|
| /linux-6.3-rc2/Documentation/firmware-guide/acpi/ |
| A D | acpi-lid.rst | 49 Exceptions for the userspace users of the ACPI lid device driver
52 The ACPI button driver exports the lid state to the userspace via the
59 it is advised for the userspace program to not to solely rely on this file
62 The ACPI button driver emits the following input event to the userspace:
66 triggered events to the userspace. However, given the fact that the buggy
70 If the userspace hasn't been prepared to ignore the unreliable "opened"
84 This option is the default behavior during the period the userspace
96 If the userspace has been prepared to ignore the unreliable "opened" events
104 to the userspace by always pairing "closed" input events with complement
106 notifications can be delivered to the userspace when the lid is actually
[all …]
|
| /linux-6.3-rc2/Documentation/driver-api/gpio/ |
| A D | using-gpio.rst | 20 In Linux GPIO lines also have a userspace ABI.
22 The userspace ABI is intended for one-off deployments. Examples are prototypes,
33 from userspace will likely be a good fit for using GPIO lines from userspace as
36 Do not under any circumstances abuse the GPIO userspace ABI to cut corners in
39 any circumstances deploy any uniform products using GPIO from userspace.
41 The userspace ABI is a character device for each GPIO hardware unit (GPIO chip).
43 ``/dev/gpiochipN``. Examples of how to directly use the userspace ABI can be
|
| /linux-6.3-rc2/Documentation/virt/acrn/ |
| A D | introduction.rst | 10 ACRN userspace is an application running in the Service VM that emulates
13 hypervisor services to the ACRN userspace.
22 | |ACRN userspace| | | | |
35 ACRN userspace allocates memory for the User VM, configures and initializes the
40 interface (/dev/acrn_hsm) to userspace.
|
| /linux-6.3-rc2/Documentation/userspace-api/ |
| A D | vduse.rst | 9 possible to implement software-emulated vDPA devices in userspace. And
12 implemented in the userspace.
15 which can reduce security risks when the userspace process that implements
140 - VDUSE_GET_VQ_STATE: Get the state for virtqueue, userspace should return
144 - VDUSE_SET_STATUS: Set the device status, userspace should follow
150 - VDUSE_UPDATE_IOTLB: Notify userspace to update the memory mapping for specified
151 IOVA range, userspace should firstly remove the old mapping, then setup the new
154 After DRIVER_OK status bit is set via the VDUSE_SET_STATUS message, userspace is
162 can be mapped into userspace. Some sample codes is shown below:
222 ioctl. The kick eventfd is used by VDUSE kernel module to notify userspace to
[all …]
|
| /linux-6.3-rc2/Documentation/virt/kvm/s390/ |
| A D | s390-diag.rst | 20 userspace.
33 The supported DIAGNOSE function codes vary by the userspace used. For
45 virtio subfunctions depend on KVM's userspace. Generally, userspace
53 Handled by userspace.
56 Handled by userspace.
59 Handled by userspace.
62 Handled by either userspace or KVM (ioeventfd case).
84 This function code is handled by userspace.
|
| /linux-6.3-rc2/Documentation/target/ |
| A D | tcmu-design.rst | 31 allows userspace programs to be written which act as iSCSI targets.
65 kernel, another approach is to create a userspace pass-through
86 - Cleanly handle if userspace:
96 - Simple to write a userspace backend
131 version - 1 (userspace should abort if otherwise)
148 Modified by userspace to indicate when it has completed
160 processed by userspace.
165 flags fields for setting by the kernel (kflags) and userspace
182 When completing a command, userspace sets rsp.scsi_status, and
191 ring, userspace need to update the cmd->id when completing the
[all …]
|
| /linux-6.3-rc2/Documentation/x86/ |
| A D | pti.rst | 15 page tables for use only when running userspace applications. When
20 The userspace page tables contain only a minimal amount of kernel
44 userspace upon executing its first instruction.
51 For new userspace mappings, the kernel makes the entries in its
55 userspace page tables' PGD.
59 userspace page tables to manage. One PTE to lock, one set of
87 things into the userspace page tables. The downside is
90 mapped into both kernel and userspace page tables. This
104 e. The userspace page tables must be populated for each new
114 and userspace copies always map the same userspace
[all …]
|
| /linux-6.3-rc2/Documentation/gpu/ |
| A D | drm-uapi.rst | 9 addition, drivers export device-specific interfaces for use by userspace
53 what the userspace side for new uAPI needs to look like. This section here
82 - Any new userspace interface must have an open-source implementation as
101 sufficiently documented and validated for userspace's consumption.
132 userspace. With KMS, the control node was introduced. However, the
193 graphics stack: from kernel and userspace drivers, through display
200 In other words, from userspace perspective everything needs to keep on
201 working more or less, until userspace stops using the disappeared DRM
244 force-signalled to avoid inflicting hangs on userspace.
251 driver-specific ioctls and handling those in userspace drivers, or
[all …]
|
| /linux-6.3-rc2/drivers/uio/ |
| A D | Kconfig | 6 Enable this to allow the userspace driver core code to be
7 built. This code allows userspace programs easy access to
9 to be written in userspace. Note that a small kernel driver
21 driver requires a userspace component called cif that handles
34 This kernel driver requires that the matching userspace driver
80 Automata GmbH. The userspace part of this driver will be
102 This driver requires a userspace component that comes with the card
123 together with the userspace netX stack from Hilscher.
151 A sample userspace application using this driver is available
165 to network and storage devices from userspace.
[all …]
|
| /linux-6.3-rc2/Documentation/arm64/ |
| A D | perf.rst | 18 This attribute excludes userspace.
59 The KVM host may run at EL0 (userspace), EL1 (non-VHE kernel) and EL2 (VHE
62 The KVM guest may run at EL0 (userspace) and EL1 (kernel).
100 The perf userspace tool relies on the PMU to monitor events. It offers an
103 Arm64 allows userspace tools to have access to the registers storing the
112 registers is enabled and that the userspace has access to the relevant
132 The userspace access is supported in libperf using the perf_evsel__mmap()
138 On heterogeneous systems such as big.LITTLE, userspace PMU counter access can
145 correctly from userspace:
154 counter along with userspace access. The sys_perf_event_open syscall will fail
[all …]
|