Searched +full:use +full:- +full:cases (Results 1 – 25 of 567) sorted by relevance
12345678910>>...23
| /Documentation/dev-tools/kunit/ |
| D | usage.rst | 1 .. SPDX-License-Identifier: GPL-2.0
6 Test Cases
7 ----------
13 .. code-block:: c
38 .. code-block:: c
59 To learn about more KUnit expectations, see Documentation/dev-tools/kunit/api/test.rst.
66 additional tests cases which would test each property that an ``add`` function
69 .. code-block:: c
79 KUNIT_EXPECT_EQ(test, 0, add(-1, 1));
85 KUNIT_EXPECT_EQ(test, -1, add(INT_MAX, INT_MIN));
[all …]
|
| D | architecture.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 - `In-Kernel Testing Framework`_
10 - `kunit_tool (Command-line Test Harness)`_
12 In-Kernel Testing Framework
19 - Organizes tests
20 - Reports test results
21 - Provides test utilities
23 Test Cases
24 ----------
26 The test case is the fundamental unit in KUnit. KUnit test cases are organised
[all …]
|
| /Documentation/power/regulator/ |
| D | design.rst | 9 ------
11 - Errors in regulator configuration can have very serious consequences
13 - It is not possible to automatically determine the power configuration
14 of the system - software-equivalent variants of the same chip may
24 Consumer use cases
25 ------------------
27 - The overwhelming majority of devices in a system will have no
31 - Many of the power supplies in the system will be shared between many
36 The consumer API should be structured so that these use cases are
|
| /Documentation/process/ |
| D | deprecated.rst | 1 .. SPDX-License-Identifier: GPL-2.0
21 ------------
33 ------------------
34 Use WARN() and WARN_ON() instead, and handle the "impossible"
35 error condition as gracefully as possible. While the BUG()-family
42 <https://lore.kernel.org/lkml/CA+55aFy6jNLsywVYdGp83AMrXBo_P-pkjkphPGrO=82SPKCpLQ@mail.gmail.com/>`_
44 <https://lore.kernel.org/lkml/CAHk-=whDHsbK3HTOpTF=ue_o04onRwTEaK_ZoJp_fjbqq4+=Jw@mail.gmail.com/>`…
46 Note that the WARN()-family should only be used for "expected to
48 but undesirable" situations, please use the pr_warn()-family of
54 open-coded arithmetic in allocator arguments
[all …]
|
| /Documentation/devicetree/bindings/iommu/ |
| D | iommu.txt | 13 Example: 32-bit DMA to 64-bit physical addresses
15 * Implement scatter-gather at page level granularity so that the device does
29 IOMMUs can be single-master or multiple-master. Single-master IOMMU devices
30 typically have a fixed association to the master device, whereas multiple-
34 "dma-ranges" property that describes how the physical address space of the
35 IOMMU maps to memory. An empty "dma-ranges" property means that there is a
39 --------------------
40 - #iommu-cells: The number of cells in an IOMMU specifier needed to encode an
44 the specific IOMMU. Below are a few examples of typical use-cases:
46 - #iommu-cells = <0>: Single master IOMMU devices are not configurable and
[all …]
|
| /Documentation/devicetree/bindings/interconnect/ |
| D | qcom,bcm-voter.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/interconnect/qcom,bcm-voter.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Qualcomm BCM-Voter Interconnect
10 - Georgi Djakov <georgi.djakov@linaro.org>
22 - qcom,bcm-voter
24 qcom,tcs-wait:
34 In most cases, it's necessary to wait in both the AMC and WAKE sets to
35 ensure resources are available before use. If a specific RSC and its use
[all …]
|
| /Documentation/i2c/ |
| D | fault-codes.rst | 5 This is a summary of the most important conventions for use of fault
10 ----------------------------------
14 some cases, such as re-initializing (and maybe resetting). After such
27 -------------------------
29 some positive number indicating a non-fault return. The specific
31 though most Linux systems use <asm-generic/errno*.h> numbering.
34 codes that may be returned, and other cases where these codes should
36 cases (unless the hardware doesn't provide unique fault reports).
44 they are requested to use such an address.
61 host. Note that even if PECs are in use, you should not rely
[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 ------------------
39 with existing perf buffer use in BPF, but would fail if application needed more
42 Additionally, given the performance of BPF ringbuf, many use cases would just
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
[all …]
|
| D | bpf_devel_QA.rst | 10 Documentation/process/submitting-patches.rst. This document only describes
21 --------------------------------------------
48 ------------------------------------------------------------------------
49 A: BPF CI is GitHub based and hosted at https://github.com/kernel-patches/bpf.
55 - Create a fork of the aforementioned repository in your own account (one time
58 - Clone the fork locally, check out a new branch tracking either the bpf-next
59 or bpf branch, and apply your to-be-tested patches on top of it
61 - Push the local branch to your fork and create a pull request against
62 kernel-patches/bpf's bpf-next_base or bpf_base branch, respectively
68 Note furthermore that both base branches (bpf-next_base and bpf_base) will be
[all …]
|
| /Documentation/userspace-api/ |
| D | mseal.rst | 1 .. SPDX-License-Identifier: GPL-2.0
17 such an attacker primitive can break control-flow integrity guarantees
18 since read-only memory that is supposed to be trusted can become writable
29 -----------------------
34 - The start address must be in an allocated VMA.
35 - The start address must be page aligned.
36 - The end address (**addr** + **len**) must be in an allocated VMA.
37 - no gap (unallocated memory) between start and end address.
41 **flags**: reserved for future use.
44 - **0**: Success.
[all …]
|
| /Documentation/networking/ |
| D | mptcp.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 `RFC 8684 (MPTCPv1) <https://www.rfc-editor.org/rfc/rfc8684.html>`_. It allows a
12 device to make use of multiple interfaces at once to send and receive TCP
15 fail-over if one path is down, and the traffic is seamlessly reinjected on other
22 Use cases
25 Thanks to MPTCP, being able to use multiple paths in parallel or simultaneously
26 brings new use-cases, compared to TCP:
28 - Seamless handovers: switching from one path to another while preserving
29 established connections, e.g. to be used in mobility use-cases, like on
31 - Best network selection: using the "best" available path depending on some
[all …]
|
| /Documentation/arch/powerpc/ |
| D | ultravisor.rst | 1 .. SPDX-License-Identifier: GPL-2.0
16 (PVR=0x004e1203) or greater will be PEF-capable. A new ISA release
25 +------------------+
29 +------------------+
31 +------------------+
33 +------------------+
35 +------------------+
62 to return to a SVM it must use an ultracall. It can determine if
75 +---+---+---+---------------+
79 +---+---+---+---------------+
[all …]
|
| /Documentation/devicetree/bindings/ |
| D | writing-bindings.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 Documentation/devicetree/bindings/submitting-patches.rst
17 - DO attempt to make bindings complete even if a driver doesn't support some
21 - DON'T refer to Linux or "device driver" in bindings. Bindings should be
24 - DO use node names matching the class of the device. Many standard names are
27 - DO check that the example matches the documentation especially after making
30 - DON'T create nodes just for the sake of instantiating drivers. Multi-function
34 - DON'T use 'syscon' alone without a specific compatible string. A 'syscon'
42 - DO make 'compatible' properties specific. DON'T use wildcards in compatible
43 strings. DO use fallback compatibles when devices are the same as or a subset
[all …]
|
| /Documentation/livepatch/ |
| D | reliable-stacktrace.rst | 16 to identify which functions are live is to use a stacktrace.
19 functions with live state, and best-effort approaches which can be helpful for
38 * The return code is non-zero to indicate that the trace is not reliable.
41 In some cases it is legitimate to omit specific functions from the trace,
42 but all other functions must be reported. These cases are described in
45 Secondly, the reliable stacktrace function must be robust to cases where
47 function should attempt to detect such cases and return a non-zero error
49 an unsafe way. Specific cases are described in further detail below.
52 3. Compile-time analysis
55 To ensure that kernel code can be correctly unwound in all cases,
[all …]
|
| D | callbacks.rst | 5 Livepatch (un)patch-callbacks provide a mechanism for livepatch modules
10 - Safe updates to global data
12 - "Patches" to init and probe functions
14 - Patching otherwise unpatchable code (i.e. assembly)
16 In most cases, (un)patch callbacks will need to be used in conjunction
25 - Module init/exit code doesn't run when disabling and re-enabling a
28 - A module notifier can't stop a to-be-patched module from loading.
39 * Pre-patch
40 - before a klp_object is patched
42 * Post-patch
[all …]
|
| D | shadow-vars.rst | 11 The implementation introduces a global, in-kernel hashtable that
30 meta-data and shadow-data:
32 - meta-data
34 - obj - pointer to parent object
35 - id - data identifier
37 - data[] - storage for shadow data
41 They also allow to call a custom constructor function when a non-zero
48 * klp_shadow_get() - retrieve a shadow variable data pointer
49 - search hashtable for <obj, id> pair
51 * klp_shadow_alloc() - allocate and add a new shadow variable
[all …]
|
| /Documentation/crypto/ |
| D | index.rst | 10 for cryptographic use cases, as well as programming examples.
17 api-intro
20 async-tx-api
21 asymmetric-keys
22 devel-algos
23 userspace-if
26 api-samples
27 descore-readme
|
| /Documentation/RCU/ |
| D | rcuref.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Reference-count design for elements of lists/arrays protected by RCU
8 Please note that the percpu-ref feature is likely your first
10 include/linux/percpu-refcount.h for more information. However, in
11 those unusual cases where percpu-ref would consume too much memory,
14 ------------------------------------------------------------------------
26 atomic_set(&el->rc, 1); atomic_inc(&el->rc);
37 if(atomic_dec_and_test(&el->rc)) ...
42 if (atomic_dec_and_test(&el->rc))
51 has already been deleted from the list/array. Use atomic_inc_not_zero()
[all …]
|
| D | lockdep.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 aware of when each task enters and leaves any flavor of RCU read-side
18 rcu_read_lock_bh_held() for RCU-bh.
19 rcu_read_lock_sched_held() for RCU-sched.
20 rcu_read_lock_any_held() for any of normal RCU, RCU-bh, and RCU-sched.
33 Check for RCU read-side critical section.
35 Check for RCU-bh read-side critical section.
37 Check for RCU-sched read-side critical section.
39 Check for SRCU read-side critical section.
41 Use explicit check expression "c" along with
[all …]
|
| /Documentation/gpu/ |
| D | vkms.rst | 7 .. kernel-doc:: drivers/gpu/drm/vkms/vkms_drv.c
31 Now, to load the driver, use::
39 which are exposed as module options. You can use the `modinfo` command
46 use::
50 To disable the driver, use ::
52 sudo modprobe -r vkms
60 `here <https://gitlab.freedesktop.org/drm/igt-gpu-tools>`_ .
65 sudo systemctl isolate multi-user.target
71 Once you are in text only mode, you can run tests using the --device switch
73 to test. IGT_DEVICE can also be used with the run-test.sh script to run the
[all …]
|
| /Documentation/firmware-guide/acpi/ |
| D | DSD-properties-rules.rst | 1 .. SPDX-License-Identifier: GPL-2.0
22 In the ACPI _DSD context it is an element of the sub-package following the
24 section titled "Well-Known _DSD UUIDs and Data Structure Formats" sub-section
29 that can be returned by _DSD in the Device Properties UUID sub-package for a
34 can be returned in the Device Properties UUID sub-package for the device in
41 section titled "Well-Known _DSD UUIDs and Data Structure Formats" sub-section
58 provisions for handling the underlying use case. It generally is invalid to
63 -------------------------
65 There are cases in which, even if the general rule given above is followed in
77 In all cases in which kernel code may do something that will confuse AML as a
[all …]
|
| /Documentation/ABI/testing/ |
| D | debugfs-cros-ec | 1 What: /sys/kernel/debug/<cros-ec-device>/console_log
10 What: /sys/kernel/debug/<cros-ec-device>/panicinfo
18 What: /sys/kernel/debug/<cros-ec-device>/pdinfo
23 information for all the USB PD/type-C ports available. If
27 What: /sys/kernel/debug/<cros-ec-device>/uptime
36 What: /sys/kernel/debug/<cros-ec-device>/last_resume_result
41 the (Intel) processor's SLP_S0 line, in order to detect cases
51 Callers can use this to detect a wake from the EC due to
58 What: /sys/kernel/debug/<cros-ec-device>/suspend_timeout_ms
63 a hardware-controlled sleep line, such as Intel's SLP_S0 line,
[all …]
|
| /Documentation/driver-api/pci/ |
| D | p2pdma.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 PCI Peer-to-Peer DMA Support
9 called Peer-to-Peer (or P2P). However, there are a number of issues that
23 The second issue is that to make use of existing interfaces in Linux,
36 * Provider - A driver which provides or publishes P2P resources like
38 * Client - A driver which makes use of a resource by setting up a
40 * Orchestrator - A driver which orchestrates the flow of data between
43 In many cases there could be overlap between these three types (i.e.,
51 to be used directly (client) and it can also make use of the CMB as
62 then the NVMe Target could use the RNIC's memory instead of the CMB
[all …]
|
| /Documentation/arch/arm/omap/ |
| D | omap_pm.rst | 6 authors use these functions to communicate minimum latency or
13 - support the range of power management parameters present in the TI SRF;
15 - separate the drivers from the underlying PM parameter
19 - specify PM parameters in terms of fundamental units, such as
23 - allow drivers which are shared with other architectures (e.g.,
24 DaVinci) to add these constraints in a way which won't affect non-OMAP
27 - can be implemented immediately with minimal disruption of other
36 (*pdata->set_max_mpu_wakeup_lat)(struct device *dev, unsigned long t)
40 (*pdata->set_max_dev_wakeup_lat)(struct device *dev, unsigned long t)
44 (*pdata->set_max_sdma_lat)(struct device *dev, long t)
[all …]
|
| /Documentation/mm/ |
| D | page_frags.rst | 5 A page fragment is an arbitrary-length arbitrary-offset area of memory
13 memory for use as either an sk_buff->head, or to be used in the "frags"
16 In order to make use of the page fragment APIs a backing page fragment
18 and tracks allows multiple calls to make use of a cached page. The
22 either a per-cpu limitation, or a per-cpu limitation and forcing interrupts
26 allocation. The netdev_alloc_cache is used by callers making use of the
34 Many network device drivers use a similar methodology for allocating page
36 level. In order to enable these cases it is necessary to provide a generic
|
12345678910>>...23