| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-4.19/arch/s390/kernel/ |
| D | debug.c | 33 #define ALL_AREAS 0 /* copy all debug areas */
34 #define NO_AREAS 1 /* copy no debug areas */
188 * - Debug areas are implemented as a threedimensonal array:
189 * areas[areanumber][pagenumber][pageoffset]
194 debug_entry_t ***areas; in debug_areas_alloc() local
197 areas = kmalloc_array(nr_areas, sizeof(debug_entry_t **), GFP_KERNEL); in debug_areas_alloc()
198 if (!areas) in debug_areas_alloc()
202 areas[i] = kmalloc_array(pages_per_area, in debug_areas_alloc()
205 if (!areas[i]) in debug_areas_alloc()
208 areas[i][j] = kzalloc(PAGE_SIZE, GFP_KERNEL); in debug_areas_alloc()
[all …]
|
| /kernel/linux/linux-4.19/Documentation/media/uapi/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:
49 When two consecutive areas don't overlap (n+1L is equal to nU) the boundary
54 with a hue value included in the overlapping region between two areas (between
55 n+1L and nU excluded) are attributed to both areas and given a weight for each
56 of these areas proportional to their position along the diagonal lines
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | memblock.h | 149 * for_each_physmem_range - iterate through physmem areas not included in type.
162 * __for_each_mem_range - iterate through memblock areas from type_a and not
182 * __for_each_mem_range_rev - reverse iterate through memblock areas from
203 * for_each_mem_range - iterate through memory areas.
213 * for_each_mem_range_rev - reverse iterate through memblock areas from
224 * for_each_reserved_mem_range - iterate over all reserved memblock areas
229 * Walks over reserved areas of memblock. Available as soon as memblock
276 * memblock areas
282 * Walks over free (memory && !reserved) areas of memblock in a specific
296 * free memblock areas from a given point
[all …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-4.19/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
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/gpu/ |
| D | brcm,bcm-v3d.txt | 8 - reg: Physical base addresses and lengths of the register areas
9 - reg-names: Names for the register areas. The "hub", "bridge", and "core0"
10 register areas are always required. The "gca" register area
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/gpu/ |
| D | brcm,bcm-v3d.txt | 8 - reg: Physical base addresses and lengths of the register areas
9 - reg-names: Names for the register areas. The "hub" and "core0"
10 register areas are always required. The "gca" register area
|
| /kernel/linux/linux-4.19/Documentation/s390/ |
| D | s390dbf.txt | 23 debug log for the caller. For each debug log exists a number of debug areas
25 pages in memory. In the debug areas there are stored debug entries (log records)
39 The debug areas themselves are also ordered in form of a ring buffer.
109 nr_areas: number of debug areas
125 nr_areas: Number of debug areas
343 /* register 4 debug areas with one page each and 4 byte data field */
377 /* register 4 debug areas with one page each and data field for */
434 Flushing debug areas
436 Debug areas can be flushed with piping the number of the desired
437 area (0...n) to the debugfs file "flush". When using "-" all debug areas
[all …]
|
| /kernel/linux/linux-4.19/arch/ia64/mm/ |
| D | contig.c | 42 * Allocate and setup per-cpu data areas.
72 * 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
147 * into account reserved areas.
|
| /kernel/linux/linux-5.10/arch/ia64/mm/ |
| D | contig.c | 39 * Allocate and setup per-cpu data areas.
69 * percpu areas which is important for congruent in per_cpu_init()
95 * setup_per_cpu_areas - setup percpu areas
97 * Arch code has already allocated and initialized percpu areas. All
145 * into account reserved areas.
|
| /kernel/linux/linux-4.19/include/linux/ |
| D | memblock.h | 145 * for_each_mem_range - iterate through memblock areas from type_a and not
165 * for_each_mem_range_rev - reverse iterate through memblock areas from
186 * for_each_reserved_mem_region - iterate over all reserved memblock areas
191 * Walks over reserved areas of memblock. Available as soon as memblock
236 * for_each_free_mem_range - iterate through free memblock areas
244 * Walks over free (memory && !reserved) areas of memblock. Available as
252 * for_each_free_mem_range_reverse - rev-iterate through free memblock areas
260 * Walks over free (memory && !reserved) areas of memblock in reverse
|
| /kernel/linux/linux-5.10/mm/ |
| D | Kconfig | 111 # to represent different areas of memory. This variable allows
341 Enable Kernel Samepage Merging: KSM periodically scans those areas
547 int "Maximum count of the CMA areas"
552 CMA allows to create CMA areas for particular purpose, mainly,
563 allocations with __GFP_CMA flag will use cma areas prior to
564 movable areas.
566 It improves the utilization ratio of cma areas.
907 Allow naming anonymous virtual memory areas.
909 This feature allows assigning names to virtual memory areas. Assigned
911 and help identifying individual anonymous memory areas.
[all …]
|
| /kernel/linux/linux-4.19/drivers/soc/renesas/ |
| D | rcar-sysc.c | 248 /* Skip CPUs (handled by SMP code) and areas without control */ in rcar_sysc_pd_setup()
372 syscier |= BIT(info->areas[i].isr_bit); in rcar_sysc_pd_init()
393 const struct rcar_sysc_area *area = &info->areas[i]; in rcar_sysc_pd_init()
425 const struct rcar_sysc_area *area = &info->areas[i]; in rcar_sysc_pd_init()
445 void __init rcar_sysc_nullify(struct rcar_sysc_area *areas, in rcar_sysc_nullify() argument
451 if (areas[i].isr_bit == id) { in rcar_sysc_nullify()
452 areas[i].name = NULL; in rcar_sysc_nullify()
|
| /kernel/linux/linux-4.19/Documentation/cma/ |
| D | debugfs.txt | 2 different CMA areas and to test allocation/release in each of the areas.
|
| /kernel/linux/linux-4.19/include/pcmcia/ |
| D | ss.h | 234 * - pccard_static_ops iomem and ioport areas are assigned statically
235 * - pccard_iodyn_ops iomem areas is assigned statically, ioport
236 * areas dynamically
239 * - pccard_nonstatic_ops iomem and ioport areas are assigned dynamically.
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-4.19/Documentation/ABI/testing/ |
| D | sysfs-devices-platform-docg3 | 7 keylocked. Each docg3 chip (or floor) has 2 protection areas,
22 (0 or 1). Each docg3 chip (or floor) has 2 protection areas,
|
| /kernel/linux/linux-5.10/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,
|
| /kernel/linux/linux-5.10/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()
|