Home
last modified time | relevance | path

Searched full:regions (Results 1 – 25 of 1114) sorted by relevance

12345678910>>...45

/linux-5.10/arch/powerpc/mm/nohash/
Dkaslr_booke.c24 struct regions { struct
43 struct regions __initdata regions; argument
119 if (regions.reserved_mem < 0) in overlaps_reserved_region()
123 for (subnode = fdt_first_subnode(fdt, regions.reserved_mem); in overlaps_reserved_region()
131 while (len >= (regions.reserved_mem_addr_cells + in overlaps_reserved_region()
132 regions.reserved_mem_size_cells)) { in overlaps_reserved_region()
134 if (regions.reserved_mem_addr_cells == 2) in overlaps_reserved_region()
137 reg += regions.reserved_mem_addr_cells; in overlaps_reserved_region()
138 len -= 4 * regions.reserved_mem_addr_cells; in overlaps_reserved_region()
141 if (regions.reserved_mem_size_cells == 2) in overlaps_reserved_region()
[all …]
/linux-5.10/drivers/mtd/chips/
Djedec_probe.c274 const uint32_t regions[6]; member
306 .regions = {
318 .regions = {
333 .regions = {
348 .regions = {
363 .regions = {
378 .regions = {
394 .regions = {
411 .regions = {
428 .regions = {
[all …]
/linux-5.10/Documentation/admin-guide/device-mapper/
Ddm-clone.rst58 3. A small metadata device - it records which regions are already valid in the
59 destination device, i.e., which regions have already been hydrated, or have
65 Regions section in Design
68 dm-clone divides the source and destination devices in fixed sized regions.
69 Regions are the unit of hydration, i.e., the minimum amount of data copied from
77 Reads and writes from/to hydrated regions are serviced from the destination
93 as a hint to skip hydration of the regions covered by the request, i.e., it
111 A message `hydration_threshold <#regions>` can be used to set the maximum number
112 of regions being copied, the default being 1 region.
116 region size. A message `hydration_batch_size <#regions>` can be used to tune the
[all …]
/linux-5.10/Documentation/networking/devlink/
Ddevlink-region.rst7 ``devlink`` regions enable access to driver defined address regions using
10 Each device can create and register its own supported address regions. The
15 Regions may optionally support triggering snapshots on demand.
22 address regions that are otherwise inaccessible to the user.
24 Regions may also be used to provide an additional way to debug complex error
27 Regions may optionally support capturing a snapshot on demand via the
45 # Show all of the exposed regions with region sizes:
68 As regions are likely very device or driver specific, no generic regions are
70 specific regions a driver supports.
/linux-5.10/drivers/gpu/drm/nouveau/nvkm/nvfw/
Dacr.c89 hdr->regions.no_regions); in flcn_acr_desc_dump()
91 for (i = 0; i < ARRAY_SIZE(hdr->regions.region_props); i++) { in flcn_acr_desc_dump()
94 hdr->regions.region_props[i].start_addr); in flcn_acr_desc_dump()
96 hdr->regions.region_props[i].end_addr); in flcn_acr_desc_dump()
98 hdr->regions.region_props[i].region_id); in flcn_acr_desc_dump()
100 hdr->regions.region_props[i].read_mask); in flcn_acr_desc_dump()
102 hdr->regions.region_props[i].write_mask); in flcn_acr_desc_dump()
104 hdr->regions.region_props[i].client_mask); in flcn_acr_desc_dump()
132 hdr->regions.no_regions); in flcn_acr_desc_v1_dump()
134 for (i = 0; i < ARRAY_SIZE(hdr->regions.region_props); i++) { in flcn_acr_desc_v1_dump()
[all …]
/linux-5.10/mm/
Dmemblock.c35 * Memblock is a method of managing memory regions during the early
40 * regions. There are several types of these collections:
46 * * ``reserved`` - describes the regions that were allocated
54 * which contains an array of memory regions along with
62 * arrays during addition of new regions. This feature should be used
112 .memory.regions = memblock_memory_init_regions,
117 .reserved.regions = memblock_reserved_init_regions,
128 .regions = memblock_physmem_init_regions,
144 for (i = 0, rgn = &memblock_type->regions[0]; \
146 i++, rgn = &memblock_type->regions[i])
[all …]
/linux-5.10/drivers/vfio/platform/
Dvfio_platform_common.c145 vdev->regions = kcalloc(cnt, sizeof(struct vfio_platform_region), in vfio_platform_regions_init()
147 if (!vdev->regions) in vfio_platform_regions_init()
157 vdev->regions[i].addr = res->start; in vfio_platform_regions_init()
158 vdev->regions[i].size = resource_size(res); in vfio_platform_regions_init()
159 vdev->regions[i].flags = 0; in vfio_platform_regions_init()
163 vdev->regions[i].type = VFIO_PLATFORM_REGION_TYPE_MMIO; in vfio_platform_regions_init()
164 vdev->regions[i].flags |= VFIO_REGION_INFO_FLAG_READ; in vfio_platform_regions_init()
166 vdev->regions[i].flags |= in vfio_platform_regions_init()
170 * Only regions addressed with PAGE granularity may be in vfio_platform_regions_init()
173 if (!(vdev->regions[i].addr & ~PAGE_MASK) && in vfio_platform_regions_init()
[all …]
/linux-5.10/drivers/vfio/fsl-mc/
Dvfio_fsl_mc.c100 vdev->regions = kcalloc(count, sizeof(struct vfio_fsl_mc_region), in vfio_fsl_mc_regions_init()
102 if (!vdev->regions) in vfio_fsl_mc_regions_init()
106 struct resource *res = &mc_dev->regions[i]; in vfio_fsl_mc_regions_init()
109 vdev->regions[i].addr = res->start; in vfio_fsl_mc_regions_init()
110 vdev->regions[i].size = resource_size(res); in vfio_fsl_mc_regions_init()
111 vdev->regions[i].type = mc_dev->regions[i].flags & IORESOURCE_BITS; in vfio_fsl_mc_regions_init()
113 * Only regions addressed with PAGE granularity may be in vfio_fsl_mc_regions_init()
116 if (!no_mmap && !(vdev->regions[i].addr & ~PAGE_MASK) && in vfio_fsl_mc_regions_init()
117 !(vdev->regions[i].size & ~PAGE_MASK)) in vfio_fsl_mc_regions_init()
118 vdev->regions[i].flags |= in vfio_fsl_mc_regions_init()
[all …]
/linux-5.10/include/linux/
Dkcsan.h20 * We distinguish between: (a) nestable atomic regions that may contain
21 * other nestable regions; and (b) flat atomic regions that do not keep
28 * atomic regions, but reader critical sections as (b) flat atomic
29 * regions, but have encountered cases where seqlock reader critical
Dmemblock.h59 * struct memblock_type - collection of memory regions of certain type
60 * @cnt: number of regions
62 * @total_size: size of all regions
63 * @regions: array of regions
70 struct memblock_region *regions; member
78 * @memory: usable memory regions
79 * @reserved: reserved memory regions
557 * for_each_mem_region - itereate over memory regions
561 for (region = memblock.memory.regions; \
562 region < (memblock.memory.regions + memblock.memory.cnt); \
[all …]
/linux-5.10/Documentation/devicetree/bindings/fpga/
Dfpga-region.txt18 FPGA Regions represent FPGA's and partial reconfiguration regions of FPGA's in
19 the Device Tree. FPGA Regions provide a way to program FPGAs under device tree
55 * A persona may create more regions.
65 will be used to gate the busses. Traffic to other regions is not affected.
69 * An FPGA image may create a set of reprogrammable regions, each having its
79 * A base image may set up a set of partial reconfiguration regions that may
99 Figure 1: An FPGA set up with a base image that created three regions. Each
124 FPGA Regions represent FPGA's and FPGA PR regions in the device tree. An FPGA
151 These FPGA regions are children of FPGA bridges which are then children of the
160 FPGA Regions do not inherit their ancestor FPGA regions' bridges. This prevents
[all …]
/linux-5.10/Documentation/devicetree/bindings/reserved-memory/
Dreserved-memory.txt1 *** Reserved memory regions ***
6 normal use) memory regions. Such memory regions are usually designed for
21 Each child of the reserved-memory node specifies one or more regions of
41 - Specifies regions of memory that are
79 Regions in the /reserved-memory node may be referenced by other device
88 This example defines 3 contiguous regions are defined for Linux kernel:
/linux-5.10/arch/powerpc/platforms/powernv/
Dopal-fadump.c57 * Preserve memory only if kernel memory regions are registered in opal_fadump_dt_scan()
98 pr_debug("Boot memory regions count: %d\n", fdm->region_cnt); in opal_fadump_update_config()
102 * destination address of boot memory regions. in opal_fadump_update_config()
105 pr_debug("Destination address of boot memory regions: %#016llx\n", in opal_fadump_update_config()
128 pr_debug("Boot memory regions:\n"); in opal_fadump_get_config()
150 * boot memory regions are registered for MPIPL. In such in opal_fadump_get_config()
159 pr_warn("Not all memory regions were saved!!!\n"); in opal_fadump_get_config()
160 pr_warn(" Unsaved memory regions:\n"); in opal_fadump_get_config()
168 …pr_warn("If the unsaved regions only contain pages that are filtered out (eg. free/user pages), th… in opal_fadump_get_config()
169 pr_warn("WARNING: If the unsaved regions contain kernel pages, the vmcore will be corrupted.\n"); in opal_fadump_get_config()
[all …]
/linux-5.10/drivers/net/ipa/
Dipa_mem.c23 /* "Canary" value placed between memory regions to detect overflow */
46 * Set up the shared memory regions in IPA local memory. This involves
47 * zero-filling memory regions, and in the case of header memory, telling
51 * crashes, its regions are re-zeroed in ipa_mem_zero_modem().
66 * the processing context and modem memory regions. in ipa_mem_setup()
75 * regions are contiguous, and initialized together. in ipa_mem_setup()
172 /* Prealloc DMA memory for zeroing regions */ in ipa_mem_config()
189 /* Validate all regions (even undefined ones) */ in ipa_mem_config()
193 /* Skip over undefined regions */ in ipa_mem_config()
208 /* Make sure filter and route table memory regions are valid */ in ipa_mem_config()
[all …]
Dipa_mem.h15 * The IPA has a block of shared memory, divided into regions used for
18 * The regions within the shared block are bounded by an offset (relative to
26 * defined in the config data, allowing for generic handling of regions.
28 * The set of memory regions is defined in configuration data. They are
65 IPA_MEM_COUNT, /* Number of regions (not an index) */
/linux-5.10/drivers/net/dsa/sja1105/
Dsja1105_devlink.c7 /* Since devlink regions have a fixed size and the static config has a variable
85 priv->regions = kcalloc(num_regions, sizeof(struct devlink_region *), in sja1105_setup_devlink_regions()
87 if (!priv->regions) in sja1105_setup_devlink_regions()
97 dsa_devlink_region_destroy(priv->regions[i]); in sja1105_setup_devlink_regions()
101 priv->regions[i] = region; in sja1105_setup_devlink_regions()
113 dsa_devlink_region_destroy(priv->regions[i]); in sja1105_teardown_devlink_regions()
115 kfree(priv->regions); in sja1105_teardown_devlink_regions()
/linux-5.10/Documentation/x86/
Dintel-iommu.rst30 PS2 emulation. The regions of memory used for these devices are marked
32 regions will fail. Hence BIOS uses RMRR to specify these regions along with
33 devices that need to access these regions. OS is expected to setup
34 unity mappings for these regions for these devices to access these regions.
/linux-5.10/arch/mips/include/asm/
Dyamon-dt.h38 * @regions: zero size terminated array of physical memory regions
41 * by YAMON in its environment and the @regions array.
46 const struct yamon_mem_region *regions);
/linux-5.10/drivers/virt/nitro_enclaves/
Dne_misc_dev.h20 * struct ne_mem_region - Entry in the enclave user space memory regions list.
21 * @mem_region_list_entry: Entry in the list of enclave memory regions.
44 * @max_mem_regions: The maximum number of memory regions that can be
46 * @mem_regions_list: Enclave user space memory regions list.
49 * @nr_mem_regions: Number of memory regions associated with the enclave.
/linux-5.10/drivers/soc/qcom/
Dsmem.c41 * the partition and holds properties for the two internal memory regions. The
42 * two regions are cached and non-cached memory respectively. Each region
258 * @num_regions: number of @regions
259 * @regions: list of the memory regions defining the shared memory
274 struct smem_region regions[]; member
406 header = smem->regions[0].virt_base; in qcom_smem_alloc_global()
491 header = smem->regions[0].virt_base; in qcom_smem_get_global()
499 region = &smem->regions[i]; in qcom_smem_get_global()
639 header = __smem->regions[0].virt_base; in qcom_smem_get_free_space()
659 struct smem_region *region = &__smem->regions[i]; in qcom_smem_virt_to_phys()
[all …]
/linux-5.10/drivers/staging/comedi/
Dcomedi_pci.c32 * comedi_pci_enable() - Enable the PCI device and request the regions
37 * and request its regions. Set @dev->ioenabled to %true if successful,
45 * -%EBUSY if regions busy,
72 * comedi_pci_disable() - Release the regions and disable the PCI device
77 * to comedi_pci_enable() was successful, release the PCI device's regions
97 * and have no ioremapped regions other than that pointed to by @dev->mmio may
103 * non-%NULL, and call comedi_pci_disable() to release the PCI device's regions
/linux-5.10/arch/x86/platform/efi/
Dquirks.c235 * However, some boot services regions contain data that is required
237 * freed. This is done by tagging those regions with the
242 * into efi.memmap (splitting existing regions if necessary) and tag
296 * can free regions in efi_free_boot_services().
298 * Use this function to ensure we do not free regions owned by somebody
299 * else. We must only reserve (and then free) regions:
338 * critical regions of memory (like the kernel image) or in efi_reserve_boot_services()
339 * those regions that somebody else has already in efi_reserve_boot_services()
365 * those regions that must not be paired with in efi_reserve_boot_services()
373 * Apart from having VA mappings for EFI boot services code/data regions,
[all …]
/linux-5.10/arch/arm64/kernel/
Defi.c16 * Only regions of type EFI_RUNTIME_SERVICES_CODE need to be
29 "UEFI Runtime regions are not aligned to 64 KB -- buggy firmware?")) in create_mapping_protection()
33 * the mapping attributes of the adjacent regions. in create_mapping_protection()
105 * Calling apply_to_page_range() is only safe on regions that are in efi_set_mapping_permissions()
107 * for regions that have been mapped using efi_create_mapping() above in efi_set_mapping_permissions()
/linux-5.10/drivers/gpu/drm/nouveau/nvkm/subdev/acr/
Dgp102.c198 desc->regions.no_regions = 2; in gp102_acr_load_load()
199 desc->regions.region_props[0].start_addr = acr->wpr_start >> 8; in gp102_acr_load_load()
200 desc->regions.region_props[0].end_addr = acr->wpr_end >> 8; in gp102_acr_load_load()
201 desc->regions.region_props[0].region_id = 1; in gp102_acr_load_load()
202 desc->regions.region_props[0].read_mask = 0xf; in gp102_acr_load_load()
203 desc->regions.region_props[0].write_mask = 0xc; in gp102_acr_load_load()
204 desc->regions.region_props[0].client_mask = 0x2; in gp102_acr_load_load()
205 desc->regions.region_props[0].shadow_mem_start_addr = in gp102_acr_load_load()
/linux-5.10/Documentation/devicetree/bindings/pmem/
Dpmem-region.txt1 Device-tree bindings for persistent memory regions
11 persistent regions separately to the normal memory pool. To aid with that this
13 memory regions exist inside the physical address space.
56 * This node specifies two 4KB regions that are backed by

12345678910>>...45