| /kernel/linux/linux-5.10/samples/trace_events/ |
| D | trace-events-sample.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
8 * In this case, it would look for sample-trace.h
14 * This file is called trace-events-sample.h but we want the system
15 * to be called "sample-trace". Therefore we must define the name of this
18 * #define TRACE_INCLUDE_FILE trace-events-sample
26 #define TRACE_SYSTEM sample-trace
29 * TRACE_SYSTEM is expected to be a C valid variable (alpha-numeric
36 * But the above is only needed if TRACE_SYSTEM is not alpha-numeric
38 * TRACE_SYSTEM. As TRACE_SYSTEM_VAR must be alpha-numeric, if
40 * only alpha-numeric and underscores.
[all …]
|
| /kernel/linux/linux-6.6/samples/trace_events/ |
| D | trace-events-sample.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
8 * In this case, it would look for sample-trace.h
14 * This file is called trace-events-sample.h but we want the system
15 * to be called "sample-trace". Therefore we must define the name of this
18 * #define TRACE_INCLUDE_FILE trace-events-sample
26 #define TRACE_SYSTEM sample-trace
29 * TRACE_SYSTEM is expected to be a C valid variable (alpha-numeric
36 * But the above is only needed if TRACE_SYSTEM is not alpha-numeric
38 * TRACE_SYSTEM. As TRACE_SYSTEM_VAR must be alpha-numeric, if
40 * only alpha-numeric and underscores.
[all …]
|
| /kernel/linux/linux-5.10/tools/testing/selftests/bpf/prog_tests/ |
| D | cgroup_attach_override.c | 1 // SPDX-License-Identifier: GPL-2.0
7 #define FOO "/foo" macro
8 #define BAR "/foo/bar/" macro
9 #define PING_CMD "ping -q -c1 -w1 127.0.0.1 > /dev/null"
28 int drop_prog = -1, allow_prog = -1, foo = -1, bar = -1; in test_cgroup_attach_override() local
33 "verifier output:\n%s\n-------\n", bpf_log_buf)) in test_cgroup_attach_override()
38 "verifier output:\n%s\n-------\n", bpf_log_buf)) in test_cgroup_attach_override()
41 foo = test__join_cgroup(FOO); in test_cgroup_attach_override()
42 if (CHECK(foo < 0, "cgroup_join_foo", "cgroup setup failed\n")) in test_cgroup_attach_override()
45 if (CHECK(bpf_prog_attach(drop_prog, foo, BPF_CGROUP_INET_EGRESS, in test_cgroup_attach_override()
[all …]
|
| /kernel/linux/linux-6.6/tools/testing/selftests/bpf/prog_tests/ |
| D | cgroup_attach_override.c | 1 // SPDX-License-Identifier: GPL-2.0
7 #define FOO "/foo" macro
8 #define BAR "/foo/bar/" macro
9 #define PING_CMD "ping -q -c1 -w1 127.0.0.1 > /dev/null"
28 int drop_prog = -1, allow_prog = -1, foo = -1, bar = -1; in serial_test_cgroup_attach_override() local
33 "verifier output:\n%s\n-------\n", bpf_log_buf)) in serial_test_cgroup_attach_override()
38 "verifier output:\n%s\n-------\n", bpf_log_buf)) in serial_test_cgroup_attach_override()
41 foo = test__join_cgroup(FOO); in serial_test_cgroup_attach_override()
42 if (CHECK(foo < 0, "cgroup_join_foo", "cgroup setup failed\n")) in serial_test_cgroup_attach_override()
45 if (CHECK(bpf_prog_attach(drop_prog, foo, BPF_CGROUP_INET_EGRESS, in serial_test_cgroup_attach_override()
[all …]
|
| D | linked_list.c | 1 // SPDX-License-Identifier: GPL-2.0
87 "operation on bpf_list_head expects arg#1 bpf_list_node at offset=48 in struct foo, "
88 "but arg is at offset=0 in struct bar" },
91 { "incorrect_node_off2", "arg#1 offset=0, but expected bpf_list_node at offset=48 in struct foo" },
114 prog = bpf_object__find_program_by_name(skel->obj, prog_name); in test_linked_list_fail_prog()
168 ret = bpf_prog_test_run_opts(bpf_program__fd(skel->progs.map_list_push_pop), &opts); in test_linked_list_success()
172 clear_fields(skel->maps.array_map); in test_linked_list_success()
174 ret = bpf_prog_test_run_opts(bpf_program__fd(skel->progs.inner_map_list_push_pop), &opts); in test_linked_list_success()
178 clear_fields(skel->maps.inner_map); in test_linked_list_success()
180 ret = bpf_prog_test_run_opts(bpf_program__fd(skel->progs.global_list_push_pop), &opts); in test_linked_list_success()
[all …]
|
| /kernel/linux/linux-6.6/Documentation/translations/zh_CN/admin-guide/ |
| D | bootconfig.rst | 1 .. SPDX-License-Identifier: GPL-2.0
3 .. include:: ../disclaimer-zh_CN.rst
5 :Original: Documentation/admin-guide/bootconfig.rst
32 关键字只允许包含字母、数字、连字符（ ``-`` ）和下划线（ ``_`` ）。值可包含
42 --------
46 foo.bar.baz = value1
47 foo.bar.qux.quux = value2
51 foo.bar {
58 foo.bar { baz = value1; qux.quux = value2 }
64 --------------
[all …]
|
| /kernel/linux/linux-5.10/tools/perf/Documentation/ |
| D | callchain-overhead-calculation.txt | 2 --------------------
5 adding all period values of the entry - usually a function (symbol).
23 -----------------------
24 void foo(void) {
28 void bar(void) {
30 foo();
34 bar()
37 -----------------------
39 In this case 'foo' is a child of 'bar', and 'bar' is an immediate
40 child of 'main' so 'foo' also is a child of 'main'. In other words,
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/Documentation/ |
| D | callchain-overhead-calculation.txt | 2 --------------------
5 adding all period values of the entry - usually a function (symbol).
23 -----------------------
24 void foo(void) {
28 void bar(void) {
30 foo();
34 bar()
37 -----------------------
39 In this case 'foo' is a child of 'bar', and 'bar' is an immediate
40 child of 'main' so 'foo' also is a child of 'main'. In other words,
[all …]
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/nouveau/include/nvif/ |
| D | list.h | 32 * @file Classic doubly-link circular list implementation.
36 * We need to keep a list of struct foo in the parent struct bar, i.e. what
39 * struct bar {
41 * struct foo *list_of_foos; -----> struct foo {}, struct foo {}, struct foo{}
45 * We need one list head in bar and a list element in all list_of_foos (both are of
48 * struct bar {
54 * struct foo {
62 * struct bar bar;
64 * INIT_LIST_HEAD(&bar.list_of_foos);
68 * struct foo *foo = malloc(...);
[all …]
|
| /kernel/linux/linux-6.6/tools/testing/selftests/ftrace/test.d/dynevent/ |
| D | eprobes_syntax_errors.tc | 2 # SPDX-License-Identifier: GPL-2.0
4 # requires: dynamic_events events/syscalls/sys_enter_openat "<attached-group>.<attached-event> [<ar…
6 check_error() { # command-with-error-pos-by-^
13 check_error 'e syscalls/sys_enter_openat ^foo' # BAD_ATTACH_ARG
14 check_error 'e:^/bar syscalls/sys_enter_openat' # NO_GROUP_NAME
15 check_error 'e:^12345678901234567890123456789012345678901234567890123456789012345/bar syscalls/sys_…
17 check_error 'e:^foo.1/bar syscalls/sys_enter_openat' # BAD_GROUP_NAME
19 check_error 'e:foo/^12345678901234567890123456789012345678901234567890123456789012345 syscalls/sys_…
20 check_error 'e:foo/^bar.1 syscalls/sys_enter_openat' # BAD_EVENT_NAME
22 check_error 'e:foo/bar syscalls/sys_enter_openat arg=^dfd' # BAD_FETCH_ARG
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/ |
| D | overlay-notes.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 This document describes the implementation of the in-kernel
9 companion document to Documentation/devicetree/dynamic-resolution-notes.rst[1]
12 -----------------
21 Lets take an example where we have a foo board with the following base tree::
23 ---- foo.dts ---------------------------------------------------------------
24 /* FOO platform */
25 /dts-v1/;
27 compatible = "corp,foo";
39 ---- foo.dts ---------------------------------------------------------------
[all …]
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/ |
| D | bootconfig.rst | 1 .. SPDX-License-Identifier: GPL-2.0
15 additional key-value data when booting the kernel in an efficient way.
16 This allows administrators to pass a structured-Key config file.
21 The boot config syntax is a simple structured key-value. Each key consists
22 of dot-connected-words, and key and value are connected by ``=``. The value
23 has to be terminated by semi-colon (``;``) or newline (``\n``).
30 Each key word must contain only alphabets, numbers, dash (``-``) or underscore
32 for delimiters such as semi-colon (``;``), new-line (``\n``), comma (``,``),
35 If you want to use those delimiters in a value, you can use either double-
36 quotes (``"VALUE"``) or single-quotes (``'VALUE'``) to quote it. Note that
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/ |
| D | overlay-notes.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 This document describes the implementation of the in-kernel
9 companion document to Documentation/devicetree/dynamic-resolution-notes.rst[1]
12 -----------------
21 Lets take an example where we have a foo board with the following base tree::
23 ---- foo.dts ---------------------------------------------------------------
24 /* FOO platform */
25 /dts-v1/;
27 compatible = "corp,foo";
39 ---- foo.dts ---------------------------------------------------------------
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | bootconfig.rst | 1 .. SPDX-License-Identifier: GPL-2.0
15 additional key-value data when booting the kernel in an efficient way.
16 This allows administrators to pass a structured-Key config file.
21 The boot config syntax is a simple structured key-value. Each key consists
22 of dot-connected-words, and key and value are connected by ``=``. The value
23 has to be terminated by semi-colon (``;``) or newline (``\n``).
30 Each key word must contain only alphabets, numbers, dash (``-``) or underscore
32 for delimiters such as semi-colon (``;``), new-line (``\n``), comma (``,``),
35 If you want to use those delimiters in a value, you can use either double-
36 quotes (``"VALUE"``) or single-quotes (``'VALUE'``) to quote it. Note that
[all …]
|
| /kernel/linux/linux-6.6/samples/kobject/ |
| D | kset-example.c | 1 // SPDX-License-Identifier: GPL-2.0
5 * Copyright (C) 2004-2007 Greg Kroah-Hartman <greg@kroah.com>
17 * /sys/kernel/kset-example
18 * Then tree kobjects are created and assigned to this kset, "foo", "baz",
19 * and "bar". In those kobjects, attributes of the same name are also
31 int foo; member
33 int bar; member
40 ssize_t (*show)(struct foo_obj *foo, struct foo_attribute *attr, char *buf);
41 ssize_t (*store)(struct foo_obj *foo, struct foo_attribute *attr, const char *buf, size_t count);
57 struct foo_obj *foo; in foo_attr_show() local
[all …]
|
| /kernel/linux/linux-5.10/samples/kobject/ |
| D | kset-example.c | 1 // SPDX-License-Identifier: GPL-2.0
5 * Copyright (C) 2004-2007 Greg Kroah-Hartman <greg@kroah.com>
17 * /sys/kernel/kset-example
18 * Then tree kobjects are created and assigned to this kset, "foo", "baz",
19 * and "bar". In those kobjects, attributes of the same name are also
31 int foo; member
33 int bar; member
40 ssize_t (*show)(struct foo_obj *foo, struct foo_attribute *attr, char *buf);
41 ssize_t (*store)(struct foo_obj *foo, struct foo_attribute *attr, const char *buf, size_t count);
57 struct foo_obj *foo; in foo_attr_show() local
[all …]
|
| /kernel/linux/linux-6.6/Documentation/translations/zh_CN/devicetree/ |
| D | overlay-notes.rst | 1 .. SPDX-License-Identifier: GPL-2.0
2 .. include:: ../disclaimer-zh_CN.rst
4 :Original: Documentation/devicetree/overlay-notes.rst
17 Documentation/devicetree/dynamic-resolution-notes.rst[1]的配套文档。
20 ------------
28 ---- foo.dts ---------------------------------------------------------------
30 /dts-v1/;
32 compatible = "corp,foo";
44 ---- foo.dts ---------------------------------------------------------------
49 ---- bar.dts - 按标签覆盖目标位置 ----------------------------
[all …]
|
| /kernel/linux/linux-6.6/tools/testing/selftests/net/ |
| D | unicast_extensions.sh | 2 # SPDX-License-Identifier: GPL-2.0
7 # Self-tests for IPv4 address extensions: the kernel's ability to accept
48 if [ $1 -eq 0 ]; then
49 printf "TEST: %-60s [ OK ]\n" "${2}"
51 printf "TEST: %-60s [FAIL]\n" "${2}"
60 # foo --- bar
64 # containing linked veth devices foo and bar,
67 ip -n $foo_ns address add $1/$3 dev foo || return 1
68 ip -n $foo_ns link set foo up || return 1
69 ip -n $bar_ns address add $2/$3 dev bar || return 1
[all …]
|
| /kernel/linux/linux-6.6/Documentation/doc-guide/ |
| D | kernel-doc.rst | 1 .. title:: Kernel-doc comments
4 Writing kernel-doc comments
8 comments in the kernel-doc format to describe the functions, types
9 and design of the code. It is easier to keep documentation up-to-date
12 .. note:: The kernel-doc format is deceptively similar to javadoc,
13 gtk-doc or Doxygen, yet distinctively different, for historical
14 reasons. The kernel source contains tens of thousands of kernel-doc
17 .. note:: kernel-doc does not cover Rust code: please see
18 Documentation/rust/general-information.rst instead.
20 The kernel-doc structure is extracted from the comments, and proper
[all …]
|
| /kernel/linux/linux-5.10/Documentation/doc-guide/ |
| D | kernel-doc.rst | 1 Writing kernel-doc comments
5 comments in the kernel-doc format to describe the functions, types
6 and design of the code. It is easier to keep documentation up-to-date
9 .. note:: The kernel-doc format is deceptively similar to javadoc,
10 gtk-doc or Doxygen, yet distinctively different, for historical
11 reasons. The kernel source contains tens of thousands of kernel-doc
14 The kernel-doc structure is extracted from the comments, and proper
16 generated from them. The descriptions are filtered for special kernel-doc
17 highlights and cross-references. See below for details.
19 .. _Sphinx C Domain: http://www.sphinx-doc.org/en/stable/domains.html
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/tests/ |
| D | expr.c | 1 // SPDX-License-Identifier: GPL-2.0
27 /* Union {foo, bar} against {}. */ in test_ids_union()
31 TEST_ASSERT_EQUAL("ids__insert", ids__insert(ids1, strdup("foo")), 0); in test_ids_union()
32 TEST_ASSERT_EQUAL("ids__insert", ids__insert(ids1, strdup("bar")), 0); in test_ids_union()
37 /* Union {foo, bar} against {foo}. */ in test_ids_union()
40 TEST_ASSERT_EQUAL("ids__insert", ids__insert(ids2, strdup("foo")), 0); in test_ids_union()
45 /* Union {foo, bar} against {bar,baz}. */ in test_ids_union()
48 TEST_ASSERT_EQUAL("ids__insert", ids__insert(ids2, strdup("bar")), 0); in test_ids_union()
86 expr__add_id_val(ctx, strdup("FOO"), 1); in test__expr()
87 expr__add_id_val(ctx, strdup("BAR"), 2); in test__expr()
[all …]
|
| /kernel/linux/linux-5.10/tools/perf/tests/ |
| D | expr.c | 1 // SPDX-License-Identifier: GPL-2.0
28 expr__add_id_val(&ctx, strdup("FOO"), 1); in test__expr()
29 expr__add_id_val(&ctx, strdup("BAR"), 2); in test__expr()
32 ret |= test(&ctx, "FOO+BAR", 3); in test__expr()
33 ret |= test(&ctx, "(BAR/2)%2", 1); in test__expr()
34 ret |= test(&ctx, "1 - -4", 5); in test__expr()
35 ret |= test(&ctx, "(FOO-1)*2 + (BAR/2)%2 - -4", 5); in test__expr()
36 ret |= test(&ctx, "1-1 | 1", 1); in test__expr()
37 ret |= test(&ctx, "1-1 & 1", 0); in test__expr()
55 p = "FOO/0"; in test__expr()
[all …]
|
| /kernel/linux/linux-6.6/tools/testing/ktest/examples/bootconfigs/ |
| D | verify-boottrace.sh | 18 content=`cat $file | sed -ne "/^$val/p"`
19 if [ -z "$content" ]; then
30 if ! grep -q "$val" $file ; then
41 content=`cat $file | sed -ne "/^[0 ]*$val/p"`
42 if [ -z "$content" ]; then
61 …all_finish/trigger" 'hist:keys=func:vals=hitcount:lat=common_timestamp.usecs-\$ts0:sort=hitcount:s…
64 compare_file "instances/foo/current_tracer" "function"
65 file_contains "instances/foo/set_ftrace_filter" "^user"
66 compare_file "instances/foo/buffer_size_kb" "512"
67 compare_mask "instances/foo/tracing_cpumask" "1"
[all …]
|
| /kernel/linux/linux-6.6/Documentation/translations/it_IT/doc-guide/ |
| D | kernel-doc.rst | 1 .. include:: ../disclaimer-ita.rst
4 :ref:`Documentation/doc-guide/index.rst <doc_guide>`
6 .. title:: Commenti in kernel-doc
11 Scrivere i commenti in kernel-doc
15 strutturanti secondo il formato kernel-doc. Essi possono descrivere funzioni,
18 .. note:: Il formato kernel-doc può sembrare simile a gtk-doc o Doxygen ma
20 contengono decine di migliaia di commenti kernel-doc. Siete pregati
23 La struttura kernel-doc è estratta a partire dai commenti; da questi viene
30 .. _`dominio Sphinx per il C`: http://www.sphinx-doc.org/en/stable/domains.html
34 kernel-doc. Quando l'intenzione è di utilizzarle nei moduli, anche le funzioni
[all …]
|
| /kernel/linux/linux-5.10/Documentation/translations/it_IT/doc-guide/ |
| D | kernel-doc.rst | 1 .. include:: ../disclaimer-ita.rst
4 :ref:`Documentation/doc-guide/index.rst <doc_guide>`
8 Scrivere i commenti in kernel-doc
12 strutturanti secondo il formato kernel-doc. Essi possono descrivere funzioni,
15 .. note:: Il formato kernel-doc può sembrare simile a gtk-doc o Doxygen ma
17 contengono decine di migliaia di commenti kernel-doc. Siete pregati
20 La struttura kernel-doc è estratta a partire dai commenti; da questi viene
27 .. _`dominio Sphinx per il C`: http://www.sphinx-doc.org/en/stable/domains.html
31 kernel-doc. Quando l'intenzione è di utilizzarle nei moduli, anche le funzioni
33 kernel-doc.
[all …]
|