| /linux/drivers/cpufreq/ |
| H A 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()
52 struct userspace_policy *userspace = policy->governor_data; in show_speed() local
54 return sprintf(buf, "%u\n", userspace->setspeed); in show_speed()
59 struct userspace_policy *userspace; in cpufreq_userspace_policy_init() local
61 userspace = kzalloc_obj(*userspace); in cpufreq_userspace_policy_init()
62 if (!userspace) in cpufreq_userspace_policy_init()
[all …]
|
| /linux/Documentation/ |
| H A D | .renames.txt | 11 accelerators/ocxl userspace-api/accelerators/ocxl
12 admin-guide/gpio/sysfs userspace-api/gpio/sysfs
190 driver-api/dcdbas userspace-api/dcdbas
195 driver-api/isapnp userspace-api/isapnp
216 early-userspace/buffer-format driver-api/early-userspace/buffer-format
217 early-userspace/early_userspace_support driver-api/early-userspace/early_userspace_support
218 early-userspace/index driver-api/early-userspace/index
255 gpio/sysfs userspace-api/gpio/sysfs
281 ioctl/cdrom userspace-api/ioctl/cdrom
282 ioctl/hdio userspace-api/ioctl/hdio
[all …]
|
| /linux/Documentation/networking/device_drivers/wwan/ |
| H A D | t7xx.rst | 21 WWAN port userspace interfaces representing MBIM & AT control channels and does
22 not play any role in managing their functionality. It is the job of a userspace
25 Examples of few such userspace applications are:
45 The driver provides sysfs interfaces to userspace.
49 The sysfs interface provides userspace with access to the device mode, this
61 Read from userspace to get the current device mode.
66 Write from userspace to set the device mode.
73 The sysfs interface provides userspace with access to enable/disable the debug
83 Read from userspace to get the current debug ports status.
88 Write from userspace to set the debug ports status.
[all …]
|
| H 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/Documentation/filesystems/ |
| H A 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 …]
|
| /linux/Documentation/networking/ |
| H 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
|
| H 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 …]
|
| H 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
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
57 - If the userspace flow key includes more fields than the
[all …]
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A 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 …]
|
| H 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/Documentation/infiniband/ |
| H 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/Documentation/admin-guide/hw-vuln/ |
| H A D | vmscape.rst | 7 prediction in host userspace. It particularly affects hypervisors like QEMU.
10 guest-userspace may be able to attack the guest-kernel using the hypervisor as
39 IBPB before the first exit to userspace after VM-exit. If userspace did not run
42 Note that the existing userspace mitigation against Spectre-v2 is effective in
43 protecting the userspace. They are insufficient to protect the userspace VMMs
45 context switch time, while the userspace VMM can run after a VM-exit without a
83 * 'Mitigation: IBPB before exit to userspace':
87 exit to userspace after VM-exit.
|
| /linux/Documentation/ABI/testing/ |
| H 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/Documentation/driver-api/ |
| H 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
|
| /linux/drivers/s390/crypto/ |
| H A D | zcrypt_api.h | 92 long (*send_cprb)(bool userspace, struct zcrypt_queue *, struct ica_xcRB *,
94 long (*send_ep11_cprb)(bool userspace, struct zcrypt_queue *, struct ep11_urb *,
182 static inline unsigned long z_copy_from_user(bool userspace, in z_copy_from_user() argument
187 if (likely(userspace)) in z_copy_from_user()
193 static inline unsigned long z_copy_to_user(bool userspace, in z_copy_to_user() argument
198 if (likely(userspace)) in z_copy_to_user()
|
| /linux/Documentation/firmware-guide/acpi/ |
| H 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/Documentation/driver-api/gpio/ |
| H 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/Documentation/target/ |
| H A D | tcmu-design.rst | 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
86 - Cleanly handle if userspace:
96 - Simple to write a userspace backend
103 between kernel and userspace. Within this region is: a control area
108 development in userspace, and this is conceptually very close to the
112 userspace to determine how large the shared region is) and signaling
128 userspace (respectively) to put commands on the ring, and indicate
[all …]
|
| /linux/Documentation/sound/ |
| H A D | utimers.rst | 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
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
109 To use userspace-driven ALSA timer as a timer source of snd-aloop, pass
118 userspace-driven timers device (``SNDRV_TIMER_GLOBAL_UDRIVEN``).
120 ``resolution`` for the userspace-driven ALSA timer used with snd-aloop
|
| /linux/drivers/uio/ |
| H 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.
133 A sample userspace application using this driver is available
147 to network and storage devices from userspace.
[all …]
|
| /linux/drivers/connector/ |
| H 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/Documentation/gpu/ |
| H 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
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
82 - Any new userspace interface must have an open-source implementation as
[all …]
|
| /linux/Documentation/virt/acrn/ |
| H 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/Documentation/virt/kvm/s390/ |
| H A D | s390-diag.rst | 20 userspace.
33 The supported DIAGNOSE function codes vary by the userspace used. For
45 depend on KVM's userspace. Regarding virtio subfunctions, generally
46 userspace provides either s390-virtio (subcodes 0-2) or virtio-ccw
57 Handled by userspace.
60 Handled by userspace.
63 Handled by userspace.
66 Handled by either userspace or KVM (ioeventfd case).
84 Handled by userspace.
105 This function code is handled by userspace.
|
| /linux/Documentation/arch/x86/ |
| H 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
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 …]
|