| /Linux-v5.15/arch/s390/kernel/ |
| D | debug.c | 34 #define ALL_AREAS 0 /* copy all debug areas */
35 #define NO_AREAS 1 /* copy no debug areas */
175 * - Debug areas are implemented as a threedimensonal array:
176 * areas[areanumber][pagenumber][pageoffset]
181 debug_entry_t ***areas; in debug_areas_alloc() local
184 areas = kmalloc_array(nr_areas, sizeof(debug_entry_t **), GFP_KERNEL); in debug_areas_alloc()
185 if (!areas) in debug_areas_alloc()
189 areas[i] = kmalloc_array(pages_per_area, in debug_areas_alloc()
192 if (!areas[i]) in debug_areas_alloc()
195 areas[i][j] = kzalloc(PAGE_SIZE, GFP_KERNEL); in debug_areas_alloc()
[all …]
|
| /Linux-v5.15/Documentation/userspace-api/media/v4l/ |
| D | pixfmt-meta-vsp1-hgt.rst | 25 between 1 and 16 depending on the Hue areas configuration. Finding the
34 how the HGT Hue areas are configured. There are 6 user configurable Hue
35 Areas which can be configured to cover overlapping Hue values:
58 When two consecutive areas don't overlap (n+1L is equal to nU) the boundary
63 with a hue value included in the overlapping region between two areas (between
64 n+1L and nU excluded) are attributed to both areas and given a weight for each
65 of these areas proportional to their position along the diagonal lines
|
| /Linux-v5.15/include/linux/ |
| D | memblock.h | 150 * for_each_physmem_range - iterate through physmem areas not included in type.
163 * __for_each_mem_range - iterate through memblock areas from type_a and not
183 * __for_each_mem_range_rev - reverse iterate through memblock areas from
204 * for_each_mem_range - iterate through memory areas.
214 * for_each_mem_range_rev - reverse iterate through memblock areas from
225 * for_each_reserved_mem_range - iterate over all reserved memblock areas
230 * Walks over reserved areas of memblock. Available as soon as memblock
277 * memblock areas
283 * Walks over free (memory && !reserved) areas of memblock in a specific
297 * free memblock areas from a given point
[all …]
|
| /Linux-v5.15/Documentation/s390/ |
| D | s390dbf.rst | 28 debug log for the caller. For each debug log exists a number of debug areas
30 pages in memory. In the debug areas there are stored debug entries (log records)
44 The debug areas themselves are also ordered in form of a ring buffer.
140 /* register 4 debug areas with one page each and 4 byte data field */
173 /* register 4 debug areas with one page each and data field for */
228 Flushing debug areas
230 Debug areas can be flushed with piping the number of the desired
231 area (0...n) to the debugfs file "flush". When using "-" all debug areas
240 2. Flush all debug areas::
244 Changing the size of debug areas
[all …]
|
| /Linux-v5.15/Documentation/admin-guide/mm/ |
| D | ksm.rst | 19 The KSM daemon ksmd periodically scans those areas of user memory
35 KSM only operates on those areas of address space which an application
64 Like other madvise calls, they are intended for use on mapped areas of
66 includes unmapped gaps (though working on the intervening mapped areas),
70 restricting its use to areas likely to benefit. KSM's scans may use a lot
114 leave mergeable areas registered for next run.
171 how many times all mergeable areas have been scanned
|
| D | cma_debugfs.rst | 6 different CMA areas and to test allocation/release in each of the areas.
|
| /Linux-v5.15/drivers/staging/media/atomisp/pci/isp/kernels/xnr/xnr_3.0/ |
| D | ia_css_xnr3_param.h | 40 * for dark areas, and a scaled diff towards the value for bright areas. */
51 * for dark areas, and a scaled diff towards the value for bright areas. */
|
| D | ia_css_xnr3_types.h | 45 * the three YUV planes: one for dark areas and one for bright areas. All
62 * each of the two chroma planes: one for dark areas and one for bright areas.
|
| /Linux-v5.15/arch/s390/include/asm/ |
| D | debug.h | 20 #define DEBUG_FLUSH_ALL -1 /* parameter to flush all areas */
54 debug_entry_t ***areas; member
408 * Define static areas for early trace data. During boot debug_register_static()
409 * will replace these with dynamically allocated areas to allow custom page and
424 static debug_entry_t **VNAME(var, areas)[EARLY_AREAS] __initdata = { \
440 .areas = VNAME(var, areas), \
451 #define __REGISTER_STATIC_DEBUG_INFO(var, name, pages, areas, view) \ argument
454 debug_register_static(&var, (pages), (areas)); \
466 * @nr_areas: Number of debug areas
476 * Note: Tracing will start with a fixed number of initial pages and areas.
|
| /Linux-v5.15/arch/ia64/mm/ |
| D | contig.c | 37 * Allocate and setup per-cpu data areas.
67 * percpu areas which is important for congruent in per_cpu_init()
93 * setup_per_cpu_areas - setup percpu areas
95 * Arch code has already allocated and initialized percpu areas. All
143 * into account reserved areas.
|
| /Linux-v5.15/mm/damon/ |
| D | vaddr-test.h | 51 * discontiguous regions which cover every mapped areas. However, the three
52 * regions should not include the two biggest unmapped areas in the original
53 * mapping, because the two biggest areas are normally the areas between 1)
55 * Because these two unmapped areas are very huge but obviously never accessed,
60 * unmapped areas. After that, based on the information, it constructs the
68 * and end with 305. The process also has three unmapped areas, 25-200,
70 * unmapped areas, and thus it should be converted to three regions of 10-25,
|
| D | vaddr.c | 213 * with the noise by simply identifying the unmapped areas as a region that
215 * unmapped areas inside will make the adaptive mechanism quite complex. That
216 * said, too huge unmapped areas inside the monitoring target should be removed
221 * between the three regions are the two biggest unmapped areas in the given
223 * end of the mappings and the two biggest unmapped areas of the address space.
233 * gaps are exceptionally huge areas in usual address space, excluding these
|
| /Linux-v5.15/include/pcmcia/ |
| D | ss.h | 231 * - pccard_static_ops iomem and ioport areas are assigned statically
232 * - pccard_iodyn_ops iomem areas is assigned statically, ioport
233 * areas dynamically
236 * - pccard_nonstatic_ops iomem and ioport areas are assigned dynamically.
|
| /Linux-v5.15/Documentation/ABI/testing/ |
| D | sysfs-devices-platform-docg3 | 7 keylocked. Each docg3 chip (or floor) has 2 protection areas,
24 (0 or 1). Each docg3 chip (or floor) has 2 protection areas,
|
| /Linux-v5.15/arch/sh/boards/mach-sdk7786/ |
| D | fpga.c | 17 * The FPGA can be mapped in any of the generally available areas,
30 * Iterate over all of the areas where the FPGA could be mapped. in sdk7786_fpga_probe()
|
| /Linux-v5.15/Documentation/security/ |
| D | self-protection.rst | 35 areas of the kernel that can be used to redirect execution. This ranges
37 APIs hard to use incorrectly, minimizing the areas of writable kernel
50 Any areas of the kernel with executable memory must not be writable.
73 Vast areas of kernel memory contain function pointers that are looked
178 other memory areas.
252 initializations. If the base address of these areas is not the same
|
| /Linux-v5.15/drivers/soc/renesas/ |
| D | r8a7796-sysc.c | 46 .areas = r8a7796_areas,
62 .areas = r8a7796_areas,
|
| D | rcar-sysc.h | 45 const struct rcar_sysc_area *areas; member
79 extern void rcar_sysc_nullify(struct rcar_sysc_area *areas,
|
| D | rcar-sysc.c | 250 /* Skip CPUs (handled by SMP code) and areas without control */ in rcar_sysc_pd_setup()
397 const struct rcar_sysc_area *area = &info->areas[i]; in rcar_sysc_pd_init()
448 void __init rcar_sysc_nullify(struct rcar_sysc_area *areas, in rcar_sysc_nullify() argument
454 if (areas[i].isr_bit == id) { in rcar_sysc_nullify()
455 areas[i].name = NULL; in rcar_sysc_nullify()
|
| /Linux-v5.15/drivers/s390/net/ |
| D | ctcm_dbug.c | 46 /* register the areas */ in ctcm_register_dbf_views()
49 ctcm_dbf[x].areas, in ctcm_register_dbf_views()
|
| /Linux-v5.15/arch/x86/kernel/cpu/sgx/ |
| D | sgx.h | 46 * The firmware can define multiple chunks of EPC to the different areas of the
47 * physical memory e.g. for memory areas of the each node. This structure is
|
| /Linux-v5.15/Documentation/userspace-api/accelerators/ |
| D | ocxl.rst | 66 work with, the size of its MMIO areas, ...
73 OpenCAPI defines two MMIO areas for each AFU:
158 MMIO areas, the AFU version, and the PASID for the current context.
|
| /Linux-v5.15/mm/ |
| D | percpu.c | 11 * The percpu allocator handles both static and dynamic areas. Percpu
12 * areas are allocated in chunks which are divided into units. There is
177 /* chunks which need their map areas extended, protected by pcpu_lock */
411 * pcpu_next_fit_region - finds fit areas for a given allocation request
476 * Metadata free area iterators. These perform aggregation of free areas
797 /* iterate over free areas and update the contig hints */ in pcpu_block_refresh_hint()
1100 * skip over blocks and chunks that have valid free areas.
1155 * free areas, smaller allocations will eventually fill those holes.
1881 /* clear the areas and return address relative to base address */ in pcpu_alloc()
1996 * areas can be scarce. Destroy all free chunks except for one. in pcpu_balance_free()
[all …]
|
| /Linux-v5.15/Documentation/devicetree/bindings/net/ |
| D | cortina,gemini-ethernet.txt | 11 memory areas, in total three register sets.
28 - reg: must contain two register areas: the DMA/TOE memory and
|
| /Linux-v5.15/Documentation/vm/damon/ |
| D | design.rst | 50 cases. That said, too huge unmapped areas inside the monitoring target should
55 gaps between the three regions are the two biggest unmapped areas in the given
56 address space. The two biggest unmapped areas would be the gap between the
|
