Searched refs:userspace (Results 1 – 25 of 572) sorted by relevance
12345678910>>...23
| /Linux-v4.19/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 | operstates.txt | 15 Thanks to 802.1X, userspace must be granted the possibility to
19 and changeable from userspace under certain rules.
22 2. Querying from userspace
26 to be notified of updates. This is important for setting from userspace.
46 Interface is in unknown state, neither driver nor userspace has set
70 contains link policy. This is needed for userspace interaction
92 real hardware, it is possible to set this bit from userspace. One
121 IF_OPER_UP if userspace interaction is disabled. Otherwise
122 IF_OPER_DORMANT with the possibility for userspace to initiate the
126 4. Setting from userspace
[all …]
|
| D | openvswitch.txt | 4 The Open vSwitch kernel module allows flexible userspace control over
13 table" that userspace populates with "flows" that map from keys based
21 no match, it queues the packet to userspace for processing (as part of
22 its processing, userspace will likely set up a flow to handle further
35 to Open vSwitch is designed to allow carefully written userspace
39 kernel module passes a packet to userspace, it also passes along the
44 - If userspace's notion of the flow key for the packet matches the
47 - If the kernel's flow key includes more fields than the userspace
49 headers but userspace stopped at the Ethernet type (because it
54 - If the userspace flow key includes more fields than the
[all …]
|
| D | cdc_mbim.txt | 41 provides a userspace interface to the MBIM control channel, and will
43 userspace MBIM management application always is required to enable a
46 Such userspace applications includes, but are not limited to:
59 The driver <-> userspace interfaces are described below. The MBIM
63 MBIM control channel userspace ABI
69 using the cdc-wdm driver as a subdriver. The userspace end of the
73 channel. The channel is fully delegated to the userspace management
96 The userspace application can access the CDC MBIM functional
105 The userspace application is responsible for all control message
127 userspace.
[all …]
|
| D | dns_resolver.txt | 21 upcalled to userspace through /sbin/request-key.
23 These routines must be supported by userspace tools dns.upcall, cifs.upcall and
27 (*) Implements the dns_resolver key_type to contact userspace.
77 it doesn't find it, it upcalls to userspace to make a new DNS query, which
114 Keys of dns_resolver type can be read from userspace using keyctl_read() or
123 this type are used to transport and cache DNS lookup results from userspace.
127 userspace to get a new result.
129 Upcalls to userspace are made through the request_key() upcall vector, and are
|
| /Linux-v4.19/Documentation/device-mapper/ |
| D | dm-log.txt | 23 userspace drivers/md/dm-log-userspace* include/linux/dm-log-userspace.h
37 The "userspace" log type
39 This log type simply provides a way to export the log API to userspace,
41 logging requests to userspace, where a daemon receives and processes the
44 The structure used for communication between kernel and userspace are
45 located in include/linux/dm-log-userspace.h. Due to the frequency,
47 kernel and userspace, 'connector' is used as the interface for
50 There are currently two userspace log implementations that leverage this
|
| /Linux-v4.19/Documentation/infiniband/ |
| D | user_verbs.txt | 4 enables direct userspace access to IB hardware via "verbs," as
11 userspace driver for your InfiniBand hardware. For example, to use
13 libmthca userspace driver be installed.
20 directly to hardware registers mmap()ed into userspace, with no
27 Status is returned to userspace as the return value of the write()
34 of which resources are attached to a given userspace context. The
36 between kernel pointers and opaque userspace handles, so that kernel
37 pointers are never exposed to userspace and userspace cannot trick
45 Direct userspace I/O requires that memory regions that are potential
67 and so on. Since the InfiniBand userspace verbs should be safe for
|
| /Linux-v4.19/Documentation/virtual/kvm/ |
| D | s390-diag.txt | 17 userspace.
30 The supported DIAGNOSE function codes vary by the userspace used. For
42 virtio subfunctions depend on KVM's userspace. Generally, userspace
50 Handled by userspace.
53 Handled by userspace.
56 Handled by userspace.
59 Handled by either userspace or KVM (ioeventfd case).
80 This function code is handled by userspace.
|
| /Linux-v4.19/Documentation/ |
| D | sync_file.txt | 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-v4.19/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.
|
| /Linux-v4.19/drivers/connector/ |
| D | Kconfig | 3 tristate "Connector - unified userspace <-> kernelspace linker"
6 This is unified userspace <-> kernelspace connector working on top
15 bool "Report process events to userspace"
19 Provide a connector that reports process events to userspace. Send
|
| /Linux-v4.19/Documentation/acpi/ |
| D | acpi-lid.txt | 42 3. Expections for the userspace users of the ACPI lid device driver
44 The ACPI button driver exports the lid state to the userspace via the
49 it is advised for the userspace program to not to solely rely on this file
52 The ACPI button driver emits the following input event to the userspace:
55 triggered events to the userspace. However, given the fact that the buggy
59 If the userspace hasn't been prepared to ignore the unreliable "opened"
70 This option is the default behavior during the period the userspace
80 If the userspace has been prepared to ignore the unreliable "opened" events
87 to the userspace by always pairing "closed" input events with complement
89 notifications can be delivered to the userspace when the lid is actually
[all …]
|
| D | aml-debugger.txt | 18 The userspace utilities can be built from the kernel source tree using
24 The resultant userspace tool binary is then located at:
31 2. Start the userspace debugger interface
51 3. Stop the userspace debugger interface
|
| /Linux-v4.19/Documentation/target/ |
| D | tcmu-design.txt | 26 allows userspace programs to be written which act as iSCSI targets.
52 If the target is a userspace process, supporting these is easy. tgt,
54 modules just use the available userspace libraries for RBD and GLFS.
59 kernel, another approach is to create a userspace pass-through
78 - Cleanly handle if userspace:
86 - Simple to write a userspace backend
92 between kernel and userspace. Within this region is: a control area
97 development in userspace, and this is conceptually very close to the
101 userspace to determine how large the shared region is) and signaling
116 userspace (respectively) to put commands on the ring, and indicate
[all …]
|
| /Linux-v4.19/Documentation/x86/ |
| D | pti.txt | 9 page tables for use only when running userspace applications. When
14 The userspace page tables contain only a minimal amount of kernel
32 kernels without PTI. This includes a complete mapping of userspace
38 userspace upon executing its first instruction.
40 The userspace page tables map only the kernel data needed to enter
45 For new userspace mappings, the kernel makes the entries in its
49 userspace page tables' PGD.
53 userspace page tables to manage. One PTE to lock, one set of
79 things into the userspace page tables. The downside is
82 mapped into both kernel and userspace page tables. This
[all …]
|
| /Linux-v4.19/fs/fuse/ |
| D | Kconfig | 6 in a userspace program.
17 If you want to develop a userspace FS, or if you want to use
25 implemented in userspace.
27 If you want to develop or use a userspace character device
|
| /Linux-v4.19/drivers/infiniband/ |
| D | Kconfig | 17 tristate "InfiniBand userspace MAD support"
21 is the kernel side of the userspace MAD support, which allows
22 userspace processes to send and receive MADs. You will also
27 tristate "InfiniBand userspace access (verbs and CM)"
31 kernel side of userspace verbs and the userspace
32 communication manager (CM). This allows userspace processes
54 new verbs only. This allows userspace to invoke the IOCTL based uAPI
|
| /Linux-v4.19/Documentation/accounting/ |
| D | taskstats.txt | 6 per-process statistics from the kernel to userspace.
29 To get statistics during a task's lifetime, userspace opens a unicast netlink
34 To obtain statistics for tasks which are exiting, the userspace listener
42 an additional record containing the per-tgid stats is also sent to userspace.
80 the task/process for which userspace wants statistics.
87 the cpumask would be "1-3,5,7-8". If userspace forgets to deregister interest
92 2. Response for a command: sent from the kernel in response to a userspace
120 stats in userspace alone is inefficient and potentially inaccurate (due to lack
127 gets sent to userspace (along with the per-task data).
146 interface to return them. Since userspace processes each netlink attribute
[all …]
|
| /Linux-v4.19/Documentation/ABI/obsolete/ |
| D | sysfs-gpio | 8 userspace. GPIOs are only made available to userspace by an explicit
10 kernel code, it may be exported by userspace (and unexported later).
17 /export ... asks the kernel to export a GPIO to userspace
|
| /Linux-v4.19/drivers/uio/ |
| D | Kconfig | 5 Enable this to allow the userspace driver core code to be
6 built. This code allows userspace programs easy access to
8 to be written in userspace. Note that a small kernel driver
20 driver requires a userspace component called cif that handles
33 This kernel driver requires that the matching userspace driver
79 Automata GmbH. The userspace part of this driver will be
101 This driver requires a userspace component that comes with the card
122 together with the userspace netX stack from Hilscher.
150 A sample userspace application using this driver is available
164 to network and storage devices from userspace.
|
| /Linux-v4.19/Documentation/gpu/ |
| D | drm-uapi.rst | 7 addition, drivers export device-specific interfaces for use by userspace
42 what the userspace side for new uAPI needs to look like. This section here
46 open-sourced userspace patches, and those patches must be reviewed and ready for
50 hardware, with userspace and kernel by necessity having to work together really
54 infeasible to differentiate between behaviour that's required by userspace, and
58 Without access to the full source code of all userspace users that means it
59 becomes impossible to change the implementation details, since userspace could
65 open-source userspace of the DRM subsystem. DRM developers are perfectly fine
66 if closed-source blob drivers in userspace use the same uAPI as the open
71 - Any new userspace interface must have an open-source implementation as
[all …]
|
| /Linux-v4.19/drivers/w1/ |
| D | Kconfig | 20 This allows to communicate with userspace using connector. For more
22 There are three types of messages between w1 core and userspace:
26 3. Replies to userspace commands.
|
| /Linux-v4.19/Documentation/w1/ |
| D | w1.netlink | 7 There are three types of messages between w1 core and userspace:
11 3. Replies to userspace commands.
28 userspace command for bus master
31 userspace command for slave device
50 (write and sample data back to userspace)
71 Currently replies to userspace commands are only generated for read
83 Replies to W1_LIST_MASTERS should send a message back to the userspace
178 Sequence number for userspace requests is set by userspace application.
188 This archive includes userspace application w1d.c which uses
|
| /Linux-v4.19/Documentation/gpio/ |
| D | sysfs.txt | 10 character device ABI. Also see the userspace header in
21 Given appropriate hardware documentation for the system, userspace could
30 userspace GPIO can be used to determine system configuration data that
31 standard kernels won't know about. And for some tasks, simple userspace
42 - Control interfaces used to get userspace control over GPIOs;
55 a GPIO to userspace by writing its number to this file.
60 "unexport" ... Reverses the effect of exporting to userspace.
79 allow userspace to reconfigure this GPIO's direction.
134 /* export the GPIO to userspace */
146 signal direction may change. This helps drivers prevent userspace code
|
| /Linux-v4.19/drivers/sh/intc/ |
| D | Kconfig | 13 This enables support for hardware-assisted userspace hardirq
18 userspace. This is primarily for use by userspace device
|
12345678910>>...23
