Searched full:userspace (Results 1 – 25 of 2780) sorted by relevance
12345678910>>...112
| /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 …]
|
| /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 …]
|
| /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 …]
|
| /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().
189 The time this fence completes is entirely under userspace's control.
194 * Userspace fences or gpu futexes, fine-grained locking within a command buffer
195 that userspace uses for synchronization across engines or with the CPU, which
203 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
|
| /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 …]
|
| /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 …]
|
| /linux-5.10/drivers/dma-buf/ |
| 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.
48 problem where userspace is able to pin unrestricted amounts of memory
64 allows userspace to allocate dma-bufs that can be shared
|
| /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 …]
|
| 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
90 contains link policy. This is needed for userspace interaction
113 real hardware, it is possible to set this bit from userspace. One
143 IF_OPER_UP if userspace interaction is disabled. Otherwise
144 IF_OPER_DORMANT with the possibility for userspace to initiate the
148 4. Setting from userspace
[all …]
|
| D | cdc_mbim.rst | 44 provides a userspace interface to the MBIM control channel, and will
46 userspace MBIM management application always is required to enable a
49 Such userspace applications includes, but are not limited to:
64 The driver <-> userspace interfaces are described below. The MBIM
68 MBIM control channel userspace ABI
74 using the cdc-wdm driver as a subdriver. The userspace end of the
78 channel. The channel is fully delegated to the userspace management
101 The userspace application can access the CDC MBIM functional
110 The userspace application is responsible for all control message
132 userspace.
[all …]
|
| /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 …]
|
| 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-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 …]
|
| /linux-5.10/Documentation/firmware-guide/acpi/ |
| 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-5.10/include/uapi/linux/ |
| D | dm-log-userspace.h | 15 * The device-mapper userspace log module consists of a kernel component and
41 * you will see 'Payload-to-userspace' and 'Payload-to-kernel'. The
42 * 'Payload-to-userspace' is what the kernel sends in 'additional data' as
54 * Payload-to-userspace:
78 * Payload-to-userspace:
97 * Payload-to-userspace:
116 * Payload-to-userspace:
135 * Payload-to-userspace:
154 * Payload-to-userspace:
172 * Payload-to-userspace:
[all …]
|
| /linux-5.10/drivers/infiniband/ |
| D | Kconfig | 19 tristate "InfiniBand userspace MAD support"
22 Userspace InfiniBand Management Datagram (MAD) support. This
23 is the kernel side of the userspace MAD support, which allows
24 userspace processes to send and receive MADs. You will also
29 tristate "InfiniBand userspace access (verbs and CM)"
32 Userspace InfiniBand access support. This enables the
33 kernel side of userspace verbs and the userspace
34 communication manager (CM). This allows userspace processes
|
| /linux-5.10/Documentation/filesystems/ |
| D | orangefs.rst | 7 OrangeFS is an LGPL userspace scale-out parallel storage system. It is ideal
22 * Userspace implementation is easy to install and maintain
87 Userspace Filesystem Source
230 Protocol between Kernel Module and Userspace
234 We'll just refer to the user space part of Orangefs as "userspace"
235 from here on out. Orangefs descends from PVFS, and userspace code
236 still uses PVFS for function and variable names. Userspace typedefs
240 correspond to userspace structures are not typedefed.
242 The kernel module implements a pseudo device that userspace
243 can read from and write to. Userspace can also manipulate the
[all …]
|
| D | fuse.rst | 10 Userspace filesystem:
12 userspace process. The filesystem can be accessed normally through
19 A userspace filesystem mounted by a non-privileged (non-root) user.
40 FUSE is a userspace filesystem framework. It consists of a kernel
41 module (fuse.ko), a userspace library (libfuse.*) and a mount utility
49 The userspace library and utilities are available from the
70 The file descriptor to use for communication between the userspace
95 (userspace) configuration option.
123 userspace or being processed by the filesystem daemon. If there is
140 - If the request is not yet sent to userspace AND the signal is
[all …]
|
| /linux-5.10/Documentation/accounting/ |
| D | taskstats.rst | 7 per-process statistics from the kernel to userspace.
30 To get statistics during a task's lifetime, userspace opens a unicast netlink
35 To obtain statistics for tasks which are exiting, the userspace listener
43 an additional record containing the per-tgid stats is also sent to userspace.
81 the task/process for which userspace wants statistics.
88 the cpumask would be "1-3,5,7-8". If userspace forgets to deregister interest
93 2. Response for a command: sent from the kernel in response to a userspace
121 stats in userspace alone is inefficient and potentially inaccurate (due to lack
128 gets sent to userspace (along with the per-task data).
143 structure. Userspace will use only the fields of the struct that correspond
[all …]
|
| /linux-5.10/Documentation/driver-api/gpio/ |
| 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-5.10/Documentation/virt/kvm/ |
| 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-5.10/fs/fuse/ |
| D | Kconfig | 3 tristate "FUSE (Filesystem in Userspace) support"
7 in a userspace program.
18 If you want to develop a userspace FS, or if you want to use
22 tristate "Character device in Userspace support"
26 implemented in userspace.
28 If you want to develop or use a userspace character device
|
| /linux-5.10/Documentation/w1/ |
| D | w1-netlink.rst | 2 Userspace communication protocol over connector
8 There are three types of messages between w1 core and userspace:
12 2. Userspace commands.
13 3. Replies to userspace commands.
32 userspace command for bus master
35 userspace command for slave device
54 (write and sample data back to userspace)
75 Currently replies to userspace commands are only generated for read
87 Replies to W1_LIST_MASTERS should send a message back to the userspace
190 Sequence number for userspace requests is set by userspace application.
[all …]
|
12345678910>>...112