Searched +full:last +full:- +full:used (Results 1 – 25 of 553) sorted by relevance
12345678910>>...23
| /Documentation/userspace-api/ |
| D | ELF.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Linux-specific ELF idiosyncrasies
13 "Last" program header is the one with the biggest offset in the file:
14 e_phoff + (e_phnum - 1) * sizeof(Elf_Phdr).
19 First PT_INTERP program header is used to locate the filename of ELF
25 Last PT_GNU_STACK program header defines userspace stack executability
31 ELF interpreter's last PT_GNU_PROPERTY program header is used (since
32 Linux 5.8). If interpreter doesn't have one, then the last PT_GNU_PROPERTY
33 program header of an executable is used. Other PT_GNU_PROPERTY headers
|
| D | vduse.rst | 2 VDUSE - "vDPA Device in Userspace"
9 possible to implement software-emulated vDPA devices in userspace. And
21 ----------------------------
49 .. code-block:: c
59 return -ENOMEM;
92 return -1;
96 ---------------
104 add per-virtqueue configuration such as the max size of virtqueue to the device.
111 .. code-block:: c
121 return -1;
[all …]
|
| /Documentation/wmi/ |
| D | acpi-interface.rst | 1 .. SPDX-License-Identifier: GPL-2.0-or-later
13 -------------------
17 used for mapping and execution of WMI methods and/or queries. If there exist
22 -----------
24 The ``_WDG`` buffer is used to discover WMI objects and is required to be
37 The WMI object flags control whether the method or notification ID is used:
39 - 0x1: Data block usage is expensive and must be explicitly enabled/disabled.
40 - 0x2: Data block contains WMI methods.
41 - 0x4: Data block contains ASCIZ string.
42 - 0x8: Data block describes a WMI event, use notification ID instead
[all …]
|
| /Documentation/arch/mips/ |
| D | ingenic-tcu.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 The Timer/Counter Unit (TCU) in Ingenic JZ47xx SoCs is a multi-function
8 hardware block. It features up to eight channels, that can be used as
11 - JZ4725B, JZ4750, JZ4755 only have six TCU channels. The other SoCs all
14 - JZ4725B introduced a separate channel, called Operating System Timer
15 (OST). It is a 32-bit programmable timer. On JZ4760B and above, it is
16 64-bit.
18 - Each one of the TCU channels has its own clock, which can be reparented to three
21 - The watchdog and OST hardware blocks also feature a TCSR register with the same
23 - The TCU registers used to gate/ungate can also gate/ungate the watchdog and
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-decoder-cmd.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_DECODER_CMD - VIDIOC_TRY_DECODER_CMD - Execute an decoder command
38 These ioctls control an audio/video (usually MPEG-) decoder.
40 ``VIDIOC_TRY_DECODER_CMD`` can be used to try a command without actually
68 .. flat-table:: struct v4l2_decoder_cmd
69 :header-rows: 0
70 :stub-columns: 0
73 * - __u32
74 - ``cmd``
75 -
[all …]
|
| /Documentation/admin-guide/ |
| D | serial-console.rst | 7 kernel - by default it is not compiled in. For PC style serial ports
10 :menuselection:`Character devices --> Serial drivers --> 8250/16550 and compatible serial support -…
39 the last device will be used when you open ``/dev/console``.
57 This rule is used also when the last console= parameter is not used
73 Note that the last ``console=tty1`` parameter still makes a difference.
74 The kernel command line is used also by systemd. It would use the last
78 acting as a system console will be used. At this time, the system
96 rm -f console tty0
97 mknod -m 622 console c 5 1
98 mknod -m 622 tty0 c 4 0
[all …]
|
| D | filesystem-monitoring.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 Fanotify supports the FAN_FS_ERROR event type for file system-wide error
11 reporting. It is meant to be used by file system health monitoring
26 error that occurred for a file system since the last notification, and
47 ``samples/fanotify/fs-monitor.c`` for an example parser.
50 --------------------
68 suppressed to preserve the original error information, since the last
72 ----------
74 The FID record can be used to uniquely identify the inode that triggered
|
| /Documentation/core-api/ |
| D | maple_tree.rst | 1 .. SPDX-License-Identifier: GPL-2.0+
13 The Maple Tree is a B-Tree data type which is optimized for storing
14 non-overlapping ranges, including ranges of size 1. The tree was designed to
17 entry in a cache-efficient manner. The tree can also be put into an RCU-safe
24 use the normal API. An :ref:`maple-tree-advanced-api` exists for more complex
34 :ref:`maple-tree-advanced-api`, but are blocked by the normal API.
39 Pre-allocating of nodes is also supported using the
40 :ref:`maple-tree-advanced-api`. This is useful for users who must guarantee a
45 .. _maple-tree-normal-api:
52 freshly-initialised maple tree contains a ``NULL`` pointer for the range ``0``
[all …]
|
| D | errseq.rst | 13 It's implemented as an unsigned 32-bit value. The low order bits are
15 are used as a counter. This is done with atomics instead of locking so that
21 To mitigate this, the bit between the error value and counter is used as
24 sampled it since the last time an error was recorded.
28 +--------------------------------------+----+------------------------+
30 +--------------------------------------+----+------------------------+
32 +--------------------------------------+----+------------------------+
35 it as a running cursor. That value can later be used to tell whether
39 can tell whether the value has changed since they last checked it.
54 They're all handing him work to do -- so much he can't keep track of who
[all …]
|
| D | rbtree.rst | 2 Red-black Trees (rbtree) in Linux
9 What are red-black trees, and what are they for?
10 ------------------------------------------------
12 Red-black trees are a type of self-balancing binary search tree, used for
14 are used to efficiently store sparse arrays and thus use long integer indexes
19 Red-black trees are similar to AVL trees, but provide faster real-time bounded
26 There are a number of red-black trees in use in the kernel.
29 The high-resolution timer code uses an rbtree to organize outstanding
31 red-black tree. Virtual memory areas (VMAs) are tracked with red-black
38 Linux Weekly News article on red-black trees
[all …]
|
| /Documentation/devicetree/bindings/iio/adc/ |
| D | adi,ad7280a.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Michael Hennerich <michael.hennerich@analog.com>
11 - Jonathan Cameron <jic23@kernel.org>
15 Used in devices such as hybrid electric cars, battery backup and power tools.
18 https://www.analog.com/media/en/technical-documentation/data-sheets/AD7280A.pdf
31 adi,voltage-alert-last-chan:
36 last device in the daisy chain.
40 adi,acquisition-time-ns:
[all …]
|
| /Documentation/power/ |
| D | userland-swsusp.rst | 46 last argument of ioctl() should be a pointer to an int variable,
51 has been created the read() operation can be used to transfer
72 (the last argument should be a pointer to a loff_t variable that
77 (the last argument should be a pointer to a loff_t variable that
82 (the last argument should be a pointer to a loff_t variable that
92 located (the last ioctl() argument should point to a struct
96 swap files (see Documentation/power/swsusp-and-swap-files.rst for
109 immediately enter the suspend-to-RAM state, so this call must always
112 is needed to implement the suspend-to-both mechanism in which the
118 The device's read() operation can be used to transfer the snapshot image from
[all …]
|
| /Documentation/arch/powerpc/ |
| D | vcpudispatch_stats.rst | 1 .. SPDX-License-Identifier: GPL-2.0
14 /proc/powerpc/vcpudispatch_stats can be used to obtain statistics
31 2. number of times this vcpu was dispatched on the same processor as last
34 as last time, but within the same chip
69 physical cpu as the last time. 2683 were on a different core, but within
71 its last dispatch.
|
| /Documentation/userspace-api/media/cec/ |
| D | cec-pin-error-inj.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
9 has low-level support for the CEC bus. Most hardware today will have
10 high-level CEC support where the hardware deals with driving the CEC bus,
19 Currently only the cec-gpio driver (when the CEC line is directly
20 connected to a pull-up GPIO line) and the AllWinner A10/A20 drm driver
25 now an ``error-inj`` file.
32 With ``cat error-inj`` you can see both the possible commands and the current
35 $ cat /sys/kernel/debug/cec/cec0/error-inj
38 # rx-clear clear all rx error injections
39 # tx-clear clear all tx error injections
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-iio-vf610 | 3 Contact: linux-iio@vger.kernel.org
5 Specifies the hardware conversion mode used. The three
6 available modes are "normal", "high-speed" and "low-power",
7 where the last is the default mode.
12 Contact: linux-iio@vger.kernel.org
14 Specifies the hardware conversion mode used within DAC.
15 The two available modes are "high-power" and "low-power",
16 where "low-power" mode is the default mode.
|
| D | sysfs-power | 15 labels, which may be "mem" (suspend), "standby" (power-on
16 suspend), "freeze" (suspend-to-idle) and "disk" (hibernation).
21 See Documentation/admin-guide/pm/sleep-states.rst for more
31 supported). The mode that will be used on subsequent attempts
36 represented by it to be used on subsequent attempts to suspend
39 See Documentation/admin-guide/pm/sleep-states.rst for more
47 suspend-to-disk mechanism. Reading from this file returns
51 'firmware' - means that the memory image will be saved to disk
55 'platform' - the memory image will be saved by the kernel and
59 'shutdown' - the memory image will be saved by the kernel and
[all …]
|
| /Documentation/gpu/ |
| D | msm-crash-dump.rst | 14 by a (-).
17 --------
38 rbbm-status
52 last-fence
53 The last fence that was issued on the ringbuffer
55 retired-fence
56 The last fence retired on the ringbuffer.
68 The contents of the ring encoded as ascii85. Only the used
96 registers-hlsq
|
| /Documentation/arch/s390/ |
| D | monreader.rst | 5 Date : 2004-Nov-26
23 IUCV `*MONITOR` statement in its user entry. If the monitor DCSS to be used is
33 See also "CP Command and Utility Reference" (SC24-6081-00) for more information
35 and Administration" (SC24-6116-00) for more information on DCSSes.
38 -----------
50 -----------
78 Refer to the "z/VM Performance" book (SC24-6109-00) on how to create a monitor
83 --------
92 -----
98 -----------------------
[all …]
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | mvebu-devbus.txt | 9 - compatible: Armada 370/XP SoC are supported using the
10 "marvell,mvebu-devbus" compatible string.
13 "marvell,orion-devbus" compatible string.
15 - reg: A resource specifier for the register space.
20 - #address-cells: Must be set to 1
21 - #size-cells: Must be set to 1
22 - ranges: Must be set up to reflect the memory layout with four
23 integer values for each chip-select line in use:
28 - devbus,keep-config This property can optionally be used to keep
37 - devbus,turn-off-ps: Defines the time during which the controller does not
[all …]
|
| /Documentation/driver-api/ |
| D | frame-buffer.rst | 6 fb_var_screeninfo, fb_fix_screeninfo and fb_monospecs. The last
14 fb_var_screeninfo is used to describe the features of a video card
24 The last structure is fb_monospecs. In the old API, there was little
27 fb_monospecs prevents such things, and if used correctly, can prevent a
32 -------------------
34 .. kernel-doc:: drivers/video/fbdev/core/fbmem.c
38 ---------------------
40 .. kernel-doc:: drivers/video/fbdev/core/fbcmap.c
44 --------------------------------
46 .. kernel-doc:: drivers/video/fbdev/core/modedb.c
[all …]
|
| /Documentation/networking/ |
| D | rxrpc.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 The RxRPC protocol driver provides a reliable two-phase transport on top of UDP
8 that can be used to perform RxRPC remote operations. This is done over sockets
38 RxRPC is a two-layer protocol. There is a session layer which provides
44 +-------------+
46 +-------------+
48 +-------------+
50 +-------------+
52 +-------------+
60 (2) A two-phase protocol. The client transmits a blob (the request) and then
[all …]
|
| /Documentation/staging/ |
| D | lzo.rst | 24 operands are used to indicate:
26 - a distance when copying data from the dictionary (past output buffer)
27 - a length (number of bytes to copy from dictionary)
28 - the number of literals to copy, which is retained in variable "state"
45 length = byte & ((1 << #bits) - 1)
47 length = ((1 << #bits) - 1)
49 length += first-non-zero-byte
57 forming a little-endian 16-bit quantity (marked LE16 below).
65 generally encoded in the last two bits of the instruction but may also be
66 taken from the last two bits of an extra operand (eg: distance).
[all …]
|
| /Documentation/scheduler/ |
| D | sched-pelt.c | 2 * The following program is used to generate the constants for
6 * C program (compile with -lm)
23 /* To silence -Wunused-but-set-variable warnings. */ in calc_runnable_avg_yN_inv()
26 x = ((1UL<<32)-1)*pow(y, i); in calc_runnable_avg_yN_inv()
55 int n = -1;
61 long last = 0, y_inv = ((1UL<<32)-1)*y; in calc_converged_max() local
64 if (n > -1) in calc_converged_max()
71 if (last == max) in calc_converged_max()
74 last = max; in calc_converged_max()
76 n--; in calc_converged_max()
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-integrity.rst | 2 dm-integrity
5 The dm-integrity target emulates a block device that has additional
6 per-sector tags that can be used for storing integrity information.
9 writing the sector and the integrity tag must be atomic - i.e. in case of
12 To guarantee write atomicity, the dm-integrity target uses journal, it
16 The dm-integrity target can be used with the dm-crypt target - in this
17 situation the dm-crypt target creates the integrity data and passes them
18 to the dm-integrity target via bio_integrity_payload attached to the bio.
19 In this mode, the dm-crypt and dm-integrity targets provide authenticated
20 disk encryption - if the attacker modifies the encrypted device, an I/O
[all …]
|
| /Documentation/networking/device_drivers/ethernet/toshiba/ |
| D | spider_net.rst | 1 .. SPDX-License-Identifier: GPL-2.0
15 ethernet device built into the Toshiba southbridge commonly used
21 together with three pointers into the ring that are used to manage its
29 "full" and "not-in-use". An "empty" or "ready" descriptor is ready
31 and is waiting to be emptied and processed by the OS. A "not-in-use"
40 buffers, processing them, and re-marking them empty.
54 descr. The OS will process this descr, and then mark it "not-in-use",
57 all of those behind it should be "not-in-use". When RX traffic is not
62 The head pointer (somewhat mis-named) follows after the tail pointer.
64 a "not-in-use" descr. The OS will perform various housekeeping duties
[all …]
|
12345678910>>...23