Home
last modified time | relevance | path

Searched +full:i +full:- +full:leak +full:- +full:current (Results 1 – 21 of 21) sorted by relevance

/Documentation/devicetree/bindings/power/
Dpower_domain.txt5 current.
12 #power-domain-cells property in the PM domain provider node.
16 See power-domain.yaml.
21 - power-domains : A list of PM domain specifiers, as defined by bindings of
25 - power-domain-names : A list of power domain name strings sorted in the same
26 order as the power-domains property. Consumers drivers will use
27 power-domain-names to match power domains with power-domains
32 leaky-device@12350000 {
33 compatible = "foo,i-leak-current";
35 power-domains = <&power 0>;
[all …]
Dqcom,rpmpd.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Bjorn Andersson <andersson@kernel.org>
19 - enum:
20 - qcom,mdm9607-rpmpd
21 - qcom,msm8226-rpmpd
22 - qcom,msm8909-rpmpd
23 - qcom,msm8916-rpmpd
24 - qcom,msm8917-rpmpd
[all …]
/Documentation/security/
Dlandlock.rst1 .. SPDX-License-Identifier: GPL-2.0
2 .. Copyright © 2017-2020 Mickaël Salaün <mic@digikod.net>
3 .. Copyright © 2019-2020 ANSSI
12 Landlock's goal is to create scoped access-control (i.e. sandboxing). To
15 backdoored (i.e. untrusted), Landlock's features must be safe to use from the
21 LSM). A Landlock rule shall not interfere with other access-controls enforced
29 Documentation/userspace-api/landlock.rst.
35 of syscall filtering (i.e. syscall arguments), which is the purpose of
36 seccomp-bpf.
37 * To avoid multiple kinds of side-channel attacks (e.g. leak of security
[all …]
/Documentation/process/
Dmaintainer-kvm-x86.rst1 .. SPDX-License-Identifier: GPL-2.0
7 --------
17 -----
21 -----
25 specific tree, ``github.com/kvm-x86/linux.git``.
27 Generally speaking, fixes for the current cycle are applied directly to the
29 KVM x86 tree. In the unlikely event that a fix for the current cycle is routed
33 Note, this transition period is expected to last quite some time, i.e. will be
39 using finer-grained topic branches is to make it easier to keep tabs on an area
42 in-flight commits' SHA1 hashes, and having to reject a pull request due to bugs
[all …]
Dhandling-regressions.rst1 .. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0)
7 *We don't cause regressions* -- this document describes what this "first rule of
9 Documentation/admin-guide/reporting-regressions.rst, which covers the topic from a
21 loop by immediately sending at least a brief "Reply-all" with the list
30 introduced: v5.13..v5.14-rc1``. If not, send a reply (with the regressions
39 #regzbot introduced: v5.13..v5.14-rc1
45 mandated by Documentation/process/submitting-patches.rst and
61 -----------------------------------
72 it into the loop by sending at least a brief "Reply-all" with the list CCed;
79 Documentation/admin-guide/reporting-issues.rst.
[all …]
Dmaintainer-netdev.rst1 .. SPDX-License-Identifier: GPL-2.0
3 .. _netdev-FAQ:
10 -----
12 - designate your patch to a tree - ``[PATCH net]`` or ``[PATCH net-next]``
13 - for fixes the ``Fixes:`` tag is required, regardless of the tree
14 - don't post large series (> 15 patches), break them up
15 - don't repost your patches within one 24h period
16 - reverse xmas tree
19 ------
21 netdev is a mailing list for all network-related Linux stuff. This
[all …]
/Documentation/scsi/
DChangeLog.megaraid_sas1 Release Date : Thu. Jun 19, 2014 17:00:00 PST 2014 -
2 (emaild-id:megaraidlinux@lsi.com)
7 Current Version : 06.803.02.00-rc1
8 Old Version : 06.803.01.00-rc1
9 1. Fix reset_mutex leak in megasas_reset_fusion().
14 -------------------------------------------------------------------------------
15 Release Date : Mon. Mar 10, 2014 17:00:00 PST 2014 -
16 (emaild-id:megaraidlinux@lsi.com)
20 Current Version : 06.803.01.00-rc1
21 Old Version : 06.700.06.00-rc1
[all …]
/Documentation/admin-guide/hw-vuln/
Dcore-scheduling.rst1 .. SPDX-License-Identifier: GPL-2.0
15 ----------------
16 A cross-HT attack involves the attacker and victim running on different Hyper
18 full mitigation of cross-HT attacks is to disable Hyper Threading (HT). Core
19 scheduling is a scheduler feature that can mitigate some (not all) cross-HT
21 user-designated trusted group can share a core. This increase in core sharing
27 core involves additional overhead - especially when the system is lightly
29 scheduling to perform more poorly compared to SMT-disabled, where N_CPUS is the
33 -----
35 Using this feature, userspace defines groups of tasks that can be co-scheduled
[all …]
Dl1tf.rst1 L1TF - L1 Terminal Fault
10 -------------------
15 - Processors from AMD, Centaur and other non Intel vendors
17 - Older processor models, where the CPU family is < 6
19 - A range of Intel ATOM processors (Cedarview, Cloverview, Lincroft,
22 - The Intel XEON PHI family
24 - Intel processors which have the ARCH_CAP_RDCL_NO bit set in the
33 ------------
38 CVE-2018-3615 L1 Terminal Fault SGX related aspects
39 CVE-2018-3620 L1 Terminal Fault OS, SMM related aspects
[all …]
Dtsx_async_abort.rst1 .. SPDX-License-Identifier: GPL-2.0
3 TAA - TSX Asynchronous Abort
11 -------------------
23 ------------
28 CVE-2019-11135 TAA TSX Asynchronous Abort (TAA) condition on some
36 -------
43 hardware transactional memory support to improve performance of multi-threaded
58 Because the buffers are potentially shared between Hyper-Threads cross
59 Hyper-Thread attacks are possible.
70 ----------------
[all …]
Dprocessor_mmio_stale_data.rst5 Processor MMIO Stale Data Vulnerabilities are a class of memory-mapped I/O
24 read into an architectural, software-visible state or sampled from a buffer or
28 -----------------------------------------
29 Stale data may propagate from fill buffers (FB) into the non-coherent portion
30 of the uncore on some non-coherent writes. Fill buffer propagation by itself
35 -------------------------------------
38 shared by all client cores. For non-coherent reads that go to sideband
45 ------------------------------------
55 Device Register Partial Write (DRPW) (CVE-2022-21166)
56 -----------------------------------------------------
[all …]
/Documentation/dev-tools/kunit/
Dusage.rst1 .. SPDX-License-Identifier: GPL-2.0
7 ----------
13 .. code-block:: c
38 .. code-block:: c
48 ``struct kunit *``, which contains information about the current test context.
59 To learn about more KUnit expectations, see Documentation/dev-tools/kunit/api/test.rst.
69 .. code-block:: c
79 KUNIT_EXPECT_EQ(test, 0, add(-1, 1));
85 KUNIT_EXPECT_EQ(test, -1, add(INT_MAX, INT_MIN));
99 .. code-block:: c
[all …]
/Documentation/virt/kvm/x86/
Dtimekeeping.rst1 .. SPDX-License-Identifier: GPL-2.0
4 Timekeeping Virtualization for X86-Based Architectures
32 information relevant to KVM and hardware-based virtualization.
41 2.1. i8254 - PIT
42 ----------------
46 channels which can be programmed to deliver periodic or one-shot interrupts.
53 The PIT uses I/O ports 0x40 - 0x43. Access to the 16-bit counters is done
54 using single or multiple byte access to the I/O ports. There are 6 modes
59 -------------- ----------------
61 | 1.1932 MHz|---------->| CLOCK OUT | ---------> IRQ 0
[all …]
/Documentation/admin-guide/
Dcgroup-v2.rst1 .. _cgroup-v2:
11 conventions of cgroup v2. It describes all userland-visible aspects
14 v1 is available under :ref:`Documentation/admin-guide/cgroup-v1/index.rst <cgroup-v1>`.
19 1-1. Terminology
20 1-2. What is cgroup?
22 2-1. Mounting
23 2-2. Organizing Processes and Threads
24 2-2-1. Processes
25 2-2-2. Threads
26 2-3. [Un]populated Notification
[all …]
Dkernel-parameters.txt16 force -- enable ACPI if default was off
17 on -- enable ACPI but allow fallback to DT [arm64,riscv64]
18 off -- disable ACPI if default was on
19 noirq -- do not use ACPI for IRQ routing
20 strict -- Be less tolerant of platforms that are not
22 rsdt -- prefer RSDT over (default) XSDT
23 copy_dsdt -- copy DSDT to memory
24 nospcr -- disable console in ACPI SPCR table as
41 If set to vendor, prefer vendor-specific driver
73 Documentation/firmware-guide/acpi/debug.rst for more information about
[all …]
/Documentation/locking/
Dlockdep-design.rst8 Lock-class
9 ----------
19 The validator tracks the 'usage state' of lock-classes, and it tracks
20 the dependencies between different lock-classes. Lock usage indicates
22 dependency can be understood as lock order, where L1 -> L2 suggests that
29 A lock-class's behavior is constructed by its instances collectively:
30 when the first instance of a lock-class is used after bootup the class
33 the class. A lock-class does not go away when a lock instance does, but
39 -----
41 The validator tracks lock-class usage history and divides the usage into
[all …]
/Documentation/arch/powerpc/
Dultravisor.rst1 .. SPDX-License-Identifier: GPL-2.0
16 (PVR=0x004e1203) or greater will be PEF-capable. A new ISA release
25 +------------------+
29 +------------------+
31 +------------------+
33 +------------------+
35 +------------------+
42 leak. All hypercalls except H_RANDOM are reflected to the hypervisor.
55 * There is a new bit in the MSR that determines whether the current
75 +---+---+---+---------------+
[all …]
/Documentation/admin-guide/sysctl/
Dkernel.rst5 .. See scripts/check-sysctl-docs to keep this up to date
13 Documentation/admin-guide/sysctl/index.rst.
15 ------------------------------------------------------------------------------
39 If BSD-style process accounting is enabled these values control
71 The machine hardware name, the same output as ``uname -m``
129 Ctrl-Alt-Delete). Writing a value to this file which doesn't
130 correspond to a running process will result in ``-ESRCH``.
132 See also `ctrl-alt-del`_.
166 %i tid
167 %I global tid (init PID namespace)
[all …]
/Documentation/
Dmemory-barriers.txt19 documentation at tools/memory-model/. Nevertheless, even this memory
37 Note also that it is possible that a barrier may be a no-op for an
48 - Device operations.
49 - Guarantees.
53 - Varieties of memory barrier.
54 - What may not be assumed about memory barriers?
55 - Address-dependency barriers (historical).
56 - Control dependencies.
57 - SMP barrier pairing.
58 - Examples of memory barrier sequences.
[all …]
/Documentation/driver-api/
Dipmi.rst12 standardized database for field-replaceable units (FRUs) and a watchdog
22 subject and I can't cover it all here!
25 -------------
32 No matter what, you must pick 'IPMI top-level message handler' to use
35 The message handler does not provide any user-level interfaces.
50 these enabled and let the drivers auto-detect what is present.
61 "The SMBus Driver" on how to hand-configure your system.
65 the kernel, then via a kernel command-line option you can have the
74 'IPMI Poweroff' to do this. The driver will auto-detect if the system
89 ------------
[all …]
/Documentation/filesystems/xfs/
Dxfs-online-fsck-design.rst1 .. SPDX-License-Identifier: GPL-2.0
8 Heading 3 uses "----"
25 - To help kernel distributors understand exactly what the XFS online fsck
28 - To help people reading the code to familiarize themselves with the relevant
31 - To help developers maintaining the system by capturing the reasons
59 - Provide a hierarchy of names through which application programs can associate
62 - Virtualize physical storage media across those names, and
64 - Retrieve the named data blobs at any time.
66 - Examine resource usage.
79 cross-references different types of metadata records with each other to look
[all …]