| /linux/scripts/coccinelle/misc/ |
| H A D | array_size_dup.cocci | 5 /// 1. An opencoded expression is used before array_size() to compute the same size
6 /// 2. An opencoded expression is used after array_size() to compute the same size
43 msg = "WARNING: array_size is used later (line %s) to compute the same size" % (p2[0].line)
51 msg = "WARNING: array_size is used later (line %s) to compute the same size" % (p2[0].line)
72 msg = "WARNING: array_size is already used (line %s) to compute the same size" % (p1[0].line)
80 msg = "WARNING: array_size is already used (line %s) to compute the same size" % (p1[0].line)
108 msg = "WARNING: array3_size is used later (line %s) to compute the same size" % (p2[0].line)
116 msg = "WARNING: array3_size is used later (line %s) to compute the same size" % (p2[0].line)
138 msg = "WARNING: array3_size is already used (line %s) to compute the same size" % (p1[0].line)
146 msg = "WARNING: array3_size is already used (line %s) to compute the same size" % (p1[0].line)
[all …]
|
| /linux/fs/ |
| H A D | remap_range.c | 196 bool same = true; in vfs_dedupe_file_range_compare() local
231 same = false; in vfs_dedupe_file_range_compare()
244 same = false; in vfs_dedupe_file_range_compare()
253 if (!same) in vfs_dedupe_file_range_compare()
261 *is_same = same; in vfs_dedupe_file_range_compare()
492 int vfs_dedupe_file_range(struct file *file, struct file_dedupe_range *same) in vfs_dedupe_file_range() argument
500 u16 count = same->dest_count; in vfs_dedupe_file_range()
506 if (same->reserved1 || same->reserved2) in vfs_dedupe_file_range()
509 off = same->src_offset; in vfs_dedupe_file_range()
510 len = same->src_length; in vfs_dedupe_file_range()
[all …]
|
| /linux/Documentation/ABI/stable/ |
| H A D | sysfs-devices-system-cpu | 9 all per-CPU defaults at the same time.
64 Description: internal kernel map of CPUs within the same core.
69 Description: human-readable list of CPUs within the same core.
75 Description: internal kernel map of the CPUs sharing the same physical_package_id.
80 Description: human-readable list of CPUs sharing the same physical_package_id.
86 Description: internal kernel map of CPUs within the same die.
94 Description: human-readable list of CPUs within the same die.
99 Description: internal kernel map of CPUs within the same cluster.
103 Description: human-readable list of CPUs within the same cluster.
108 Description: internal kernel map of cpuX's hardware threads within the same
[all …]
|
| /linux/kernel/ |
| H A D | latencytop.c | 21 * if the "same" latency cause is hit twice, this will be tracked as one entry
122 int q, same = 1; in account_global_scheduler_latency() local
134 same = 0; in account_global_scheduler_latency()
142 if (same) { in account_global_scheduler_latency()
204 int same = 1; in __account_scheduler_latency() local
211 same = 0; in __account_scheduler_latency()
219 if (same) { in __account_scheduler_latency()
|
| /linux/Documentation/devicetree/bindings/display/ |
| H A D | st,stih4xx.txt | 18 - clock-names: names of the clocks listed in clocks property in the same
36 - clock-names: names of the clocks listed in clocks property in the same
40 - reset-names: names of the resets listed in resets property in the same
50 the same order.
53 - reset-names: names of the resets listed in resets property in the same
62 the same order.
65 the same order
68 - clock-names: names of the clocks listed in clocks property in the same
78 the same order.
82 - clock-names: names of the clocks listed in clocks property in the same
[all …]
|
| /linux/tools/perf/Documentation/ |
| H A D | perf-buildid-cache.txt | 38 same directory and are also copied. All 3 files are created with read
40 kcore in the cache (with the same build-id) that has the same modules at
41 the same addresses. Use the -v option to see if a copy of kcore is
45 Remove a cached binary which has same build-id of specified file
62 exactly same build-id, that is replaced by new one. It can be used
79 it follows the same syntax as the DEBUGINFOD_URLS variable, like:
|
| H A D | intel-bts.txt | 39 The snapshot option is the same as Intel PT (refer Intel PT documentation).
45 The mmap size option is the same as Intel PT (refer Intel PT documentation).
53 the same as Intel PT (refer Intel PT documentation) except that neither
76 This can be further controlled by new option --itrace exactly the same as
|
| /linux/Documentation/driver-api/usb/ |
| H A D | persist.rst | 22 has no way to know what has actually happened. Perhaps the same
35 system woke up, who cares? It'll still work the same when you type on
39 devices. The effect is exactly the same as if the device really had
47 interrupts a power session will have the same effect. For example,
83 same thing that happens whenever a USB device is reset.) If the
85 same descriptors as before, including the Vendor and Product IDs, then
86 the kernel continues to use the same device structure. In effect, the
90 The same thing happens if the host controller is in the expected state
125 have the same persistent volume associated with the device. As such
142 to make sure the USB device hasn't been changed; that is, the same
[all …]
|
| /linux/Documentation/core-api/ |
| H A D | refcount-vs-atomic.rst | 35 program order (po) relation (on the same CPU). It guarantees that
42 stores (all po-earlier instructions) on the same CPU are completed
43 before any po-later instruction is executed on the same CPU.
44 It also guarantees that all po-earlier stores on the same CPU
50 stores (all po-earlier instructions) on the same CPU are completed
52 stores on the same CPU and all propagated stores from other CPUs
58 stores (all po-later instructions) on the same CPU are
60 po-later stores on the same CPU must propagate to all other CPUs
|
| /linux/Documentation/driver-api/mmc/ |
| H A D | mmc-test.rst | 169 | 10 | Weird sized block reads | same for read |
176 | 12 | Badly aligned read | same for read |
178 | 13 | Badly aligned multi-block write| same for multi-write |
180 | 14 | Badly aligned multi-block read | same for multi-read |
187 | 16 | Proper xfer_size at read | same for read |
190 | 17 | Proper xfer_size at write | same for 2 blocks |
193 | 18 | Proper xfer_size at read | same for read |
198 | 20 | Highmem read | same for read |
200 | 21 | Multi-block highmem write | same for multi-write |
202 | 22 | Multi-block highmem read | same for mult-read |
[all …]
|
| /linux/Documentation/devicetree/bindings/sound/ |
| H A D | st,sti-asoc-card.txt | 20 - clock-names: name of the clocks listed in clocks property in the same order
22 - reg: CPU DAI IP Base address and size entries, listed in same
26 the same order.
28 - interrupts: CPU_DAI interrupt line, listed in the same order than the
31 - dma: CPU_DAI DMA controller phandle and DMA request line, listed in the same
39 - clocks: CPU_DAI IP clock source, listed in the same order than the
|
| /linux/Documentation/devicetree/bindings/net/ |
| H A D | nixge.txt | 8 information of registers in the same order as described by reg-names.
14 - phy-mode: See ethernet.txt file in the same directory.
20 - fixed-link : Assume a fixed link. See fixed-link.txt in the same directory.
22 - phy-handle: See ethernet.txt file in the same directory.
|
| H A D | lpc-eth.txt | 9 - phy-mode: See ethernet.txt file in the same directory. If the property is
15 phy.txt in the same directory
|
| /linux/tools/testing/selftests/bpf/progs/ |
| H A D | cgrp_kfunc_success.c | 24 bool same = pid == cur_pid; in is_test_kfunc_task() local
26 if (same) in is_test_kfunc_task()
29 return same; in is_test_kfunc_task()
|
| /linux/Documentation/filesystems/nfs/ |
| H A D | client-identifier.rst | 57 server to distinguish successive boot epochs of the same client.
95 If distinct clients present the same "co_ownerid" string and use
96 the same principal (for example, AUTH_SYS and UID 0), a server is
97 unable to tell that the clients are not the same. Each distinct
102 If distinct clients present the same "co_ownerid" string and use
104 to operate normally but reject subsequent clients with the same
128 the client's UTS node name (the same node name, incidentally, that
140 client instances with the same host name.
191 use the same lease for operations covered by all "sec=" settings.
206 migration by presenting the same "client_owner4" to all servers it
|
| /linux/Documentation/bpf/ |
| H A D | bpf_prog_run.rst | 23 to be defined in the UAPI header, aliased to the same value.
77 via the same trace points as for regular XDP programs.
85 will be transmitted *out* of that same interface. Do note, though, that
87 ``XDP_TX`` is actually turned into the same action as an ``XDP_REDIRECT`` to
88 that same interface (i.e., it will only work if the driver has support for the
92 in batches. The batch size defaults to 64 packets (which is same as the
102 pages of the same size as the batch size. Each memory page will be initialised
|
| /linux/Documentation/arch/powerpc/ |
| H A D | vcpudispatch_stats.rst | 31 2. number of times this vcpu was dispatched on the same processor as last
34 as last time, but within the same chip
68 statistics were enabled. 4126 of those dispatches were on the same
70 the same chip, while 30 dispatches were on a different chip compared to
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-iio-dac | 17 This attribute has the same meaning as out_currentY_raw. It is
20 The same scale and offset as in out_currentY_raw applies.
48 This attribute has the same meaning as out_currentY_raw. It is
51 The same scale and offset as in out_currentY_raw applies.
|
| H A D | debugfs-scmi-raw | 9 Any subsequently received response can be read from this same
24 Any subsequently received response can be read from this same
27 from this same entry too if it arrived within the configured
77 Any subsequently received response can be read from this same
101 Any subsequently received response can be read from this same
105 from this same entry too if it arrived within the configured
|
| /linux/Documentation/admin-guide/namespaces/ |
| H A D | compatibility-list.rst | 35 words, user 10 in one user namespace shouldn't have the same
39 The same is true for the IPC namespaces being shared - two users
40 from different user namespaces should not access the same IPC objects
|
| /linux/drivers/of/unittest-data/ |
| H A D | overlay_bad_add_dup_node.dtso | 6 * &electric_1/motor-1 and &spin_ctrl_1 are the same node:
10 * result in an attempt to add the same node twice.
|
| /linux/Documentation/arch/x86/ |
| H A D | sva.rst | 11 same virtual addresses avoiding the need for software to translate virtual
18 (PRI) allow devices to function much the same way as the CPU handling
98 with the same PASID. The platform IOMMU uses the PASID in the transaction to
104 thread can interact with a device. Threads that belong to the same
105 process share the same page tables, thus the same MSR value.
114 device but finds no PASID for this process. Subsequent binds of the same, or
115 other devices will share the same PASID.
129 longer has the same address space that it had when the device was opened.
131 On clone(2) the new task shares the same address space, so will be
161 * Multiple processes can separately mmap() the same portal, in
[all …]
|
| /linux/Documentation/power/ |
| H A D | swsusp-and-swap-files.rst | 7 The Linux kernel handles swap files almost in the same way as it handles swap
45 by the same application that determines the swap file's header offset using the
56 Now, swsusp will use the swap file in the same way in which it would use a swap
61 the location of its header need not be the same as before. Thus every time
|
| /linux/Documentation/admin-guide/hw-vuln/ |
| H A D | core-scheduling.rst | 9 workloads may benefit from running on the same core as they don't need the same
17 Threads of the same core. MDS and L1TF are examples of such attacks. The only
36 on the same core. The core scheduler uses this information to make sure that
37 tasks that are not in the same group never run simultaneously on a core, while
83 same core-sched group.
96 mentioned in `Usage`_, tasks with the same cookie value are assumed to trust
101 trusted (same cookie) at any point in time. Kernel threads are assumed trusted.
108 highest priority task with the same cookie is selected if there is one runnable
109 in their individual run queues. If a task with same cookie is not available,
152 assigning them a tag that is the same cookie value.
|
| /linux/Documentation/filesystems/ |
| H A D | directory-locking.rst | 81 from the same NFS4 server and doing lookups in one of them has reached
86 For a lot of reasons we want to have the same directory present in dcache
121 on other filesystems must follow the same locking rules. Moreover, "a
142 * put ->i_rwsem of all directories on a filesystem at the same rank,
143 lower than ->i_rwsem of any non-directory on the same filesystem.
145 on the same filesystem.
152 2. ->i_rwsem of directories on that NFS filesystem, same rank for all
156 5. ->i_rwsem of directories on the local filesystem, same rank for all
168 contended locks in the minimal deadlock will be of the same rank,
169 i.e. they all will be ->i_rwsem of directories on the same filesystem.
[all …]
|