Home
last modified time | relevance | path

Searched full:areas (Results 1 – 25 of 588) sorted by relevance

12345678910>>...24

/Linux-v5.10/arch/s390/kernel/
Ddebug.c33 #define ALL_AREAS 0 /* copy all debug areas */
34 #define NO_AREAS 1 /* copy no debug areas */
172 * - Debug areas are implemented as a threedimensonal array:
173 * areas[areanumber][pagenumber][pageoffset]
178 debug_entry_t ***areas; in debug_areas_alloc() local
181 areas = kmalloc_array(nr_areas, sizeof(debug_entry_t **), GFP_KERNEL); in debug_areas_alloc()
182 if (!areas) in debug_areas_alloc()
186 areas[i] = kmalloc_array(pages_per_area, in debug_areas_alloc()
189 if (!areas[i]) in debug_areas_alloc()
192 areas[i][j] = kzalloc(PAGE_SIZE, GFP_KERNEL); in debug_areas_alloc()
[all …]
/Linux-v5.10/Documentation/userspace-api/media/v4l/
Dpixfmt-meta-vsp1-hgt.rst25 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.10/include/linux/
Dmemblock.h149 * 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 …]
/Linux-v5.10/Documentation/s390/
Ds390dbf.rst28 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.10/Documentation/admin-guide/mm/
Dksm.rst19 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
Dcma_debugfs.rst6 different CMA areas and to test allocation/release in each of the areas.
/Linux-v5.10/drivers/staging/media/atomisp/pci/isp/kernels/xnr/xnr_3.0/
Dia_css_xnr3_param.h40 * 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. */
Dia_css_xnr3_types.h45 * 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.10/Documentation/devicetree/bindings/gpu/
Dbrcm,bcm-v3d.txt8 - 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
/Linux-v5.10/arch/ia64/mm/
Dcontig.c39 * 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.
/Linux-v5.10/include/pcmcia/
Dss.h231 * - 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.10/Documentation/ABI/testing/
Dsysfs-devices-platform-docg37 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.10/arch/sh/boards/mach-sdk7786/
Dfpga.c17 * 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.10/drivers/soc/renesas/
Dr8a7796-sysc.c46 .areas = r8a7796_areas,
62 .areas = r8a7796_areas,
Drcar-sysc.h45 const struct rcar_sysc_area *areas; member
79 extern void rcar_sysc_nullify(struct rcar_sysc_area *areas,
Drcar-sysc.c255 /* Skip CPUs (handled by SMP code) and areas without control */ in rcar_sysc_pd_setup()
402 const struct rcar_sysc_area *area = &info->areas[i]; in rcar_sysc_pd_init()
449 void __init rcar_sysc_nullify(struct rcar_sysc_area *areas, in rcar_sysc_nullify() argument
455 if (areas[i].isr_bit == id) { in rcar_sysc_nullify()
456 areas[i].name = NULL; in rcar_sysc_nullify()
/Linux-v5.10/Documentation/security/
Dself-protection.rst35 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.10/drivers/s390/net/
Dctcm_dbug.c46 /* register the areas */ in ctcm_register_dbf_views()
49 ctcm_dbf[x].areas, in ctcm_register_dbf_views()
/Linux-v5.10/Documentation/userspace-api/accelerators/
Docxl.rst66 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.10/mm/
Dpercpu.c11 * The percpu allocator handles both static and dynamic areas. Percpu
12 * areas are allocated in chunks which are divided into units. There is
171 /* chunks which need their map areas extended, protected by pcpu_lock */
386 * pcpu_next_fit_region - finds fit areas for a given allocation request
451 * Metadata free area iterators. These perform aggregation of free areas
749 /* iterate over free areas and update the contig hints */ in pcpu_block_refresh_hint()
1052 * skip over blocks and chunks that have valid free areas.
1110 * free areas, smaller allocations will eventually fill those holes.
1837 /* clear the areas and return address relative to base address */ in pcpu_alloc()
1954 * areas can be scarce. Destroy all free chunks except for one. in __pcpu_balance_workfn()
[all …]
/Linux-v5.10/Documentation/devicetree/bindings/net/
Dcortina,gemini-ethernet.txt11 memory areas, in total three register sets.
28 - reg: must contain two register areas: the DMA/TOE memory and
/Linux-v5.10/arch/x86/kernel/
Dsetup_percpu.c195 * percpu areas are aligned to PMD. This, in the future, in setup_per_cpu_areas()
220 /* alrighty, percpu areas up and running */ in setup_per_cpu_areas()
230 * initial arrays to the per cpu data areas. These in setup_per_cpu_areas()
/Linux-v5.10/drivers/mtd/devices/
Ddocg3.h14 * Flash memory areas :
249 * Each floor of docg3 has 2 protection areas: DPS0 and DPS1. These areas span
/Linux-v5.10/arch/mips/include/asm/sn/sn0/
Dkldir.h14 * provides pointers to most other IP27 memory areas. This allows us to
15 * resize and/or relocate memory areas at a later time without breaking all
17 * permanently dedicated to areas listed below. Some memory areas (marked
/Linux-v5.10/Documentation/arm/
Dmemory.rst86 Please note that mappings which collide with the above areas may result
92 to TASK_SIZE address range. If they wish to access these areas, they

12345678910>>...24