Searched full:accessible (Results 1 – 25 of 218) sorted by relevance
123456789
| /Documentation/gpu/rfc/ |
| D | i915_small_bar.rst | 7 I915_MEMORY_CLASS_DEVICE will be CPU accessible(for example the first 256M),
8 while the remainder is only accessible via the GPU.
15 accessible. Without this flag the kernel will assume that CPU access is not
25 CPU accessible portion, for the particular region. This should only be
42 CPU accessible, at the time of capture, then the kernel is free to skip
47 error capture, when for example something is not currently CPU accessible.
|
| D | i915_small_bar.h | 43 * that is CPU accessible.
47 * accessible.
51 * of it will be CPU accessible.
164 * entire I915_MEMORY_CLASS_DEVICE region will be CPU accessible, and as
|
| /Documentation/virt/kvm/s390/ |
| D | s390-pv-boot.rst | 9 The memory of Protected Virtual Machines (PVMs) is not accessible to
11 access the memory of a PVM, that memory must be made accessible.
12 Memory made accessible to the hypervisor will be encrypted. See
|
| /Documentation/virt/kvm/devices/ |
| D | vm.rst | 42 :Returns: -EFAULT if the given address is not accessible;
75 :Returns: -EFAULT if the given address is not accessible from kernel space;
100 -EFAULT if the given address is not accessible from kernel space;
120 :Returns: -EFAULT if the given address is not accessible from kernel space;
133 :Returns: -EFAULT if the given address is not accessible from kernel space;
176 :Returns: -EFAULT if the given address is not accessible from kernel space;
199 :Returns: -EFAULT if the given address is not accessible from kernel space;
216 :Returns: -EFAULT if the given address is not accessible from kernel space;
227 :Returns: -EFAULT if the given address is not accessible from kernel space
240 :Returns: -EFAULT if the given address is not accessible from kernel space;
[all …]
|
| /Documentation/devicetree/bindings/pci/ |
| D | snps,dw-pcie-ep.yaml | 44 Basic DWC PCIe controller configuration-space accessible over
47 with all spaces. Note iATU/eDMA CSRs are indirectly accessible
86 PCS and PHY CSRs accessible over a dedicated memory mapped
87 region, but mainly these registers are indirectly accessible
|
| D | snps,dw-pcie.yaml | 53 Basic DWC PCIe controller configuration-space accessible over
56 with all spaces. Note iATU/eDMA CSRs are indirectly accessible
95 PCS and PHY CSRs accessible over a dedicated memory mapped
96 region, but mainly these registers are indirectly accessible
|
| /Documentation/filesystems/ |
| D | romfs.rst | 50 structure is very simple. Every accessible structure begins on 16
67 8 | full size | The number of accessible bytes in this fs.
82 bytes accessible from the start of this filesystem. The 4th longword
84 accessible, whichever is smaller). The applied algorithm is the same
116 they are never accessible for other than owner. The owner of every
|
| /Documentation/admin-guide/pm/ |
| D | strategies.rst | 35 be accessible.
56 accessible.
|
| /Documentation/core-api/ |
| D | memory-allocation.rst | 62 will be directly accessible by the kernel and implies that the
66 but it is not required to be directly accessible by the kernel. An
71 must be directly accessible by the kernel.
82 used to ensure that the allocated memory is accessible by hardware
|
| /Documentation/ABI/testing/ |
| D | sysfs-firmware-dmi-tables | 16 presented as binary attributes and are accessible via:
|
| D | sysfs-memory-page-offline | 17 The page must be still accessible, not poisoned. The
|
| /Documentation/networking/ |
| D | netfilter-sysctl.rst | 17 namespaces. This variable is only accessible from init_net.
|
| /Documentation/process/ |
| D | development-process.rst | 9 accessible to those who are not intimately familiar with Linux kernel
|
| /Documentation/devicetree/bindings/net/pcs/ |
| D | fsl,lynx-pcs.yaml | 14 protocol controllers. They are accessible over the Ethernet interface's MDIO
|
| /Documentation/arch/arm/sa1100/ |
| D | lart.rst | 7 other StrongARM-gadgets. Almost all SA signals are directly accessible
|
| /Documentation/devicetree/bindings/fuse/ |
| D | renesas,rcar-otp.yaml | 13 The E-FUSE is a type of non-volatile memory, which is accessible through the
|
| D | renesas,rcar-efuse.yaml | 13 The E-FUSE is a type of non-volatile memory, which is accessible through the
|
| /Documentation/admin-guide/nfs/ |
| D | pnfs-scsi-server.rst | 14 file system must sit on a SCSI LUN that is accessible to the clients in
|
| /Documentation/driver-api/mmc/ |
| D | mmc-dev-parts.rst | 40 not accessible through sysfs in order to avoid accidental or malicious
|
| /Documentation/w1/slaves/ |
| D | w1_ds28e04.rst | 37 The 2 PIOs of the DS28E04-100 are accessible via the "pio" sysfs file.
|
| /Documentation/devicetree/bindings/media/i2c/ |
| D | imi,rdacm2x-gmsl.yaml | 23 accessible by the host SoC by direct addressing.
27 the serializer local I2C bus while the image sensor is not accessible from
|
| /Documentation/driver-api/ |
| D | vfio-pci-device-specific-driver-acceptance.rst | 21 accessible via the vfio-pci base driver. Authors of such drivers
|
| /Documentation/mm/ |
| D | free_page_reporting.rst | 27 accessible to the allocator. Once the report function has been completed
|
| D | page_table_check.rst | 14 accessible from the userspace by getting their page table entries (PTEs PMDs
68 separate from Linux-MM state machine that verifies that the user accessible
|
| /Documentation/devicetree/bindings/mtd/ |
| D | nxp-spifi.txt | 6 mode. In memory mode the Flash is accessible from the CPU as
|
123456789