| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/powerpc/power10/ |
| D | pipeline.json | 5 …"BriefDescription": "Cycles in which the oldest instruction in the pipeline suffered a TLB miss or…
10 …"BriefDescription": "Cycles in which the next-to-complete (NTC) instruction is held at dispatch fo…
35 "BriefDescription": "Cycles in which an instruction reload is pending to satisfy a demand miss."
55 …"BriefDescription": "Cycles in which the oldest instruction in the pipeline was waiting for a load…
60 …"BriefDescription": "Cycles in which the oldest instruction in the pipeline finished at dispatch a…
75 …"BriefDescription": "Cycles in which the next-to-complete (NTC) instruction is held at dispatch be…
80 …"BriefDescription": "Cycles in which the next-to-complete (NTC) instruction is held at dispatch be…
85 …"BriefDescription": "Cycles in which the oldest instruction in the pipeline was waiting for a load…
90 …"BriefDescription": "Cycles in which the oldest instruction in the pipeline was executing in the s…
95 …"BriefDescription": "Cycles in which the oldest instruction in the pipeline was a lwsync waiting t…
[all …]
|
| /kernel/linux/linux-6.6/drivers/staging/greybus/ |
| D | gpio.c | 67 static int gb_gpio_activate_operation(struct gb_gpio_controller *ggc, u8 which) in gb_gpio_activate_operation() argument
77 request.which = which; in gb_gpio_activate_operation()
85 ggc->lines[which].active = true; in gb_gpio_activate_operation()
91 u8 which) in gb_gpio_deactivate_operation() argument
98 request.which = which; in gb_gpio_deactivate_operation()
102 dev_err(dev, "failed to deactivate gpio %u\n", which); in gb_gpio_deactivate_operation()
106 ggc->lines[which].active = false; in gb_gpio_deactivate_operation()
113 u8 which) in gb_gpio_get_direction_operation() argument
121 request.which = which; in gb_gpio_get_direction_operation()
131 which, direction); in gb_gpio_get_direction_operation()
[all …]
|
| D | pwm.c | 43 u8 which) in gb_pwm_activate_operation() argument
49 if (which > pwmc->pwm_max) in gb_pwm_activate_operation()
52 request.which = which; in gb_pwm_activate_operation()
68 u8 which) in gb_pwm_deactivate_operation() argument
74 if (which > pwmc->pwm_max) in gb_pwm_deactivate_operation()
77 request.which = which; in gb_pwm_deactivate_operation()
93 u8 which, u32 duty, u32 period) in gb_pwm_config_operation() argument
99 if (which > pwmc->pwm_max) in gb_pwm_config_operation()
102 request.which = which; in gb_pwm_config_operation()
120 u8 which, u8 polarity) in gb_pwm_set_polarity_operation() argument
[all …]
|
| /kernel/linux/linux-5.10/drivers/staging/greybus/ |
| D | gpio.c | 60 static int gb_gpio_activate_operation(struct gb_gpio_controller *ggc, u8 which) in gb_gpio_activate_operation() argument
70 request.which = which; in gb_gpio_activate_operation()
78 ggc->lines[which].active = true; in gb_gpio_activate_operation()
84 u8 which) in gb_gpio_deactivate_operation() argument
91 request.which = which; in gb_gpio_deactivate_operation()
95 dev_err(dev, "failed to deactivate gpio %u\n", which); in gb_gpio_deactivate_operation()
99 ggc->lines[which].active = false; in gb_gpio_deactivate_operation()
106 u8 which) in gb_gpio_get_direction_operation() argument
114 request.which = which; in gb_gpio_get_direction_operation()
124 which, direction); in gb_gpio_get_direction_operation()
[all …]
|
| D | pwm.c | 42 u8 which) in gb_pwm_activate_operation() argument
48 if (which > pwmc->pwm_max) in gb_pwm_activate_operation()
51 request.which = which; in gb_pwm_activate_operation()
67 u8 which) in gb_pwm_deactivate_operation() argument
73 if (which > pwmc->pwm_max) in gb_pwm_deactivate_operation()
76 request.which = which; in gb_pwm_deactivate_operation()
92 u8 which, u32 duty, u32 period) in gb_pwm_config_operation() argument
98 if (which > pwmc->pwm_max) in gb_pwm_config_operation()
101 request.which = which; in gb_pwm_config_operation()
119 u8 which, u8 polarity) in gb_pwm_set_polarity_operation() argument
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/arm64/arm/cortex-a76/ |
| D | cache.json | 3 "PublicDescription": "This event counts any instruction fetch which misses in the cache.",
11 …re operation or page table walk access which causes data to be read from outside the L1, including…
15 …store operation or page table walk access which looks up in the L1 data cache. In particular, any …
23 …or Level 0 Macro-op cache access. This event counts any instruction fetch which accesses the L1 in…
31 …"PublicDescription": "This event counts any transaction from L1 which looks up in the L2 cache, an…
35 …L2 data cache refill. This event counts any cacheable transaction from L1 which causes data to be …
39 …which return data, regardless of whether they cause an invalidation. Invalidations from the L2 whi…
43 …line write into the L2 cache which does not cause a linefill, including write-backs from L1 to L2 …
47 …"PublicDescription": "This event counts any load or store operation which accesses the data L1 TLB…
52 …"PublicDescription": "This event counts any instruction fetch which accesses the instruction L1 TL…
[all …]
|
| /kernel/linux/linux-6.6/Documentation/process/ |
| D | 4.Coding.rst | 8 code. It is the code which will be examined by other developers and merged
9 (or not) into the mainline tree. So it is the quality of this code which
13 number of ways in which kernel developers can go wrong. Then the focus
14 will shift toward doing things right and the tools which can help in that
28 which does not meet the coding style guidelines. The presence of that code
46 The other trap is to assume that code which is already in the kernel is
56 The coding style document also should not be read as an absolute law which
58 style (a line which becomes far less readable if split to fit within the
81 At a simple level, consider a function which has an argument which is
84 provides. By that time, though, chances are good that the code which
[all …]
|
| D | 1.Intro.rst | 27 :ref:`development_coding` is about the coding process; several pitfalls which
30 which can help to ensure that kernel patches are correct.
56 kernel has evolved into a best-of-breed operating system component which
75 offer this kind of openness, which is a characteristic of the free software
84 evolved its own distinct ways of operating which allow it to function
132 - Code which has been merged into the mainline kernel is available to all
133 Linux users. It will automatically be present on all distributions which
148 Code which is in the mainline, instead, does not require this work as the
151 which has been merged into the mainline has significantly lower
154 - Beyond that, code which is in the kernel will often be improved by other
[all …]
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | 4.Coding.rst | 8 code. It is the code which will be examined by other developers and merged
9 (or not) into the mainline tree. So it is the quality of this code which
13 number of ways in which kernel developers can go wrong. Then the focus
14 will shift toward doing things right and the tools which can help in that
28 which does not meet the coding style guidelines. The presence of that code
46 The other trap is to assume that code which is already in the kernel is
56 The coding style document also should not be read as an absolute law which
58 style (a line which becomes far less readable if split to fit within the
81 At a simple level, consider a function which has an argument which is
84 provides. By that time, though, chances are good that the code which
[all …]
|
| D | 1.Intro.rst | 27 :ref:`development_coding` is about the coding process; several pitfalls which
30 which can help to ensure that kernel patches are correct.
56 kernel has evolved into a best-of-breed operating system component which
75 offer this kind of openness, which is a characteristic of the free software
84 evolved its own distinct ways of operating which allow it to function
132 - Code which has been merged into the mainline kernel is available to all
133 Linux users. It will automatically be present on all distributions which
148 Code which is in the mainline, instead, does not require this work as the
151 which has been merged into the mainline has significantly lower
154 - Beyond that, code which is in the kernel will often be improved by other
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/arm64/arm/cortex-a55/ |
| D | branch.json | 18 … "Predicted conditional branch executed.This event counts when any branch which can be predicted b…
21 … "Predicted conditional branch executed.This event counts when any branch which can be predicted b…
24 …"Indirect branch mis-predicted.This event counts when any indirect branch which can be predicted b…
27 …"Indirect branch mis-predicted.This event counts when any indirect branch which can be predicted b…
30 …ted due to address mis-compare.This event counts when any indirect branch which can be predicted b…
33 …ted due to address mis-compare.This event counts when any indirect branch which can be predicted b…
36 …which can be predicted by the conditional predictor is retired, and has mis-predicted the conditio…
39 …which can be predicted by the conditional predictor is retired, and has mis-predicted the conditio…
42 …ith predicted address executed.This event counts when any indirect branch which can be predicted b…
45 …ith predicted address executed.This event counts when any indirect branch which can be predicted b…
[all …]
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/arm64/arm/cortex-a76-n1/ |
| D | cache.json | 3 …n": "L1 instruction cache refill. This event counts any instruction fetch which misses in the cach…
15 …re operation or page table walk access which causes data to be read from outside the L1, including…
21 …store operation or page table walk access which looks up in the L1 data cache. In particular, any …
33 …or Level 0 Macro-op cache access. This event counts any instruction fetch which accesses the L1 in…
45 …"PublicDescription": "L2 data cache access. This event counts any transaction from L1 which looks …
51 …L2 data cache refill. This event counts any cacheable transaction from L1 which causes data to be …
57 …which return data, regardless of whether they cause an invalidation. Invalidations from the L2 whi…
63 …line write into the L2 cache which does not cause a linefill, including write-backs from L1 to L2 …
69 …: "Level 1 data TLB access. This event counts any load or store operation which accesses the data …
75 … "Level 1 instruction TLB access. This event counts any instruction fetch which accesses the instr…
[all …]
|
| /kernel/linux/linux-5.10/tools/testing/kunit/test_data/ |
| D | test_is_test_passed-no_tests_run.log | 39 Using a channel type which is configured out of UML
41 Using a channel type which is configured out of UML
43 Using a channel type which is configured out of UML
45 Using a channel type which is configured out of UML
47 Using a channel type which is configured out of UML
49 Using a channel type which is configured out of UML
51 Using a channel type which is configured out of UML
53 Using a channel type which is configured out of UML
55 Using a channel type which is configured out of UML
57 Using a channel type which is configured out of UML
[all …]
|
| D | test_output_isolated_correctly.log | 61 Using a channel type which is configured out of UML
63 Using a channel type which is configured out of UML
65 Using a channel type which is configured out of UML
67 Using a channel type which is configured out of UML
69 Using a channel type which is configured out of UML
71 Using a channel type which is configured out of UML
73 Using a channel type which is configured out of UML
75 Using a channel type which is configured out of UML
77 Using a channel type which is configured out of UML
79 Using a channel type which is configured out of UML
[all …]
|
| /kernel/linux/linux-6.6/tools/testing/kunit/test_data/ |
| D | test_is_test_passed-no_tests_run_no_header.log | 39 Using a channel type which is configured out of UML
41 Using a channel type which is configured out of UML
43 Using a channel type which is configured out of UML
45 Using a channel type which is configured out of UML
47 Using a channel type which is configured out of UML
49 Using a channel type which is configured out of UML
51 Using a channel type which is configured out of UML
53 Using a channel type which is configured out of UML
55 Using a channel type which is configured out of UML
57 Using a channel type which is configured out of UML
[all …]
|
| D | test_output_isolated_correctly.log | 61 Using a channel type which is configured out of UML
63 Using a channel type which is configured out of UML
65 Using a channel type which is configured out of UML
67 Using a channel type which is configured out of UML
69 Using a channel type which is configured out of UML
71 Using a channel type which is configured out of UML
73 Using a channel type which is configured out of UML
75 Using a channel type which is configured out of UML
77 Using a channel type which is configured out of UML
79 Using a channel type which is configured out of UML
[all …]
|
| /kernel/linux/linux-6.6/Documentation/dev-tools/ |
| D | ktap.rst | 11 which don't align with the original TAP specification. Thus, a "Kernel TAP"
16 KTAP test results describe a series of tests (which may be nested: i.e., test
17 can have subtests), each of which can contain both diagnostic data -- e.g., log
31 a couple of places (notably the "Subtest" header), which are described where
37 All KTAP-formatted results begin with a "version line" which specifies which
45 Note that, in KTAP, subtests also begin with a version line, which denotes the
46 start of the nested test results. This differs from TAP14, which uses a
62 which case the test plan may be omitted -- it is strongly recommended one is
75 The result can be either "ok", which indicates the test case passed,
76 or "not ok", which indicates that the test case failed.
[all …]
|
| /kernel/linux/linux-6.6/drivers/mtd/chips/ |
| D | Kconfig | 22 This option enables JEDEC-style probing of flash chips which are not
24 CFI-targeted flash drivers for any chips which are identified which
40 configuration options which allow you to do so.
49 This option defines the way in which the CPU attempts to arrange
51 'NO', which is the default when CONFIG_MTD_CFI_ADV_OPTIONS isn't
79 some other configuration options which would allow you to reduce
82 which are supported by the current code will be enabled.
88 If you wish to support CFI devices on a physical bus which is
95 If you wish to support CFI devices on a physical bus which is
102 If you wish to support CFI devices on a physical bus which is
[all …]
|
| /kernel/linux/linux-5.10/drivers/mtd/chips/ |
| D | Kconfig | 22 This option enables JEDEC-style probing of flash chips which are not
24 CFI-targeted flash drivers for any chips which are identified which
40 configuration options which allow you to do so.
49 This option defines the way in which the CPU attempts to arrange
51 'NO', which is the default when CONFIG_MTD_CFI_ADV_OPTIONS isn't
79 some other configuration options which would allow you to reduce
82 which are supported by the current code will be enabled.
88 If you wish to support CFI devices on a physical bus which is
95 If you wish to support CFI devices on a physical bus which is
102 If you wish to support CFI devices on a physical bus which is
[all …]
|
| /kernel/linux/linux-5.10/net/bridge/netfilter/ |
| D | Kconfig | 98 This option adds the among match, which allows matching the MAC source
107 This option adds the ARP match, which allows ARP and RARP header field
115 This option adds the IP match, which allows basic IP header field
124 This option adds the IP6 match, which allows basic IPV6 header field
132 This option adds the limit match, which allows you to control
133 the rate at which a rule can be matched. This match is the
142 This option adds the mark match, which allows matching frames based on
152 This option adds the packet type match, which allows matching on the
162 This option adds the Spanning Tree Protocol match, which
170 This option adds the 802.1Q vlan match, which allows the filtering of
[all …]
|
| /kernel/linux/linux-6.6/net/bridge/netfilter/ |
| D | Kconfig | 96 This option adds the among match, which allows matching the MAC source
105 This option adds the ARP match, which allows ARP and RARP header field
113 This option adds the IP match, which allows basic IP header field
122 This option adds the IP6 match, which allows basic IPV6 header field
130 This option adds the limit match, which allows you to control
131 the rate at which a rule can be matched. This match is the
140 This option adds the mark match, which allows matching frames based on
150 This option adds the packet type match, which allows matching on the
160 This option adds the Spanning Tree Protocol match, which
168 This option adds the 802.1Q vlan match, which allows the filtering of
[all …]
|
| /kernel/linux/linux-5.10/tools/testing/selftests/timers/ |
| D | posix_timers.c | 77 static int check_itimer(int which) in check_itimer() argument
87 if (which == ITIMER_VIRTUAL) in check_itimer()
89 else if (which == ITIMER_PROF) in check_itimer()
91 else if (which == ITIMER_REAL) in check_itimer()
98 if (which == ITIMER_VIRTUAL) in check_itimer()
100 else if (which == ITIMER_PROF) in check_itimer()
102 else if (which == ITIMER_REAL) in check_itimer()
111 err = setitimer(which, &val, NULL); in check_itimer()
117 if (which == ITIMER_VIRTUAL) in check_itimer()
119 else if (which == ITIMER_PROF) in check_itimer()
[all …]
|
| /kernel/linux/linux-5.10/net/netfilter/ipset/ |
| D | Kconfig | 32 This option adds the bitmap:ip set type support, by which one
41 This option adds the bitmap:ip,mac set type support, by which one
50 This option adds the bitmap:port set type support, by which one
59 This option adds the hash:ip set type support, by which one
69 This option adds the hash:ip,mark set type support, by which one
78 This option adds the hash:ip,port set type support, by which one
87 This option adds the hash:ip,port,ip set type support, by which
97 This option adds the hash:ip,port,net set type support, by which
107 This option adds the hash:ip,mac set type support, by which
116 This option adds the hash:mac set type support, by which
[all …]
|
| /kernel/linux/linux-6.6/net/netfilter/ipset/ |
| D | Kconfig | 32 This option adds the bitmap:ip set type support, by which one
41 This option adds the bitmap:ip,mac set type support, by which one
50 This option adds the bitmap:port set type support, by which one
59 This option adds the hash:ip set type support, by which one
69 This option adds the hash:ip,mark set type support, by which one
78 This option adds the hash:ip,port set type support, by which one
87 This option adds the hash:ip,port,ip set type support, by which
97 This option adds the hash:ip,port,net set type support, by which
107 This option adds the hash:ip,mac set type support, by which
116 This option adds the hash:mac set type support, by which
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/arm64/arm/cortex-a73/ |
| D | pipeline.json | 15 "PublicDescription": "Duration for which all slots in the Load-Store Unit are busy",
18 "BriefDescription": "Duration for which all slots in the Load-Store Unit are busy"
21 "PublicDescription": "Duration for which all slots in the load-store issue queue are busy",
24 "BriefDescription": "Duration for which all slots in the load-store issue queue are busy"
27 … "PublicDescription": "Duration for which all slots in the data processing issue queue are busy",
30 … "BriefDescription": "Duration for which all slots in the data processing issue queue are busy"
33 "PublicDescription": "Duration for which all slots in the Data Engine issue queue are busy",
36 "BriefDescription": "Duration for which all slots in the Data Engine issue queue are busy"
|