Home
last modified time | relevance | path

Searched refs:userspace (Results 1 – 25 of 618) sorted by relevance

12345678910>>...25

/Linux-v5.4/Documentation/networking/
Dmac80211-auth-assoc-deauth.txt9 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
Doperstates.txt15 Thanks to 802.1X, userspace must be granted the possibility to
19 and changeable from userspace under certain rules.
22 2. Querying from userspace
27 important for setting from userspace.
47 Interface is in unknown state, neither driver nor userspace has set
71 contains link policy. This is needed for userspace interaction
93 real hardware, it is possible to set this bit from userspace. One
123 IF_OPER_UP if userspace interaction is disabled. Otherwise
124 IF_OPER_DORMANT with the possibility for userspace to initiate the
128 4. Setting from userspace
[all …]
Dopenvswitch.txt4 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 …]
Dcdc_mbim.txt41 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 …]
Ddns_resolver.txt21 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-v5.4/Documentation/admin-guide/device-mapper/
Ddm-init.rst8 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 …]
Ddm-log.rst25 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-v5.4/Documentation/infiniband/
Duser_verbs.rst6 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-v5.4/drivers/dma-buf/
DKconfig10 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.
/Linux-v5.4/Documentation/virt/kvm/
Ds390-diag.txt17 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).
81 This function code is handled by userspace.
/Linux-v5.4/Documentation/driver-api/
Dsync_file.rst13 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-v5.4/drivers/connector/
DKconfig4 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-v5.4/Documentation/firmware-guide/acpi/
Dacpi-lid.rst49 Expections 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-v5.4/Documentation/target/
Dtcmu-design.rst31 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-v5.4/drivers/infiniband/
DKconfig19 tristate "InfiniBand userspace MAD support"
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)"
33 kernel side of userspace verbs and the userspace
34 communication manager (CM). This allows userspace processes
45 new verbs only. This allows userspace to invoke the IOCTL based uAPI
/Linux-v5.4/Documentation/x86/
Dpti.rst15 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-v5.4/Documentation/gpu/
Ddrm-uapi.rst7 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-v5.4/fs/fuse/
DKconfig7 in a userspace program.
18 If you want to develop a userspace FS, or if you want to use
26 implemented in userspace.
28 If you want to develop or use a userspace character device
/Linux-v5.4/Documentation/accounting/
Dtaskstats.rst7 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).
147 interface to return them. Since userspace processes each netlink attribute
[all …]
/Linux-v5.4/Documentation/ABI/obsolete/
Dsysfs-gpio8 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-v5.4/arch/um/kernel/
Dtlb.c40 int userspace; member
47 #define INIT_HVC(mm, force, userspace) \ argument
52 .userspace = userspace, \
73 if (hvc->userspace) in do_ops()
84 if (hvc->userspace) in do_ops()
96 if (hvc->userspace) in do_ops()
129 if (hvc->userspace) in add_mmap()
308 int ret = 0, userspace = 1; in fix_range_common() local
310 hvc = INIT_HVC(mm, force, userspace); in fix_range_common()
345 int updated = 0, err = 0, force = 0, userspace = 0; in flush_tlb_kernel_range_common() local
[all …]
/Linux-v5.4/drivers/uio/
DKconfig6 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.
151 A sample userspace application using this driver is available
165 to network and storage devices from userspace.
/Linux-v5.4/Documentation/security/tpm/
Dtpm_ftpm_tee.rst20 used more like a dumb pipe between firmware and kernel/userspace.
26 userspace which will enable userspace to communicate with the firmware TPM
/Linux-v5.4/drivers/w1/
DKconfig21 This allows to communicate with userspace using connector. For more
23 There are three types of messages between w1 core and userspace:
27 3. Replies to userspace commands.
/Linux-v5.4/Documentation/admin-guide/gpio/
Dsysfs.rst12 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
44 - Control interfaces used to get userspace control over GPIOs;
58 a GPIO to userspace by writing its number to this file.
64 Reverses the effect of exporting to userspace.
84 allow userspace to reconfigure this GPIO's direction.
145 /* export the GPIO to userspace */
157 signal direction may change. This helps drivers prevent userspace code

12345678910>>...25