| /linux-6.12.1/drivers/cpufreq/ |
| D | cpufreq_userspace.c | 34 struct userspace_policy *userspace = policy->governor_data; in cpufreq_set() local
38 mutex_lock(&userspace->mutex); in cpufreq_set()
39 if (!userspace->is_managed) in cpufreq_set()
42 userspace->setspeed = freq; in cpufreq_set()
46 mutex_unlock(&userspace->mutex); in cpufreq_set()
57 struct userspace_policy *userspace; in cpufreq_userspace_policy_init() local
59 userspace = kzalloc(sizeof(*userspace), GFP_KERNEL); in cpufreq_userspace_policy_init()
60 if (!userspace) in cpufreq_userspace_policy_init()
63 mutex_init(&userspace->mutex); in cpufreq_userspace_policy_init()
65 policy->governor_data = userspace; in cpufreq_userspace_policy_init()
[all …]
|
| /linux-6.12.1/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 …]
|
| 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 …]
|
| /linux-6.12.1/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-6.12.1/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-6.12.1/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-6.12.1/Documentation/sound/ |
| D | utimers.rst | 4 Userspace-driven timers
12 This document describes the userspace-driven timers: virtual ALSA timers
13 which could be created and controlled by userspace applications using
21 Enabling userspace-driven timers
24 The userspace-driven timers could be enabled in the kernel using the
28 Userspace-driven timers API
31 Userspace application can create a userspace-driven ALSA timer by
50 passing the timer to ``snd-aloop`` kernel module or other userspace
51 applications. There could be up to 128 userspace-driven timers in the
96 Userspace-driven timers and snd-aloop
[all …]
|
| /linux-6.12.1/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 …]
|
| /linux-6.12.1/Documentation/driver-api/ |
| D | dma-buf.rst | 16 - dma-buf, representing a sg_table and exposed to userspace as a file
26 Userspace API principles and use
30 see Documentation/userspace-api/dma-buf-alloc-exchange.rst.
68 Userspace Interface Notes
71 Mostly a DMA buffer file descriptor is simply an opaque object for userspace,
81 cases. Userspace can use this to detect support for discovering the dma-buf
96 To avoid this problem, userspace must have a way to request O_CLOEXEC
99 userspace control setting of O_CLOEXEC flag passed in to dma_buf_fd().
245 The time this fence completes is entirely under userspace's control.
250 * Userspace fences or gpu futexes, fine-grained locking within a command buffer
[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-6.12.1/Documentation/networking/device_drivers/wwan/ |
| 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 provides sysfs interfaces to userspace.
48 The sysfs interface provides userspace with access to the device mode, this interface
60 Read from userspace to get the current device mode.
65 Write from userspace to set the device mode.
72 The driver and userspace interfaces are described below. The MBIM protocol is
75 MBIM control channel userspace ABI
81 MBIM WWAN Port. The userspace end of the control channel pipe is a
[all …]
|
| /linux-6.12.1/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 …]
|
| /linux-6.12.1/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
88 mapped into both kernel and userspace page tables. This
100 deferred until the exit to userspace, minimizing the cost.
[all …]
|
| /linux-6.12.1/Documentation/networking/ |
| 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 | 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
|
| /linux-6.12.1/Documentation/block/ |
| D | ublk.rst | 4 Userspace block device driver (ublk driver)
10 ublk is a generic framework for implementing block device logic from userspace.
11 The motivation behind it is that moving virtual block drivers into userspace,
16 Userspace block devices are attractive because:
29 on the device will be forwarded to ublk userspace program. For convenience,
30 in this document, ``ublk server`` refers to generic ublk userspace
31 program. ``ublksrv`` [#userspace]_ is one of such implementation. It
34 included, such as loop and null. Richard W.M. Jones wrote userspace nbd device
37 After the IO is handled by userspace, the result is committed back to the
39 logic is totally done by userspace, such as loop's IO handling, NBD's IO
[all …]
|
| /linux-6.12.1/Documentation/accel/qaic/ |
| D | qaic.rst | 79 roll back userspace activity. To ensure that a userspace client's resources
99 The PCIe device may not be in the state to accept requests from userspace at
104 QAIC defines a number of driver specific IOCTLs as part of the userspace API.
107 This IOCTL allows userspace to send a NNC request to the QSM. The call will
111 This IOCTL allows userspace to allocate a buffer object (BO) which can send
117 This IOCTL allows userspace to prepare an allocated BO to be mmap'd into the
118 userspace process.
121 This IOCTL allows userspace to slice a BO in preparation for sending the BO
127 This IOCTL allows userspace to submit a set of sliced BOs to the device. The
132 This IOCTL operates like DRM_IOCTL_QAIC_EXECUTE_BO, but it allows userspace
[all …]
|
| /linux-6.12.1/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 …]
|
| D | rfkill.h | 24 /* define userspace visible states */
60 * @RFKILL_OP_CHANGE: a device's state changed -- userspace changes one device
61 * @RFKILL_OP_CHANGE_ALL: userspace changes all devices (of a type, or all)
83 * struct rfkill_event - events for userspace on /dev/rfkill
90 * Structure used for userspace communication on /dev/rfkill,
102 * struct rfkill_event_ext - events for userspace on /dev/rfkill
111 * Structure used for userspace communication on /dev/rfkill,
140 * This would have allowed userspace to detect on read() and write()
146 * hard block reasons field, we found that userspace (notably systemd)
159 * old behaviour for all userspace, unless it explicitly opts in to the
[all …]
|
| /linux-6.12.1/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-6.12.1/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-6.12.1/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"
40 A driver to let userspace turn memfd regions into dma-bufs.
50 problem where userspace is able to pin unrestricted amounts of memory
75 allows userspace to allocate dma-bufs that can be shared
|
| /linux-6.12.1/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-6.12.1/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
|