Searched refs:Regions (Results 1 – 22 of 22) sorted by relevance
15 Regions may optionally support triggering snapshots on demand.24 Regions may also be used to provide an additional way to debug complex error27 Regions may optionally support capturing a snapshot on demand via the34 Regions may optionally allow directly reading from their contents without a
45 Regions chapter
95 Regions chapter103 .. list-table:: Regions implemented
38 Regions chapter
193 Regions chapter
11 Regions 2-18 have registers for the 16 individual queues which are isolated
18 FPGA Regions represent FPGA's and partial reconfiguration regions of FPGA's in19 the Device Tree. FPGA Regions provide a way to program FPGAs under device tree124 FPGA Regions represent FPGA's and FPGA PR regions in the device tree. An FPGA160 FPGA Regions do not inherit their ancestor FPGA regions' bridges. This prevents168 - fpga-mgr : should contain a phandle to an FPGA Manager. Child FPGA Regions
16 Regions 1...N are extended regions (unused address space) for mapping foreign
65 Regions section in Design69 Regions are the unit of hydration, i.e., the minimum amount of data copied from
34 Operation Regions allow firmware (BIOS) code to access I2C slave devices,
365 CXL Regions
202 PCI Memory/IO Mapped Regions
49 redistributors are laid out contiguously within the region. Regions
198 |///| -> Regions (CPU, HPTE & Metadata) marked like this in the above
1393 struct file_region_info Regions[]; member
184 VFIO-CCW Regions
560 marked for use as PCC Operation Regions must not be used as PCC
174 Adaptive Regions Adjustment
563 Initial Monitoring Target Regions
1000 This option provides a means to manipulate Isolated Memory Regions.
74 Race Conditions and Critical Regions
487 - Regions: debugging feature which allows user space to dump driver-defined
