Searched full:userspace (Results 1 – 25 of 7907) sorted by relevance
12345678910>>...317
| /kernel/linux/linux-6.6/Documentation/filesystems/ |
| D | idmappings.rst | 7 reading from or writing ownership to disk, reporting ownership to userspace, or
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
130 A userspace id is always an element in the upper idmapset of an idmapping of
133 "userspace id" will be used to refer to the well known ``uid_t`` and ``gid_t``
138 A userspace id on the other hand is an id that is reported to userspace by the
139 kernel, or is passed by userspace to the kernel, or a raw device id that is
143 how userspace would specify them.
[all …]
|
| /kernel/linux/linux-6.6/drivers/uio/ |
| D | Kconfig | 3 tristate "Userspace I/O drivers"
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
29 tristate "Userspace I/O platform driver with generic IRQ handling"
31 Platform driver for Userspace I/O devices, including generic
34 This kernel driver requires that the matching userspace driver
35 handles interrupts in a special way. Userspace is responsible
42 tristate "Userspace platform driver with generic irq and dynamic memory"
[all …]
|
| /kernel/linux/linux-5.10/drivers/uio/ |
| D | Kconfig | 3 tristate "Userspace I/O drivers"
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
29 tristate "Userspace I/O platform driver with generic IRQ handling"
31 Platform driver for Userspace I/O devices, including generic
34 This kernel driver requires that the matching userspace driver
35 handles interrupts in a special way. Userspace is responsible
42 tristate "Userspace platform driver with generic irq and dynamic memory"
[all …]
|
| /kernel/linux/linux-6.6/Documentation/target/ |
| D | tcmu-design.rst | 2 TCM Userspace Design
30 Existing TCM targets run in the kernel. TCMU (TCM in Userspace)
31 allows userspace programs to be written which act as iSCSI targets.
58 If the target is a userspace process, supporting these is easy. tgt,
60 modules just use the available userspace libraries for RBD and GLFS.
65 kernel, another approach is to create a userspace pass-through
75 (Filesystem in Userspace), but at the SCSI layer instead of the
86 - Cleanly handle if userspace:
96 - Simple to write a userspace backend
103 between kernel and userspace. Within this region is: a control area
[all …]
|
| /kernel/linux/linux-5.10/Documentation/target/ |
| D | tcmu-design.rst | 2 TCM Userspace Design
30 Existing TCM targets run in the kernel. TCMU (TCM in Userspace)
31 allows userspace programs to be written which act as iSCSI targets.
58 If the target is a userspace process, supporting these is easy. tgt,
60 modules just use the available userspace libraries for RBD and GLFS.
65 kernel, another approach is to create a userspace pass-through
75 (Filesystem in Userspace), but at the SCSI layer instead of the
86 - Cleanly handle if userspace:
96 - Simple to write a userspace backend
103 between kernel and userspace. Within this region is: a control area
[all …]
|
| /kernel/linux/linux-6.6/Documentation/infiniband/ |
| D | user_verbs.rst | 2 Userspace verbs access
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.
20 Userspace communicates with the kernel for slow path, resource
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
[all …]
|
| /kernel/linux/linux-5.10/Documentation/infiniband/ |
| D | user_verbs.rst | 2 Userspace verbs access
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.
20 Userspace communicates with the kernel for slow path, resource
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
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/ |
| D | dma-buf.rst | 12 sg_table and exposed to userspace as a file descriptor to allow passing
52 Userspace Interface Notes
55 Mostly a DMA buffer file descriptor is simply an opaque object for userspace,
65 cases. Userspace can use this to detect support for discovering the dma-buf
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().
194 The time this fence completes is entirely under userspace's control.
199 * Userspace fences or gpu futexes, fine-grained locking within a command buffer
200 that userspace uses for synchronization across engines or with the CPU, which
208 Common to all these schemes is that userspace controls the dependencies of these
[all …]
|
| 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.
68 Receiving Sync Files from Userspace
71 When userspace needs to send an in-fence to the driver it passes file descriptor
|
| /kernel/linux/linux-5.10/Documentation/gpu/ |
| D | drm-uapi.rst | 9 addition, drivers export device-specific interfaces for use by userspace
40 Open-Source Userspace Requirements
44 what the userspace side for new uAPI needs to look like. This section here
48 open-sourced userspace patches, and those patches must be reviewed and ready for
52 hardware, with userspace and kernel by necessity having to work together really
56 infeasible to differentiate between behaviour that's required by userspace, and
60 Without access to the full source code of all userspace users that means it
61 becomes impossible to change the implementation details, since userspace could
67 open-source userspace of the DRM subsystem. DRM developers are perfectly fine
68 if closed-source blob drivers in userspace use the same uAPI as the open
[all …]
|
| /kernel/linux/linux-6.6/Documentation/gpu/ |
| D | drm-uapi.rst | 9 addition, drivers export device-specific interfaces for use by userspace
49 Open-Source Userspace Requirements
53 what the userspace side for new uAPI needs to look like. This section here
57 open-sourced userspace patches, and those patches must be reviewed and ready for
61 hardware, with userspace and kernel by necessity having to work together really
65 infeasible to differentiate between behaviour that's required by userspace, and
69 Without access to the full source code of all userspace users that means it
70 becomes impossible to change the implementation details, since userspace could
76 open-source userspace of the DRM subsystem. DRM developers are perfectly fine
77 if closed-source blob drivers in userspace use the same uAPI as the open
[all …]
|
| /kernel/linux/linux-6.6/Documentation/arch/x86/ |
| 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
38 kernels without PTI. This includes a complete mapping of userspace
44 userspace upon executing its first instruction.
46 The userspace page tables map only the kernel data needed to enter
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
[all …]
|
| /kernel/linux/linux-5.10/Documentation/x86/ |
| 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
38 kernels without PTI. This includes a complete mapping of userspace
44 userspace upon executing its first instruction.
46 The userspace page tables map only the kernel data needed to enter
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
[all …]
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/ |
| D | vduse.rst | 2 VDUSE - "vDPA Device in Userspace"
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
99 /dev/vduse/control. With this ioctl, userspace can specify some basic configuration
102 Then a char device interface (/dev/vduse/$NAME) is exported to userspace for device
103 emulation. Userspace can use the VDUSE_VQ_SETUP ioctl on /dev/vduse/$NAME to
107 the VDPA_CMD_DEV_NEW netlink message. Userspace needs to read()/write() on
140 - VDUSE_GET_VQ_STATE: Get the state for virtqueue, userspace should return
144 - VDUSE_SET_STATUS: Set the device status, userspace should follow
[all …]
|
| /kernel/linux/linux-6.6/Documentation/driver-api/ |
| D | dma-buf.rst | 12 sg_table and exposed to userspace as a file descriptor to allow passing
52 Userspace Interface Notes
55 Mostly a DMA buffer file descriptor is simply an opaque object for userspace,
65 cases. Userspace can use this to detect support for discovering the dma-buf
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().
229 The time this fence completes is entirely under userspace's control.
234 * Userspace fences or gpu futexes, fine-grained locking within a command buffer
235 that userspace uses for synchronization across engines or with the CPU, which
243 Common to all these schemes is that userspace controls the dependencies of these
[all …]
|
| 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.
68 Receiving Sync Files from Userspace
71 When userspace needs to send an in-fence to the driver it passes file descriptor
|
| /kernel/linux/linux-6.6/Documentation/networking/ |
| 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
|
| 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
43 flow key that it parsed from the packet. Userspace then extracts its
47 - If userspace's notion of the flow key for the packet matches the
50 - If the kernel's flow key includes more fields than the userspace
52 headers but userspace stopped at the Ethernet type (because it
[all …]
|
| /kernel/linux/linux-5.10/Documentation/networking/ |
| 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
|
| 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
43 flow key that it parsed from the packet. Userspace then extracts its
47 - If userspace's notion of the flow key for the packet matches the
50 - If the kernel's flow key includes more fields than the userspace
52 headers but userspace stopped at the Ethernet type (because it
[all …]
|
| /kernel/linux/linux-6.6/Documentation/accel/qaic/ |
| D | qaic.rst | 56 roll back userspace activity. To ensure that a userspace client's resources
73 QAIC defines a number of driver specific IOCTLs as part of the userspace API.
77 This IOCTL allows userspace to send a NNC request to the QSM. The call will
81 This IOCTL allows userspace to allocate a buffer object (BO) which can send
87 This IOCTL allows userspace to prepare an allocated BO to be mmap'd into the
88 userspace process.
91 This IOCTL allows userspace to slice a BO in preparation for sending the BO
97 This IOCTL allows userspace to submit a set of sliced BOs to the device. The
102 This IOCTL operates like DRM_IOCTL_QAIC_EXECUTE_BO, but it allows userspace
105 allows userspace to indicate that only the first M bytes of the BO should be
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/device-mapper/ |
| D | dm-init.rst | 8 The first is to build an initial ramdisk which boots to a minimal userspace
41 activation of certain DM targets without first using userspace tools to check
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
56 `snapshot-merge` constrained, userspace should verify src/dst device
58 `switch` constrained, userspace should verify dev path
[all …]
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/gpio/ |
| D | sysfs.rst | 1 GPIO Sysfs Interface for Userspace
7 Documentation/ABI/obsolete/sysfs-gpio AND NEW USERSPACE CONSUMERS
12 character device ABI. Also see the userspace header in
23 Given appropriate hardware documentation for the system, userspace could
32 userspace GPIO can be used to determine system configuration data that
33 standard kernels won't know about. And for some tasks, simple userspace
38 TO AVOID REINVENTING KERNEL WHEELS IN USERSPACE. I MEAN IT. REALLY.
44 - Control interfaces used to get userspace control over GPIOs;
57 Userspace may ask the kernel to export control of
58 a GPIO to userspace by writing its number to this file.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/arch/arm64/ |
| D | perf.rst | 18 This attribute excludes userspace.
20 Userspace always runs at EL0 and thus this attribute will exclude EL0.
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).
95 Perf Userspace PMU Hardware Counter Access
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
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/gpio/ |
| D | sysfs.rst | 1 GPIO Sysfs Interface for Userspace
7 Documentation/ABI/obsolete/sysfs-gpio AND NEW USERSPACE CONSUMERS
12 character device ABI. Also see the userspace header in
23 Given appropriate hardware documentation for the system, userspace could
32 userspace GPIO can be used to determine system configuration data that
33 standard kernels won't know about. And for some tasks, simple userspace
38 TO AVOID REINVENTING KERNEL WHEELS IN USERSPACE. I MEAN IT. REALLY.
44 - Control interfaces used to get userspace control over GPIOs;
57 Userspace may ask the kernel to export control of
58 a GPIO to userspace by writing its number to this file.
[all …]
|
12345678910>>...317