/linux/samples/ |
H A D | Kconfig | 17 This builds the trace event example module. 20 tristate "Build custom trace event example -- loadable modules only" 23 This builds the custom trace event example module. 33 tristate "Build register_ftrace_direct() example" 37 This builds an ftrace direct function example 41 tristate "Build register_ftrace_direct() on multiple ips example" 45 This builds an ftrace direct function example 50 tristate "Build custom ftrace ops example" 53 This builds an ftrace ops example that hooks two functions and 76 This build several kprobes example modules. [all …]
|
/linux/Documentation/kbuild/ |
H A D | makefiles.rst | 88 Example:: 98 Example:: 128 Example:: 146 Example:: 151 Note: In this example $(CONFIG_ISDN_PPP_BSDCOMP) evaluates to "m" 159 Example:: 165 In this example, the module name will be isdn.o. Kbuild will 173 Example:: 182 In this example, xattr.o, xattr_user.o and xattr_trusted.o are only 209 Example:: [all …]
|
/linux/tools/bpf/bpftool/Documentation/ |
H A D | bpftool-gen.rst | 95 file name, i.e., if BPF object file name is **example.o**, BPF object name 96 will be **example**. Object name can be also specified explicitly through 98 provided (assuming **example** as the object name): 265 This is example BPF application with three BPF programs and a mix of BPF 275 **$ bpftool gen object example.bpf.o example1.bpf.o example2.bpf.o example3.bpf.o** 279 files into the final BPF ELF object file *example.bpf.o*. 281 **$ bpftool gen skeleton example.bpf.o name example | tee example.skel.h** 294 struct example { 334 static void example__destroy(struct example *obj); 335 static inline struct example *example__open_opts( [all …]
|
/linux/Documentation/admin-guide/perf/ |
H A D | hisi-pcie-pmu.rst | 35 Example usage of perf:: 54 Example usage of perf group:: 82 For example, if target Root Port is 0000:00:00.0 (x8 lanes), bit0 of 87 Example usage of perf:: 97 For example, "bdf=0x3900" means BDF of target Endpoint is 0000:39:00.0. 99 Example usage of perf:: 110 For example, "trig_len=4" means trigger condition is 2^4 DW, "trig_mode=0" 114 Example usage of perf:: 124 For example, "thr_len=4" means threshold is 2^4 DW, "thr_mode=0" means 128 Example usage of perf:: [all …]
|
H A D | hns3-pmu.rst | 41 Example usage of checking event code and subevent code:: 61 Example usage of checking supported filter mode:: 66 Example usage of perf:: 84 Example usage of perf:: 93 Example usage of perf:: 101 Example usage of perf:: 111 for example: 118 Example usage of perf:: 126 Example usage of perf:: 134 Example usage of perf::
|
/linux/Documentation/dev-tools/kunit/ |
H A D | start.rst | 97 For example, to include the kernel's linked-list test you can run:: 103 For example, to run only ``FAT_FS`` and ``EXT4`` tests you can run:: 130 For example, let's assume we are using the default config: 138 like ``"example.example_simple_test"``, to run specifically that test case:: 140 ./tools/testing/kunit/kunit.py run "example.example_simple_test" 150 If you do not want to use the KUnit Wrapper (for example: you want code 184 1. Create a file ``drivers/misc/example.h``, which includes: 190 2. Create a file ``drivers/misc/example.c``, which includes: 196 #include "example.h" 208 bool "My example" [all …]
|
H A D | style.rst | 17 example, non-deterministically producing false positives or negatives, or 45 example, subsystems could be called: 82 to be split into multiple test suites (for example, simple drivers). 89 subsystem (for example, both unit tests and integration tests), they should be 96 module name. For example, test suites could include: 108 Avoid names, for example: 117 ``integration_test``. It should be a separate test suite. For example, if the 139 Example test names include: 168 If we are not able to meet above conditions (for example, the test is unable to 171 For example, a Kconfig entry might look like: [all …]
|
H A D | running_tips.rst | 186 # Subtest: example 190 ok 1 - example 197 For example, we'd change the config options from before to 208 $ modprobe kunit-example-test 249 So using our example config: 253 $ modprobe kunit-example-test > /dev/null 254 $ cat /sys/kernel/debug/kunit/example/results 258 $ modprobe -r kunit-example-test 259 $ cat /sys/kernel/debug/kunit/example/results 260 /sys/kernel/debug/kunit/example/results: No such file or directory [all …]
|
/linux/tools/testing/kunit/test_data/ |
H A D | test_is_test_passed-all_passed_nested.log | 7 # Subtest: example 16 kunit example: all tests passed 17 ok 2 - example 24 # Subtest: example 33 kunit example: all tests passed 34 ok 2 - example
|
/linux/tools/sched_ext/ |
H A D | README.md | 1 SCHED_EXT EXAMPLE SCHEDULERS 6 This directory contains a number of example sched_ext schedulers. These 17 This README will describe these example schedulers, including describing the 25 There are a few toolchain dependencies for compiling the example schedulers. 78 You may notice that most of the example schedulers include a "vmlinux.h" file. 93 example, using vmlinux.h allows a scheduler to access fields defined directly 108 bpf_printk("Task %s enabled in example scheduler", p->comm); 115 .name = "example", 144 example above, we print out a task name with `p->comm`. CO-RE would perform 157 # Example schedulers [all …]
|
/linux/tools/testing/ktest/examples/ |
H A D | README | 1 This directory contains example configs to use ktest for various tasks. 10 crosstests.conf - this config shows an example of testing a git repo against 16 test.conf - A generic example of a config. This is based on an actual config 19 kvm.conf - A example of a config that is used to test a virtual guest running 22 snowball.conf - An example config that was used to demo ktest.pl against 26 included into other configs. This is a real use example that shows how
|
/linux/Documentation/ABI/testing/ |
H A D | ima_policy | 74 For example, "selinux" to measure critical data for SELinux. 76 For example, "sha256,sha512" to only accept to appraise 141 Example of measure rules using alternate PCRs:: 146 Example of appraise rule allowing modsig appended signatures: 150 Example of measure rule using KEY_CHECK to measure all keys: 154 Example of measure rule using KEY_CHECK to only measure 159 Example of the special SETXATTR_CHECK appraise rule, that 165 Example of a 'measure' rule requiring fs-verity's digests 171 Example of 'measure' and 'appraise' rules requiring fs-verity 188 All of these policy rules could, for example, be constrained
|
/linux/Documentation/driver-api/dmaengine/ |
H A D | dmatest.rst | 41 Example of usage:: 57 Example of multi-channel test usage (new in the 5.0 kernel):: 96 before returning. For example, the following scripts wait for 42 tests 100 Example:: 131 Example of output:: 142 Example:: 160 Example:: 168 Example:: 173 More channels can be added by repeating the example above. 176 Example:: [all …]
|
/linux/Documentation/leds/ |
H A D | leds-lm3556.rst | 28 * if STROBE pin is enabled, below example control brightness only, and 31 Flash Example: 55 * if TORCH pin is enabled, below example control brightness only, 58 Torch Example: 86 Indicator pattern example: 101 Example: 123 Example:: 134 Example::
|
/linux/tools/power/pm-graph/config/ |
H A D | custom-timeline-functions.cfg | 92 # example: _cpu_up: 99 # example: CPU_ON[{cpu}] 105 # example: [color=#CC00CC] 110 # example: cpu=%di:s32 112 # Example: Display cpu resume in the timeline 157 # example: ata_eh_recover: 164 # example: ata{port}_port_reset 170 # example: [color=#CC00CC] 175 # example: port=+36(%di):s32 177 # Example: Display ATA port reset as ataN_port_reset in the timeline
|
/linux/Documentation/admin-guide/gpio/ |
H A D | gpio-aggregator.rst | 51 Example: Instantiate a new GPIO aggregator by aggregating GPIO 64 Example: Destroy the previously-created aggregated GPIO 79 **Group:** ``/config/gpio-aggregator/<example-name>`` 82 name to ``<example-name>`` (e.g. ``agg0``), except names starting with 86 **Attribute:** ``/config/gpio-aggregator/<example-name>/live`` 94 **Attribute:** ``/config/gpio-aggregator/<example-name>/dev_name`` 108 **Group:** ``/config/gpio-aggregator/<example-name>/<lineY>/`` 112 **Attribute:** ``/config/gpio-aggregator/<example-name>/<lineY>/key`` 114 **Attribute:** ``/config/gpio-aggregator/<example-name>/<lineY>/offset`` 134 **Attribute:** ``/config/gpio-aggregator/<example-name>/<lineY>/name`` [all …]
|
/linux/rust/kernel/sync/ |
H A D | arc.rs | 54 /// struct Example { 59 /// // Create a refcounted instance of `Example`. 60 /// let obj = Arc::new(Example { a: 10, b: 20 }, GFP_KERNEL)?; 84 /// struct Example { 89 /// impl Example { 99 /// let obj = Arc::new(Example { a: 10, b: 20 }, GFP_KERNEL)?; 105 /// Coercion from `Arc<Example>` to `Arc<dyn MyTrait>`: 118 /// struct Example; 119 /// impl MyTrait for Example {} 121 /// // `obj` has type `Arc<Example>`. [all …]
|
/linux/tools/memory-model/Documentation/ |
H A D | control-dependencies.txt | 22 from "a". This means that an explicit read barrier is required, for example 33 following example: 50 the original example by eliminating the "if" statement as follows: 91 have been applied. Therefore, if you need ordering in this example, 92 you must use explicit memory ordering, for example, smp_store_release(): 104 guaranteed only when the stores differ, for example: 121 preserve ordering. For example: 164 evaluation. Consider this example: 171 always true, the compiler can transform this example as follows, again 177 This is yet another example showing the importance of preventing the [all …]
|
H A D | access-marking.txt | 18 1. Plain C-language accesses (unmarked), for example, "a = b;" 20 2. Data-race marking, for example, "data_race(a = b);" 22 3. READ_ONCE(), for example, "a = READ_ONCE(b);" 25 4. WRITE_ONCE(), for example, "WRITE_ONCE(a, b);" 28 5. __data_racy, for example "int __data_racy a;" 35 example: 46 C-language accesses. It is permissible to combine #2 and #3, for example, 89 the core concurrency design. For example, suppose that the core design 98 KCSAN diagnostics, use both data_race() and READ_ONCE(), for example, 112 is not a problem. For example, if a bogus value is fed into cmpxchg(), [all …]
|
/linux/samples/kfifo/ |
H A D | Makefile | 2 obj-$(CONFIG_SAMPLE_KFIFO) += bytestream-example.o dma-example.o inttype-example.o record-example.o
|
/linux/samples/user_events/ |
H A D | Makefile | 4 example: example.o target 5 example.o: example.c
|
/linux/Documentation/devicetree/bindings/regulator/ |
H A D | da9211.txt | 21 Example 1) DA9211 41 Example 2) DA9212 67 Example 3) DA9213 85 Example 4) DA9223 103 Example 5) DA9214 129 Example 6) DA9224 155 Example 7) DA9215 181 Example 8) DA9225
|
/linux/Documentation/input/ |
H A D | uinput.rst | 40 This first example shows how to create a new virtual device, and how to 80 strcpy(usetup.name, "Example device"); 90 * to send. This pause is only needed in our example code! 115 This example shows how to create a virtual device that behaves like a physical 122 /* emit function is identical to of the first example */ 143 strcpy(usetup.name, "Example device"); 153 * to send. This pause is only needed in our example code! 191 /* emit function is identical to of the first example */ 224 * to send. This pause is only needed in our example code!
|
/linux/Documentation/userspace-api/ |
H A D | dma-buf-alloc-exchange.rst | 64 One of the dimensions in a color model. For example, RGB model has 108 For example, ``DRM_FORMAT_ARGB8888`` describes a format in which each pixel has 115 As a more complex example, ``DRM_FORMAT_NV12`` describes a format in which luma 128 making use of tiled access and possibly also compression. For example, the 135 example, the ``I915_FORMAT_MOD_Y_TILED_CCS`` modifier adds a second plane to RGB 151 underlying memory storage. For example, even though a 1920x1080 163 buffer; for example, ``DRM_FORMAT_NV12`` may be stored in a single memory buffer 169 between two contiguous row. For example, a ``DRM_FORMAT_MOD_LINEAR`` buffer 177 larger area than would ordinarily be required. For example, many media decoders 204 lists. For example, if a user wants to use Vulkan to render an image to be [all …]
|
/linux/Documentation/trace/rv/ |
H A D | deterministic_automata.rst | 19 For example, a given automaton named 'wip' (wakeup in preemptive) can 32 in multiple formats. For example, using a *graphical representation*, using 55 For example, the 'wip' automata can be presented as (augmented with comments):: 102 in O(1). For example:: 113 For example, this is the 'wip' model in DOT:: 143 in the example above and automatically convert it to the C representation 146 For example, having the previous 'wip' model into a file named 'wip.dot', 161 For example, the formal description using set theory is better suitable
|