Home
last modified time | relevance | path

Searched refs:regions (Results 1 – 25 of 129) sorted by relevance

123456

/f-stack/dpdk/drivers/vdpa/mlx5/
H A Dmlx5_vdpa_mem.c90 qsort(mem->regions, mem->nregions, sizeof(mem->regions[0]), in mlx5_vdpa_vhost_mem_regions_prepare()
94 (mem->regions[0].guest_phys_addr); in mlx5_vdpa_vhost_mem_regions_prepare()
99 mem->regions[i].host_user_addr, in mlx5_vdpa_vhost_mem_regions_prepare()
100 mem->regions[i].guest_phys_addr, mem->regions[i].size); in mlx5_vdpa_vhost_mem_regions_prepare()
103 size = mem->regions[i].guest_phys_addr - in mlx5_vdpa_vhost_mem_regions_prepare()
104 (mem->regions[i - 1].guest_phys_addr + in mlx5_vdpa_vhost_mem_regions_prepare()
105 mem->regions[i - 1].size); in mlx5_vdpa_vhost_mem_regions_prepare()
109 size = mem->regions[i].size; in mlx5_vdpa_vhost_mem_regions_prepare()
204 reg = &mem->regions[i]; in mlx5_vdpa_mem_register()
241 mem->regions[i - 1].size); in mlx5_vdpa_mem_register()
[all …]
/f-stack/freebsd/contrib/device-tree/Bindings/pci/
H A Dcdns-pcie-ep.yaml16 cdns,max-outbound-regions:
17 description: maximum number of outbound regions
24 - cdns,max-outbound-regions
H A Dcdns-pcie-host.yaml17 cdns,max-outbound-regions:
18 description: maximum number of outbound regions
H A Drockchip-pcie-ep.txt34 - rockchip,max-outbound-regions: Maximum number of outbound regions
44 rockchip,max-outbound-regions = <16>;
H A Dti,j721e-pci-ep.yaml60 - cdns,max-outbound-regions
87 cdns,max-outbound-regions = <16>;
H A Dxgene-pci.txt14 - ranges: ranges for the outbound memory, I/O regions.
15 - dma-ranges: ranges for the inbound memory regions.
/f-stack/freebsd/contrib/device-tree/Bindings/pmem/
H A 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
/f-stack/freebsd/contrib/device-tree/Bindings/mfd/
H A Dqcom,spmi-pmic.txt7 locations/definitions within these regions, with some of these regions
13 16-bit SPMI slave address space into 256 smaller fixed-size regions, 256 bytes
14 each. A function can consume one or more of these fixed-size register regions.
/f-stack/freebsd/contrib/device-tree/Bindings/reserved-memory/
H A 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
85 This example defines 3 contiguous regions are defined for Linux kernel:
H A Dxen,shared-memory.txt3 Expose one or more memory regions as reserved-memory to the guest
8 For each of these pre-shared memory regions, a range is exposed under
/f-stack/freebsd/contrib/device-tree/Bindings/soc/ti/
H A Dk3-ringacc.yaml35 - description: real time registers regions
36 - description: fifos registers regions
37 - description: proxy gcfg registers regions
38 - description: proxy target registers regions
H A Dkeystone-navigator-qmss.txt14 The QMSS driver manages the PDSP setups, linking RAM regions,
35 Register regions should be specified in the following
91 - descriptor-regions : child node describing the memory regions for keystone
107 Register regions should be specified in the following
216 descriptor-regions {
H A Dkeystone-navigator-dma.txt43 register regions. Register regions should be specified in the following
52 - reg-names: Names for the register regions.
/f-stack/freebsd/contrib/device-tree/Bindings/display/msm/
H A Dmdp5.txt14 - reg-names: The names of register regions. The following regions are required:
41 - reg-names: The names of register regions. The following regions are required:
H A Dedp.txt7 - reg-names: The names of register regions. The following regions are required:
H A Dhdmi.txt42 - reg-names: The names of register regions. The following regions are required:
45 For HDMI PHY on msm8996, these additional register regions are required:
/f-stack/freebsd/contrib/device-tree/Bindings/remoteproc/
H A Dmtk,scp.txt10 regions, SRAM and CFG.
12 regions. These should be named "sram" & "cfg".
H A Dwkup_m3_rproc.txt22 memory regions, UMEM and DMEM. The parent node should
26 regions. These should be named "umem" & "dmem".
/f-stack/dpdk/drivers/net/memif/
H A Drte_eth_memif.c107 if (proc_private->regions[msg_param->idx] != NULL) { in memif_mp_send_region()
179 proc_private->regions[reply_param->idx] = r; in memif_mp_request_regions()
211 void *p = proc_private->regions[0]->addr; in memif_get_ring()
228 (uint8_t *)proc_private->regions[mq->region]->addr); in memif_get_ring_offset()
237 r = proc_private->regions[mq->region]; in memif_get_ring_from_queue()
712 (uint8_t *)proc_private->regions[d0->region]->addr; in memif_tx_one_zc()
854 r = proc_private->regions[i]; in memif_free_regions()
870 proc_private->regions[i] = NULL; in memif_free_regions()
1045 proc_private->regions[0]->pkt_buffer_offset + in memif_init_rings()
1066 proc_private->regions[0]->pkt_buffer_offset + in memif_init_rings()
[all …]
/f-stack/freebsd/contrib/device-tree/Bindings/misc/
H A Daspeed-p2a-ctrl.txt8 has read access to all the regions of memory, however the host only has read
21 - reg: A hint for the memory regions associated with the P2A controller
/f-stack/freebsd/contrib/device-tree/Bindings/fpga/
H A Dfpga-region.txt18 FPGA Regions represent FPGA's and partial reconfiguration regions of FPGA's in
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
161 shutting down bridges that are upstream from the other active regions while one
163 hardware bridges remain enabled. The PR regions' bridges will be FPGA bridges
[all …]
/f-stack/freebsd/contrib/device-tree/Bindings/display/
H A Dzte,vou.txt22 - reg: Physical base address and length of DPC register regions, one for each
24 - reg-names: The names of register regions. The following regions are required:
/f-stack/freebsd/kern/
H A Dsubr_physmem.c277 insert_region(struct region *regions, size_t rcnt, vm_paddr_t addr, in insert_region() argument
283 ep = regions + rcnt; in insert_region()
284 for (i = 0, rp = regions; i < rcnt; ++i, ++rp) { in insert_region()
/f-stack/dpdk/lib/librte_vhost/
H A Drte_vhost.h136 struct rte_vhost_mem_region regions[]; member
317 reg = &mem->regions[i]; in rte_vhost_gpa_to_vva()
353 r = &mem->regions[i]; in rte_vhost_va_from_guest_pa()
/f-stack/dpdk/doc/guides/howto/
H A Dvirtio_user_for_container_networking.rst49 all virtual memory regions to backend. So only those virtual memory regions
106 If you have more regions (especially when 2MB hugepages are used), the option,

123456