Searched +full:fine +full:- +full:grained (Results 1 – 25 of 42) sorted by relevance
12
| /Documentation/scsi/ |
| D | scsi_eh.rst | 1 .. SPDX-License-Identifier: GPL-2.0
14 [1-1] struct scsi_cmnd
15 [1-2] How do scmd's get completed?
16 [1-2-1] Completing a scmd w/ scsi_done
17 [1-2-2] Completing a scmd w/ timeout
18 [1-3] How EH takes over
20 [2-1] EH through fine-grained callbacks
21 [2-1-1] Overview
22 [2-1-2] Flow of scmds through EH
23 [2-1-3] Flow of control
[all …]
|
| /Documentation/tools/rv/ |
| D | rv.rst | 1 .. SPDX-License-Identifier: GPL-2.0
6 --------------------
8 --------------------
22 Instead of relying on a fine-grained model of a system (e.g., a
23 re-implementation a instruction level), RV works by analyzing the trace
44 **-h**, **--help**
53 **rv-list**\(1), **rv-mon**\(1)
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | maxim,max6650.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Javier Carrasco <javier.carrasco.cruz@gmail.com>
15 of 5VDC/12VDC burshless fans with built-in tachometers.
18 https://datasheets.maximintegrated.com/en/ds/MAX6650-MAX6651.pdf
23 - maxim,max6650
24 - maxim,max6651
29 maxim,fan-microvolt:
35 maxim,fan-prescale:
[all …]
|
| /Documentation/devicetree/bindings/regulator/ |
| D | pwm-regulator.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/regulator/pwm-regulator.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Brian Norris <briannorris@chromium.org>
11 - Lee Jones <lee@kernel.org>
12 - Alexandre Courbot <acourbot@nvidia.com>
19 duty-cycle values must be provided via DT. Limitations are that the
21 Intermediary duty-cycle values which would normally allow finer grained
23 is given to the user if the assumptions made in continuous-voltage mode do
[all …]
|
| /Documentation/admin-guide/perf/ |
| D | cxl.rst | 1 .. SPDX-License-Identifier: GPL-2.0
39 The events shown in perf list are the most fine grained events with a single
58 -----------------------------------------------------------
60 $# perf stat -a -e cxl_pmu_mem0.0/clock_ticks/ -e cxl_pmu_mem0.0/d2h_req_rdshared/
64 $# perf stat -a -e cxl_pmu_mem0.0/vid=VID,gid=GID,mask=MASK/
67 It only supports system-wide counting so attaching to a task is
|
| /Documentation/cpu-freq/ |
| D | cpufreq-stats.rst | 1 .. SPDX-License-Identifier: GPL-2.0
16 3. Configuring cpufreq-stats
22 cpufreq-stats is a driver that provides CPU frequency statistics for each CPU.
37 - time_in_state
38 - total_trans
39 - trans_table
48 <mysystem>:/sys/devices/system/cpu/cpu0/cpufreq/stats # ls -l
50 drwxr-xr-x 2 root root 0 May 14 16:06 .
51 drwxr-xr-x 3 root root 0 May 14 15:58 ..
52 --w------- 1 root root 4096 May 14 16:06 reset
[all …]
|
| /Documentation/security/ |
| D | lsm.rst | 17 about Security-Enhanced Linux (SELinux) at the 2.5 Linux Kernel Summit.
18 SELinux is an implementation of flexible and fine-grained
40 individuals, including Greg Kroah-Hartman and James Morris, to develop a
95 32-bit integer. The security modules are required to map or otherwise
|
| /Documentation/arch/powerpc/ |
| D | dexcr.rst | 1 .. SPDX-License-Identifier: GPL-2.0-or-later
11 PowerPC ISA 3.1B (Power10) that allows per-cpu control over several dynamic
13 branch target prediction) and enabling return-oriented programming (ROP)
24 A hypervisor-privileged SPR that can control aspects for the hypervisor and
27 An optional ultravisor-privileged SPR that can control aspects for the ultravisor.
30 provides a non-privileged read-only view of the userspace DEXCR aspects.
31 There is also an SPR that provides a read-only view of the hypervisor enforced
40 -----
52 .. flat-table::
53 :header-rows: 1
[all …]
|
| /Documentation/power/powercap/ |
| D | powercap.rst | 15 example, the intel-rapl control type represents the Intel "Running Average
16 Power Limit" (RAPL) technology, whereas the 'idle-injection' control type
29 fine grained control is required, it can be applied through the subzones.
35 └──intel-rapl
36 ├──intel-rapl:0
43 │ ├──device -> ../../intel-rapl
45 │ ├──intel-rapl:0:0
52 │ │ ├──device -> ../../intel-rapl:0
60 │ │ ├──subsystem -> ../../../../../../class/power_cap
62 │ ├──intel-rapl:0:1
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-thermal | 61 E.g. it can be one of critical, hot, passive, `active[0-*]`
84 The trip point in this thermal zone which `cdev[0-*]` is
85 associated with; -1 means the cooling device is not
92 The influence of `cdev[0-*]` in this thermal zone. This value
124 Documentation/driver-api/thermal/power_allocator.rst
133 Documentation/driver-api/thermal/power_allocator.rst
143 Documentation/driver-api/thermal/power_allocator.rst
153 Documentation/driver-api/thermal/power_allocator.rst
165 Documentation/driver-api/thermal/power_allocator.rst
194 Documentation/driver-api/thermal/power_allocator.rst
[all …]
|
| /Documentation/gpu/ |
| D | afbc.rst | 1 .. SPDX-License-Identifier: GPL-2.0+
8 It provides fine-grained random access and minimizes the amount of
21 AFBC streams can contain several components - where a component
37 reside in the least-significant bits of the corresponding linear
81 Formats which are typically multi-planar in linear layouts (e.g. YUV
111 Cross-device interoperability
115 canonical formats for use between AFBC-enabled devices. Formats which
119 .. flat-table:: AFBC formats
121 * - Fourcc code
122 - Description
[all …]
|
| /Documentation/arch/arm64/ |
| D | booting.rst | 13 (EL0 - EL3), with EL0, EL1 and EL2 having a secure and a non-secure
33 ---------------------------
46 -------------------------
50 The device tree blob (dtb) must be placed on an 8-byte boundary and must
59 ------------------------------
71 ------------------------
75 The decompressed kernel image contains a 64-byte header as follows::
91 - As of v3.17, all fields are little endian unless stated otherwise.
93 - code0/code1 are responsible for branching to stext.
95 - when booting through EFI, code0/code1 are initially skipped.
[all …]
|
| /Documentation/trace/rv/ |
| D | runtime-verification.rst | 10 Instead of relying on a fine-grained model of a system (e.g., a
11 re-implementation a instruction level), RV works by analyzing the trace of the
17 that require a re-implementation of the entire system in a modeling language.
20 events, avoiding, for example, the propagation of a failure on safety-critical
32 system, a set of instances of the monitor (per-cpu monitor, per-task monitor,
36 Linux +---- RV Monitor ----------------------------------+ Formal
38 +-------------------+ +----------------+ +-----------------+
40 | Tracing | -> | Instance(s) | <- | Model |
42 +-------------------+ +----------------+ +-----------------+
45 | +----------+ |
[all …]
|
| /Documentation/core-api/ |
| D | entry.rst | 16 exceptions`_, `NMI and NMI-like exceptions`_.
18 Non-instrumentable code - noinstr
19 ---------------------------------
33 .. code-block:: c
37 handle_entry(); // <-- must be 'noinstr' or '__always_inline'
41 handle_context(); // <-- instrumentable code
45 handle_exit(); // <-- must be 'noinstr' or '__always_inline'
51 Invoking non-instrumentable functions from instrumentable context has no
55 All non-instrumentable entry/exit code sections before and after the RCU
59 --------
[all …]
|
| /Documentation/userspace-api/ |
| D | landlock.rst | 1 .. SPDX-License-Identifier: GPL-2.0
2 .. Copyright © 2017-2020 Mickaël Salaün <mic@digikod.net>
3 .. Copyright © 2019-2020 ANSSI
4 .. Copyright © 2021-2022 Microsoft Corporation
16 new security layers in addition to the existing system-wide access-controls.
23 ``dmesg | grep landlock || journalctl -kb -g landlock`` .
48 ----------------------------------------
59 to be explicit about the denied-by-default access rights.
61 .. code-block:: c
90 on, it is safer to follow a best-effort security approach. Indeed, we
[all …]
|
| /Documentation/userspace-api/media/drivers/ |
| D | uvcvideo.rst | 1 .. SPDX-License-Identifier: GPL-2.0
6 This file documents some driver-specific aspects of the UVC driver, such as
7 driver-specific ioctls and implementation notes.
10 linux-media@vger.kernel.org.
14 ---------------------------
19 The UVC specification allows for vendor-specific extensions through extension
23 - through mappings of XU controls to V4L2 controls
24 - through a driver-specific ioctl interface
30 The second mechanism requires uvcvideo-specific knowledge for the application to
40 The UVC driver provides an API for user space applications to define so-called
[all …]
|
| /Documentation/bpf/ |
| D | ringbuf.rst | 12 ----------
18 - more efficient memory utilization by sharing ring buffer across CPUs;
19 - preserving ordering of events that happen sequentially in time, even across
23 Both are a result of a choice to have per-CPU perf ring buffer. Both can be
25 problem could technically be solved for perf buffer with some in-kernel
30 ------------------
56 The approach chosen has an advantage of re-using existing BPF map
62 combined with ``ARRAY_OF_MAPS`` and ``HASH_OF_MAPS`` map-in-maps to implement
75 - variable-length records;
76 - if there is no more space left in ring buffer, reservation fails, no
[all …]
|
| /Documentation/scheduler/ |
| D | sched-bwc.rst | 7 The SCHED_RT case is covered in Documentation/scheduler/sched-rt-group.rst
14 microseconds of CPU time. That quota is assigned to per-cpu run queues in
22 is transferred to cpu-local "silos" on a demand basis. The amount transferred
26 -------------
30 Traditional (UP-EDF) bandwidth control is something like:
66 https://lore.kernel.org/lkml/5371BD36-55AE-4F71-B9D7-B86DC32E3D2B@linux.alibaba.com/
69 ----------
75 :ref:`Documentation/admin-guide/cgroup-v2.rst <cgroup-v2-cpu>`.
77 - cpu.cfs_quota_us: run-time replenished within a period (in microseconds)
78 - cpu.cfs_period_us: the length of a period (in microseconds)
[all …]
|
| /Documentation/bpf/libbpf/ |
| D | libbpf_overview.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 libbpf is a C-based library containing a BPF loader that takes compiled BPF
13 The following are the high-level features supported by libbpf:
15 * Provides high-level and low-level APIs for user space programs to interact
16 with BPF programs. The low-level APIs wrap all the bpf system call
17 functionality, which is useful when users need more fine-grained control
22 * Provides BPF-side APIS, including BPF helper definitions, BPF maps support,
24 * Supports BPF CO-RE mechanism, enabling BPF developers to write portable
48 (setting BPF program types, if necessary; pre-setting initial values for
87 * ``<name>__attach()`` – attaches all auto-attachable BPF programs (it’s
[all …]
|
| /Documentation/admin-guide/mm/ |
| D | userfaultfd.rst | 8 Userfaults allow the implementation of on-demand paging from userland
38 Vmas are not suitable for page- (or hugepage) granular fault tracking
48 is a corner case that would currently return ``-EBUSY``).
54 ----------------------
63 - Any user can always create a userfaultfd which traps userspace page faults
67 - In order to also trap kernel page faults for the address space, either the
77 filesystem permissions (user/group/mode), which gives fine grained access to
84 --------------------------
101 - The ``UFFD_FEATURE_EVENT_*`` flags indicate that various other events
103 detail below in the `Non-cooperative userfaultfd`_ section.
[all …]
|
| /Documentation/block/ |
| D | inline-encryption.rst | 1 .. SPDX-License-Identifier: GPL-2.0
19 keys directly in low-level I/O requests. However, most inline encryption
22 low-level I/O request then just contains a keyslot index and data unit number.
30 Inline encryption hardware is also very different from "self-encrypting drives",
31 such as those based on the TCG Opal or ATA Security standards. Self-encrypting
32 drives don't provide fine-grained control of encryption and provide no way to
34 provides fine-grained control of encryption, including the choice of key and
43 layered devices like device-mapper and loopback (i.e. we want to be able to use
50 - We need a way for upper layers (e.g. filesystems) to specify an encryption
56 - Different inline encryption hardware has different supported algorithms,
[all …]
|
| /Documentation/power/ |
| D | opp.rst | 5 (C) 2009-2010 Nishanth Menon <nm@ti.com>, Texas Instruments Incorporated
20 -------------------------------------------------
22 Complex SoCs of today consists of a multiple sub-modules working in conjunction.
25 facilitate this, sub-modules in a SoC are grouped into domains, allowing some
41 - {300000000, 1000000}
42 - {800000000, 1200000}
43 - {1000000000, 1300000}
46 ----------------------------------------
57 (users) -> registers a set of default OPPs -> (library)
58 SoC framework -> modifies on required cases certain OPPs -> OPP layer
[all …]
|
| /Documentation/dev-tools/ |
| D | kcov.rst | 5 for coverage-guided fuzzing. Coverage data of a running kernel is exported via
13 inherently non-deterministic parts of the kernel (e.g. scheduler, locking).
24 -------------
41 mount -t debugfs none /sys/kernel/debug
44 -------------------
49 .. code-block:: c
80 if (fd == -1)
85 /* Mmap buffer shared between kernel- and user-space. */
96 read(-1, NULL, 0);
134 The interface is fine-grained to allow efficient forking of test processes.
[all …]
|
| /Documentation/admin-guide/ |
| D | workload-tracing.rst | 1 .. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0)
7 :Authors: - Shuah Khan <skhan@linuxfoundation.org>
8 - Shefali Sharma <sshefali021@gmail.com>
9 :maintained-by: Shuah Khan <skhan@linuxfoundation.org>
21 `perf <https://man7.org/linux/man-pages/man1/perf.1.html>`_,
22 `stress-ng <https://www.mankier.com/1/stress-ng>`_,
23 `paxtest <https://github.com/opntr/paxtest-freebsd>`_.
30 `strace <https://man7.org/linux/man-pages/man1/strace.1.html>`_ is a
50 How do we gather fine-grained system information?
65 to gather fine-grained information on a workload's usage of system resources.
[all …]
|
| /Documentation/netlink/specs/ |
| D | netdev.yaml | 1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
9 -
11 name: xdp-act
12 render-max: true
14 -
19 -
23 -
24 name: ndo-xmit
27 -
28 name: xsk-zerocopy
[all …]
|
12