Home
last modified time | relevance | path

Searched refs:same (Results 1 – 25 of 1768) sorted by relevance

12345678910>>...71

/linux/tools/testing/selftests/arm64/pauth/
A Dpac.c73 int same = 0; in n_same_single_set() local
86 same += 1; in n_same_single_set()
89 return same; in n_same_single_set()
254 int same = 10; in TEST() local
283 if (tmp < same) in TEST()
284 same = tmp; in TEST()
287 ASSERT_EQ(0, same) TH_LOG("%d keys clashed every time", same); in TEST()
299 int same = 10; in TEST() local
320 if (ret < same) in TEST()
321 same = ret; in TEST()
[all …]
/linux/scripts/coccinelle/misc/
A Darray_size_dup.cocci5 /// 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)
172 msg = "WARNING: struct_size is used later (line %s) to compute the same size" % (p2[0].line)
[all …]
/linux/fs/
A Dremap_range.c201 bool same; in vfs_dedupe_file_range_compare() local
205 same = true; in vfs_dedupe_file_range_compare()
237 same = false; in vfs_dedupe_file_range_compare()
248 same = false; in vfs_dedupe_file_range_compare()
257 if (!same) in vfs_dedupe_file_range_compare()
265 *is_same = same; in vfs_dedupe_file_range_compare()
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 …]
A Dioctl.c423 struct file_dedupe_range *same = NULL; in ioctl_file_dedupe_range() local
439 same = memdup_user(argp, size); in ioctl_file_dedupe_range()
440 if (IS_ERR(same)) { in ioctl_file_dedupe_range()
441 ret = PTR_ERR(same); in ioctl_file_dedupe_range()
442 same = NULL; in ioctl_file_dedupe_range()
446 same->dest_count = count; in ioctl_file_dedupe_range()
447 ret = vfs_dedupe_file_range(file, same); in ioctl_file_dedupe_range()
451 ret = copy_to_user(argp, same, size); in ioctl_file_dedupe_range()
456 kfree(same); in ioctl_file_dedupe_range()
/linux/Documentation/ABI/stable/
A Dsysfs-devices-system-cpu9 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.
86 Description: internal kernel map of CPUs within the same die.
90 Description: human-readable list of CPUs within the same die.
95 Description: internal kernel map of CPUs within the same cluster.
99 Description: human-readable list of CPUs within the same cluster.
104 Description: internal kernel map of cpuX's hardware threads within the same
109 Description: human-readable list of cpuX's hardware threads within the same
115 Description: internal kernel map of cpuX's hardware threads within the same
[all …]
/linux/kernel/
A Dlatencytop.c97 int q, same = 1; in account_global_scheduler_latency() local
109 same = 0; in account_global_scheduler_latency()
117 if (same) { in account_global_scheduler_latency()
179 int same = 1; in __account_scheduler_latency() local
186 same = 0; in __account_scheduler_latency()
194 if (same) { in __account_scheduler_latency()
/linux/Documentation/devicetree/bindings/display/
A Dst,stih4xx.txt18 - 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 …]
A Dallwinner,sun4i-a10-display-engine.yaml22 display pipeline, when there are multiple components of the same
23 type at the same depth, the local endpoint ID must be the same as
39 The same rule also applies to DE 2.0 mixer-TCON connections:
/linux/tools/perf/Documentation/
A Dperf-buildid-cache.txt38 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:
A Dintel-bts.txt39 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/
A Dpersist.rst22 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
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
146 If you replace one USB device with another of the same type (same
[all …]
/linux/Documentation/devicetree/bindings/net/
A Dsocionext-netsec.txt11 - phy-mode: See ethernet.txt file in the same directory
12 - phy-handle: See ethernet.txt in the same directory.
26 Optional properties: (See ethernet.txt file in the same directory)
29 - max-speed: See ethernet.txt in the same directory.
30 - max-frame-size: See ethernet.txt in the same directory.
A Dnixge.txt8 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.
A Dftgmac100.txt18 - phy-handle: See ethernet.txt file in the same directory.
19 - phy-mode: See ethernet.txt file in the same directory. If the property is
37 - mdio: See mdio.txt file in the same directory.
/linux/Documentation/core-api/
A Drefcount-vs-atomic.rst35 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
A Dbus-virt-phys-mapping.rst43 external hardware sees the memory the same way.
45 Now, on normal PCs the bus address is exactly the same as the physical
47 because the memory and the devices share the same address space, and that is
57 Now, that looks simple enough. However, when you look at the same thing from
71 where all the addresses actually point to the same thing. It's just seen
81 are the same).
151 conceptually in the same memory space as "real memory" at all, so you cannot
152 just dereference a pointer. (Sadly, on x86 it **is** in the same memory space,
/linux/Documentation/devicetree/bindings/sound/
A Dst,sti-asoc-card.txt20 - 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/powerpc/
A Dvcpudispatch_stats.rst31 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/drivers/pci/
A DKconfig105 require SR-IOV support, while at the same time the PF (Physical
157 to access more than one IO address space at the same time. To make
176 P2P DMA transactions must be between devices behind the same root
203 at compile-time. The choices are the same as those offered for
215 Use the BIOS defaults; don't touch MPS at all. This is the same
231 is the same as booting with 'pci=pcie_bus_safe'.
240 parent. This is the same as booting with 'pci=pcie_bus_perf'.
251 This is the same as booting with 'pci=pcie_bus_peer2peer'.
/linux/Documentation/admin-guide/namespaces/
A Dcompatibility-list.rst35 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/
A Doverlay_bad_add_dup_node.dts6 * &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/admin-guide/hw-vuln/
A Dcore-scheduling.rst9 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/virt/kvm/devices/
A Dvcpu.rst8 KVM_GET_DEVICE_ATTR, and KVM_HAS_DEVICE_ATTR. The interface uses the same struct
39 type must be same for each vcpu. As a PPI, the interrupt number is the same for
97 Note: "Cancelling" a filter by registering the opposite action for the same
100 action for the same range will leave the whole range as disabled.
135 Setting the same PPI for different timers will prevent the VCPUs from running.
230 same on the destination as it was on the source).
/linux/Documentation/power/
A Dswsusp-and-swap-files.rst7 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/mm/
A Dzswap.rst117 Some of the pages in zswap are same-value filled pages (i.e. contents of the
118 page have same value or repetitive pattern). These pages include zero-filled
120 checked if it is a same-value filled page before compressing it. If true, the
121 compressed length of the page is set to zero and the pattern or same-filled
132 When zswap same-filled page identification is disabled at runtime, it will stop
133 checking for the same-value filled pages during store operation. However, the
134 existing pages which are marked as same-value filled pages remain stored
151 of pages stored, same-value filled pages and various counters for the reasons

Completed in 25 milliseconds

12345678910>>...71