| /kernel/linux/linux-5.10/tools/testing/selftests/tc-testing/ |
| D | README | 1 tdc - Linux Traffic Control (tc) unit testing suite
3 Author: Lucas Bates - lucasb@mojatatu.com
10 ------------
24 * All tc-related features being tested must be built in or available as
26 ./tdc.py -c
30 teardown commands - which includes not being able to run a test simply
32 handled in a future version - the current workaround is to run the tests
37 --------------
44 using the -p option when running tdc:
45 ./tdc.py -p /path/to/tc
[all …]
|
| /kernel/linux/linux-6.6/tools/testing/selftests/tc-testing/ |
| D | README | 1 tdc - Linux Traffic Control (tc) unit testing suite
3 Author: Lucas Bates - lucasb@mojatatu.com
10 ------------
24 * All tc-related features being tested must be built in or available as
26 ./tdc.py -c
30 teardown commands - which includes not being able to run a test simply
32 handled in a future version - the current workaround is to run the tests
37 --------------
44 using the -p option when running tdc:
45 ./tdc.py -p /path/to/tc
[all …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/ |
| D | device-io.rst | 10 Bus-Independent Device Accesses
27 ----------------------------
49 --------------------
52 memory-mapped registers on the device. Linux provides interfaces to read
53 and write 8-bit, 16-bit, 32-bit and 64-bit quantities. Due to a
62 Some devices (such as framebuffers) would like to use larger transfers than
65 provided. Do not use memset or memcpy on IO addresses; they are not
70 can be compiler optimised, you can use __readb() and friends to
71 indicate the relaxed ordering. Use this with care.
78 writes have occurred in the specific cases the author cares. This kind
[all …]
|
| /kernel/linux/linux-5.10/Documentation/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 …]
|
| /kernel/linux/linux-6.6/Documentation/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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-6.6/tools/usb/ |
| D | hcd-tests.sh | 2 # SPDX-License-Identifier: GPL-2.0
6 # - control: any device can do this
7 # - out, in: out needs 'bulk sink' firmware, in needs 'bulk src'
8 # - iso-out, iso-in: out needs 'iso sink' firmware, in needs 'iso src'
9 # - halt: needs bulk sink+src, tests halt set/clear from host
10 # - unlink: needs bulk sink and/or src, test HCD unlink processing
11 # - loop: needs firmware that will buffer N transfers
25 # - include unlink tests
26 # - add some ${RANDOM}ness
27 # - connect several devices concurrently (same HC)
[all …]
|
| /kernel/linux/linux-5.10/tools/usb/ |
| D | hcd-tests.sh | 2 # SPDX-License-Identifier: GPL-2.0
6 # - control: any device can do this
7 # - out, in: out needs 'bulk sink' firmware, in needs 'bulk src'
8 # - iso-out, iso-in: out needs 'iso sink' firmware, in needs 'iso src'
9 # - halt: needs bulk sink+src, tests halt set/clear from host
10 # - unlink: needs bulk sink and/or src, test HCD unlink processing
11 # - loop: needs firmware that will buffer N transfers
25 # - include unlink tests
26 # - add some ${RANDOM}ness
27 # - connect several devices concurrently (same HC)
[all …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-6.6/drivers/base/firmware_loader/builtin/ |
| D | main.c | 1 // SPDX-License-Identifier: GPL-2.0
24 if (size < fw->size) in fw_copy_to_prealloc_buf()
26 memcpy(buf, fw->data, fw->size); in fw_copy_to_prealloc_buf()
31 * firmware_request_builtin() - load builtin firmware
35 * Some use cases in the kernel have a requirement so that no memory allocator
37 * the x86 CPU microcode loader. In these cases all the caller wants is to see
38 * if the firmware was built-in and if so use it right away. This can be used
39 * for such cases.
41 * This looks for the firmware in the built-in kernel. Only if the kernel was
42 * built-in with the firmware you are looking for will this return successfully.
[all …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/tools/testing/selftests/tc-testing/creating-plugins/ |
| D | AddingPlugins.txt | 1 tdc - Adding plugins for tdc
3 Author: Brenda J. Butler - bjb@mojatatu.com
6 --------------
9 There are some examples in plugin-lib.
14 - adding commands to be run before and/or after the test suite
15 - adding commands to be run before and/or after the test cases
16 - adding commands to be run before and/or after the execute phase of the test cases
17 - ability to alter the command to be run in any phase:
18 pre (the pre-suite stage)
23 post (the post-suite stage)
[all …]
|
| /kernel/linux/linux-6.6/tools/testing/selftests/tc-testing/creating-plugins/ |
| D | AddingPlugins.txt | 1 tdc - Adding plugins for tdc
3 Author: Brenda J. Butler - bjb@mojatatu.com
6 --------------
9 There are some examples in plugin-lib.
14 - adding commands to be run before and/or after the test suite
15 - adding commands to be run before and/or after the test cases
16 - adding commands to be run before and/or after the execute phase of the test cases
17 - ability to alter the command to be run in any phase:
18 pre (the pre-suite stage)
23 post (the post-suite stage)
[all …]
|
| /kernel/linux/linux-5.10/net/bluetooth/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
20 Bluetooth is low-cost, low-power, short-range wireless technology.
21 It was designed as a replacement for cables and other short-range
41 To use Linux Bluetooth subsystem, you will need several user-space
68 Bluetooth High Speed includes support for off-loading
77 Bluetooth Low Energy includes support low-energy physical
119 cases are run first thing at module load time. When the Bluetooth
120 subsystem is compiled into the kernel image, then the test cases
124 bool "ECDH test cases"
127 Run test cases for ECDH cryptographic functionality used by the
[all …]
|
| /kernel/linux/linux-6.6/net/bluetooth/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
20 Bluetooth is low-cost, low-power, short-range wireless technology.
21 It was designed as a replacement for cables and other short-range
42 To use Linux Bluetooth subsystem, you will need several user-space
70 Bluetooth Low Energy includes support low-energy physical
130 cases are run first thing at module load time. When the Bluetooth
131 subsystem is compiled into the kernel image, then the test cases
135 bool "ECDH test cases"
138 Run test cases for ECDH cryptographic functionality used by the
142 bool "SMP test cases"
[all …]
|
| /kernel/linux/linux-5.10/drivers/gpio/ |
| D | TODO | 1 This is a place for planning the ongoing long-term work in the GPIO
8 to move away from the global GPIO numberspace and toward a descriptor-based
10 ideally have no use or idea of the global GPIO numberspace that has/was
18 establish the numberspace at compile-time, making it hard to add any numbers
26 The runtime-assigned GPIO numberspace (what you get if you assign the GPIO
27 base as -1 in struct gpio_chip) has also became unpredictable due to factors
28 such as probe ordering and the introduction of -EPROBE_DEFER making probe
37 - Convert all GPIO device drivers to only #include <linux/gpio/driver.h>
39 - Convert all consumer drivers to only #include <linux/gpio/consumer.h>
41 - Convert all machine descriptors in "boardfiles" to only
[all …]
|
| /kernel/linux/linux-5.10/tools/testing/selftests/ |
| D | Makefile | 1 # SPDX-License-Identifier: GPL-2.0
11 TARGETS += cpu-hotplug
12 TARGETS += drivers/dma-buf
34 TARGETS += memory-hotplug
60 TARGETS += tc-testing
75 TARGETS_HOTPLUG = cpu-hotplug
76 TARGETS_HOTPLUG += memory-hotplug
81 TMP := $(filter-out $(SKIP_TARGETS), $(TARGETS))
92 # implicit rules to sub-test Makefiles which avoids build failures in test
113 # Make's built-in functions such as $(abspath ...), $(realpath ...) cannot
[all …]
|
| /kernel/linux/linux-6.6/drivers/gpio/ |
| D | TODO | 1 This is a place for planning the ongoing long-term work in the GPIO
8 to move away from the global GPIO numberspace and toward a descriptor-based
10 ideally have no use or idea of the global GPIO numberspace that has/was
18 establish the numberspace at compile-time, making it hard to add any numbers
26 The runtime-assigned GPIO numberspace (what you get if you assign the GPIO
27 base as -1 in struct gpio_chip) has also became unpredictable due to factors
28 such as probe ordering and the introduction of -EPROBE_DEFER making probe
37 - Convert all GPIO device drivers to only #include <linux/gpio/driver.h>
39 - Convert all consumer drivers to only #include <linux/gpio/consumer.h>
41 - Convert all machine descriptors in "boardfiles" to only
[all …]
|
| /kernel/linux/linux-6.6/lib/kunit/ |
| D | kunit-example-test.c | 1 // SPDX-License-Identifier: GPL-2.0
3 * Example KUnit test to show how to use KUnit.
55 * This is run once before all test cases in the suite.
66 * This is run once after all test cases in the suite.
150 KUNIT_EXPECT_GT_MSG(test, sizeof(int), 0, "Your ints are 0-bit?!"); in example_all_expect_macros_test()
151 KUNIT_ASSERT_GT_MSG(test, sizeof(int), 0, "Your ints are 0-bit?!"); in example_all_expect_macros_test()
168 return i - 1; in subtract_one()
172 * This test shows the use of static stubs.
200 snprintf(desc, KUNIT_PARAM_DESC_SIZE, "example value %d", p->value); in example_param_get_desc()
206 * This test shows the use of params.
[all …]
|
| /kernel/linux/linux-5.10/tools/memory-model/Documentation/ |
| D | simple.txt | 2 memory-ordering lives simple, as is necessary for those whose domain
3 is complex. After all, there are bugs other than memory-ordering bugs,
4 and the time spent gaining memory-ordering knowledge is not available
5 for gaining domain knowledge. Furthermore Linux-kernel memory model
15 of MMIO-based device drivers will often need to use mb(), rmb(), and
22 Single-threaded code
25 In single-threaded code, there is no reordering, at least assuming
38 this lock at a given time, your code will be executed single-threaded.
52 Please use the standard locking primitives provided by the kernel rather
56 surprisingly hard to correctly code production-quality lock acquisition
[all …]
|