| /openbmc/linux/Documentation/networking/ |
| H A D | xfrm_sync.rst | 1 .. SPDX-License-Identifier: GPL-2.0
21 This way a backup stays as closely up-to-date as an active member.
25 For this reason, we also add a nagle-like algorithm to restrict
28 These thresholds are set system-wide via sysctls or can be updated
32 - the lifetime byte counter
36 - the replay sequence for both inbound and outbound
39 ----------------------
41 nlmsghdr:aevent_id:optional-TLVs.
49 A XFRM_MSG_NEWAE will have at least two TLVs (as is
76 message (kernel<->user) as well the cause (config, query or event).
[all …]
|
| H A D | af_xdp.rst | 1 .. SPDX-License-Identifier: GPL-2.0
20 XDP programs to redirect frames to a memory buffer in a user-space
24 syscall. Associated with each XSK are two rings: the RX ring and the
38 is simply an offset within the entire UMEM region. The user space
42 UMEM also has two rings: the FILL ring and the COMPLETION ring. The
47 kernel has transmitted completely and can now be used again by user
59 corresponding two rings, sets the XDP_SHARED_UMEM flag in the bind
64 single-consumer / single-producer (for performance reasons), the new
72 user-space application can place an XSK at an arbitrary place in this
79 traffic to user space through the XSK.
[all …]
|
| H A D | gtp.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 In 'drivers/net/gtp.c' you are finding a kernel-level implementation
18 tunneling User-IP payload between a mobile station (phone, modem)
29 technology-dependent protocol stack for transmitting the user IP
35 is translated into GTP *without breaking the end-to-end tunnel*. So
38 At some point the GTP packet ends up on the so-called GGSN (GSM/UMTS)
39 or P-GW (LTE), which terminates the tunnel, decapsulates the packet
42 theoretically some non-IP network like X.25).
58 It *only* implements the so-called 'user plane', carrying the User-IP
59 payload, called GTP-U. It does not implement the 'control plane',
[all …]
|
| /openbmc/linux/Documentation/mm/damon/ |
| H A D | design.rst | 1 .. SPDX-License-Identifier: GPL-2.0
13 - Operations Set: Implements fundamental operations for DAMON that depends on
14 the given monitoring target address-space and available set of
16 - Core: Implements core logics including monitoring overhead/accurach control
17 and access-aware system operations on top of the operations set layer, and
18 - Modules: Implements kernel modules for various purposes that provides
19 interfaces for the user space, on top of the core layer.
23 ---------------------------
29 space. DAMON separates the two parts in different layers, namely DAMON
45 --------------------
[all …]
|
| /openbmc/linux/Documentation/admin-guide/namespaces/ |
| H A D | compatibility-list.rst | 5 This document contains the information about the problems user
13 - UTS IPC VFS PID User Net
19 User 2 2 X
33 2. Intentionally, two equal user IDs in different user namespaces
35 words, user 10 in one user namespace shouldn't have the same
36 access permissions to files, belonging to user 10 in another
39 The same is true for the IPC namespaces being shared - two users
40 from different user namespaces should not access the same IPC objects
|
| /openbmc/linux/Documentation/gpu/ |
| H A D | komeda-kms.rst | 1 .. SPDX-License-Identifier: GPL-2.0
23 -----
30 ------
39 -------------------
43 user can also insert a scaler between compositor and wb_layer to down scale
47 --------------------------
52 -----------------------------
57 --------------------------------
62 ------
66 introduces Layer Split, which splits the whole image to two half parts and feeds
[all …]
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | padata.rst | 1 .. SPDX-License-Identifier: GPL-2.0
23 ------------
43 ------------------
45 The CPUs used to run jobs can be changed in two ways, programmatically with
58 live in /sys/kernel/pcrypt/<instance-name>. Within an instance's directory
59 there are two files, parallel_cpumask and serial_cpumask, and either cpumask
64 Reading one of these files shows the user-supplied cpumask, which may be
67 Padata maintains two pairs of cpumasks internally, the user-supplied cpumasks
69 cpumask.) The user-supplied cpumasks default to all possible CPUs on instance
71 subset of the user-supplied cpumasks and contain only the online CPUs in the
[all …]
|
| H A D | cachetlb.rst | 19 if it can be proven that a user address space has never executed
25 virtual-->physical address translations obtained from the software
43 This interface flushes an entire user address space from
56 Here we are flushing a specific range of (user) virtual
59 modifications for the address space 'vma->vm_mm' in the range
60 'start' to 'end-1' will be visible to the cpu. That is, after
62 virtual addresses in the range 'start' to 'end-1'.
78 address space is available via vma->vm_mm. Also, one may
79 test (vma->vm_flags & VM_EXEC) to see if this region is
81 split-tlb type setups).
[all …]
|
| /openbmc/linux/Documentation/arch/ia64/ |
| H A D | efirtc.rst | 13 the IA-64 platform.
15 The purpose of this driver is to supply an API for kernel and user applications
31 Because we wanted to minimize the impact on existing user-level apps using
39 the reference date is different. Year is the using the full 4-digit format.
44 without necessarily impacting any of the user applications. The decoupling
47 The driver exposes two interfaces, one via the device file and a set of
48 ioctl()s. The other is read-only via the /proc filesystem.
54 "public" API of the two drivers. The specifics of the legacy RTC are still
62 Two ioctl()s, compatible with the legacy RTC calls:
90 Those two ioctl()s can be exercised with the hwclock command:
[all …]
|
| /openbmc/qemu/include/hw/virtio/ |
| H A D | vhost-user-blk.h | 2 * vhost-user-blk host device
8 * Based on vhost-scsi.h, Copyright IBM, Corp. 2011
11 * See the COPYING.LIB file in the top-level directory.
18 #include "standard-headers/linux/virtio_blk.h"
20 #include "chardev/char-fe.h"
22 #include "hw/virtio/vhost-user.h"
25 #define TYPE_VHOST_USER_BLK "vhost-user-blk"
44 * There are at least two steps of initialization of the
45 * vhost-user device. The first is a "connect" step and
47 * those initialization phases by using two fields.
|
| /openbmc/linux/drivers/thermal/intel/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
11 enforce idle time which results in more package C-state residency. The
12 user interface is exposed via generic thermal framework.
32 two trip points which can be set by user to get notifications via thermal
53 temperature sensor (DTS). These SoCs have two additional DTSs in
55 thermal zone. There are two trip points. One of the trip point can
56 be set by user mode programs to get notifications via Linux thermal
65 temperature sensor (DTS). For X1000 SoC, it has one on-die DTS.
66 The DTS will be registered as a thermal zone. There are two trip points:
|
| /openbmc/linux/Documentation/kbuild/ |
| H A D | kconfig-macro-language.rst | 6 -------
9 two languages in one. One language describes dependency graphs consisting of
13 There is clear distinction between the two language stages. For example, you
21 $(CC) -o $(APP) $(SRC)
27 gcc -o foo foo.c
32 The idea is quite similar in Kconfig - it is possible to describe a Kconfig
38 def_bool $(shell, $(srctree)/scripts/gcc-check-foo.sh $(CC))
46 Then, Kconfig moves onto the evaluation stage to resolve inter-symbol
47 dependency as explained in kconfig-language.rst.
51 ---------
[all …]
|
| /openbmc/linux/Documentation/hwmon/ |
| H A D | adm9240.rst | 10 Addresses scanned: I2C 0x2c - 0x2f
20 Addresses scanned: I2C 0x2c - 0x2f
24 http://pdfserv.maxim-ic.com/en/ds/DS1780.pdf
30 Addresses scanned: I2C 0x2c - 0x2f
37 - Frodo Looijaard <frodol@dds.nl>,
38 - Philip Edelbrock <phil@netroedge.com>,
39 - Michiel Rook <michiel@grendelproject.nl>,
40 - Grant Coady <gcoady.lk@gmail.com> with guidance
44 ---------
46 chip MSB 5-bit address. Each chip reports a unique manufacturer
[all …]
|
| /openbmc/linux/Documentation/admin-guide/pm/ |
| H A D | strategies.rst | 1 .. SPDX-License-Identifier: GPL-2.0
13 The Linux kernel supports two major high-level power management strategies.
15 One of them is based on using global low-power states of the whole system in
16 which user space code cannot be executed and the overall system activity is
17 significantly reduced, referred to as :doc:`sleep states <sleep-states>`. The
18 kernel puts the system into one of these states when requested by user space
21 user space code can run. Because sleep states are global and the whole system
23 :doc:`system-wide power management <system-wide>`.
25 The other strategy, referred to as the :doc:`working-state power management
26 <working-state>`, is based on adjusting the power states of individual hardware
[all …]
|
| /openbmc/linux/Documentation/driver-api/thermal/ |
| H A D | x86_pkg_temperature_thermal.rst | 14 ---------
16 Intel® 64 and IA-32 Architectures Software Developer’s Manual (Jan, 2013):
20 -----------
23 zone with maximum two user mode configurable trip points. Number of trip points
25 user mode can receive notification via thermal notification mechanism and can
30 --------------------
37 This contains two trip points:
39 - trip_point_0_temp
40 - trip_point_1_temp
42 User can set any temperature between 0 to TJ-Max temperature. Temperature units
[all …]
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | idmappings.rst | 1 .. SPDX-License-Identifier: GPL-2.0
12 ------------
32 u22 -> k10000
33 u23 -> k10001
34 u24 -> k10002
36 From a mathematical viewpoint ``U`` and ``K`` are well-ordered sets and an
38 order isomorphic. In fact, ``U`` and ``K`` are always well-ordered subsets of
45 k10000 -> u22
46 k10001 -> u23
47 k10002 -> u24
[all …]
|
| /openbmc/linux/Documentation/mm/ |
| H A D | active_mm.rst | 6 (running tasks with ->active_mm == mm && ->mm == NULL) on kernels
13 List: linux-kernel
16 Date: 1999-07-30 21:36:24
18 Cc'd to linux-kernel, because I don't write explanations all that often,
25 > discussed on the mailing lists---I just returned from vacation and
26 > wasn't able to follow linux-kernel for a while).
30 - we have "real address spaces" and "anonymous address spaces". The
32 user-level page tables at all, so when we do a context switch into an
37 doesn't need any user mappings - all kernel threads basically fall into
39 some amount of time they are not going to be interested in user space,
[all …]
|
| /openbmc/linux/Documentation/driver-api/iio/ |
| H A D | core.rst | 6 many different types of embedded sensors and a standard interface to user space
8 :file:`drivers/iio/industrialio-*`
11 ----------------------
13 * struct iio_dev - industrial I/O device
14 * iio_device_alloc() - allocate an :c:type:`iio_dev` from a driver
15 * iio_device_free() - free an :c:type:`iio_dev` from a driver
16 * iio_device_register() - register a device with the IIO subsystem
17 * iio_device_unregister() - unregister a device from the IIO
25 There are two ways for a user space application to interact with an IIO driver.
33 :doc:`SPI <../spi>` driver and will create two routines, probe and remove.
[all …]
|
| /openbmc/linux/drivers/usb/gadget/legacy/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
7 # NOTE: Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
9 # - Host systems (like PCs) need CONFIG_USB (with "A" jacks).
10 # - Peripherals (like PDAs) need CONFIG_USB_GADGET (with "B" jacks).
11 # - Some systems have both kinds of controllers.
13 # With help from a special transceiver and a "Mini-AB" jack, systems with
14 # both kinds of controller can also support "USB On-the-Go" (CONFIG_USB_OTG).
23 # Gadget drivers are hardware-neutral, or "platform independent",
44 Gadget Zero is a two-configuration device. It either sinks and
47 conformance. The driver needs only two bulk-capable endpoints, so
[all …]
|
| /openbmc/linux/Documentation/firmware-guide/acpi/ |
| H A D | video_extension.rst | 1 .. SPDX-License-Identifier: GPL-2.0
16 Export a sysfs interface for user space to control backlight level
26 Documentation/ABI/stable/sysfs-class-backlight.
65 The first two levels are for when laptop are on AC or on battery and are
70 as a "brightness level" indicator. Thus from the user space perspective
74 Notify user space about hotkey event
77 There are generally two cases for hotkey event reporting:
79 i) For some laptops, when user presses the hotkey, a scancode will be
80 generated and sent to user space through the input device created by
82 following key code will appear to user space::
[all …]
|
| /openbmc/linux/arch/x86/include/asm/ |
| H A D | segment.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
14 ((((base) & _AC(0xff000000,ULL)) << (56-24)) | \
16 (((limit) & _AC(0x000f0000,ULL)) << (48-16)) | \
30 * Bottom two bits of selector give the ring
38 * determine whether the context is user mode or kernel mode with
47 /* User mode is privilege level 3: */
61 * The layout of the per-CPU GDT under Linux:
63 * 0 - null <=== cacheline #1
64 * 1 - reserved
65 * 2 - reserved
[all …]
|
| /openbmc/linux/Documentation/admin-guide/nfs/ |
| H A D | nfs-idmapper.rst | 5 Id mapper is used by NFS to translate user and group ids into names, and to
6 translate user and group names into ids. Part of this translation involves
7 performing an upcall to userspace to request the information. There are two
8 ways NFS could obtain this information: placing a call to /sbin/request-key
11 NFS will attempt to call /sbin/request-key first. If this succeeds, the
12 result will be cached using the generic request-key cache. This call should
13 only fail if /etc/request-key.conf is not configured for the id_resolver key
14 type, see the "Configuring" section below if you wish to use the request-key
17 If the call to /sbin/request-key fails (if /etc/request-key.conf is not
26 The file /etc/request-key.conf will need to be modified so /sbin/request-key can
[all …]
|
| /openbmc/linux/drivers/comedi/drivers/ |
| H A D | jr3_pci.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
31 * two-byte words.
42 * Channels 1-6 contain the coupled force data Fx through Mz. Channel
43 * 7 contains the sensor's calibration data. The use of channels 8-15
90 * or the other so that two force vectors or two moment vectors are
93 * have two force vectors, set changeV1 to 1.
139 * was detected in the on-board RAM during the power-up
142 * bit latches, and must be reset by the user.
152 * user. A very fast system using the force data for feedback might
169 * received from the sensor. There are two reasons the CRC may not
[all …]
|
| /openbmc/linux/arch/x86/kernel/ |
| H A D | umip.c | 2 * umip.c Emulation for instruction protected by the User-Mode Instruction
6 * Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
13 #include <asm/insn-eval.h>
19 /** DOC: Emulation for User-Mode Instruction Prevention (UMIP)
21 * User-Mode Instruction Prevention is a security feature present in recent
23 * SIDT, SLDT, SMSW and STR) from being run in user mode by issuing a general
26 * Rather than relaying to the user space the general protection fault caused by
27 * the UMIP-protected instructions (in the form of a SIGSEGV signal), it can be
38 * The instructions protected by UMIP can be split in two groups. Those which
44 * not the actual location of the table. The result is emulated as a hard-coded
[all …]
|
| /openbmc/linux/Documentation/RCU/ |
| H A D | rcu.rst | 6 The basic idea behind RCU (read-copy update) is to split destructive
7 operations into two parts, one that prevents anyone from seeing the data
9 A "grace period" must elapse between the two parts, and this grace period
11 since dropped their references. For example, an RCU-protected deletion
17 --------------------------
19 - Why would anyone want to use RCU?
21 The advantage of RCU's two-part approach is that RCU readers need
26 in read-mostly situations. The fact that RCU readers need not
27 acquire locks can also greatly simplify deadlock-avoidance code.
29 - How can the updater tell when a grace period has completed
[all …]
|