Searched full:accessible (Results 1 – 25 of 161) sorted by relevance
1234567
| /Documentation/virt/kvm/devices/ |
| D | vm.txt | 31 Returns: -EFAULT if the given address is not accessible
61 Returns: -EFAULT if the given address is not accessible from kernel space
85 -EFAULT if the given address is not accessible from kernel space
100 Returns: -EFAULT if the given address is not accessible from kernel space.
111 Returns: -EFAULT if the given address is not accessible from kernel space.
149 Returns: -EFAULT if the given address is not accessible from kernel space.
170 Returns: -EFAULT if the given address is not accessible from kernel space.
184 Returns: -EFAULT if the given address is not accessible from kernel space
193 Returns: -EFAULT if the given address is not accessible from kernel space
203 Returns: -EFAULT if the given address is not accessible from kernel space
[all …]
|
| /Documentation/core-api/ |
| D | memory-allocation.rst | 61 will be directly accessible by the kernel and implies that the
65 but it is not required to be directly accessible by the kernel. An
70 must be directly accessible by the kernel.
81 used to ensure that the allocated memory is accessible by hardware
|
| /Documentation/networking/ |
| D | netfilter-sysctl.txt | 10 namespaces. This variable is only accessible from init_net.
|
| /Documentation/filesystems/ |
| D | romfs.txt | 46 structure is very simple. Every accessible structure begins on 16
63 8 | full size | The number of accessible bytes in this fs.
78 bytes accessible from the start of this filesystem. The 4th longword
80 accessible, whichever is smaller). The applied algorithm is the same
112 they are never accessible for other than owner. The owner of every
|
| /Documentation/dev-tools/ |
| D | kasan.rst | 145 Those 8 bytes can be accessible, partially accessible, freed or be a redzone.
147 of the corresponding memory region are accessible; number N (1 <= N <= 7) means
148 that the first N bytes are accessible, and other (8 - N) bytes are not;
154 the accessed address is partially accessible.
|
| /Documentation/admin-guide/pm/ |
| D | strategies.rst | 35 be accessible.
56 accessible.
|
| /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/process/ |
| D | development-process.rst | 24 accessible to those who are not intimately familiar with Linux kernel
|
| /Documentation/arm/sa1100/ |
| D | lart.rst | 7 other StrongARM-gadgets. Almost all SA signals are directly accessible
|
| /Documentation/filesystems/nfs/ |
| D | pnfs-scsi-server.txt | 13 file system must sit on a SCSI LUN that is accessible to the clients in
|
| D | pnfs-block-server.txt | 11 file system must sit on shared storage (typically iSCSI) that is accessible
|
| /Documentation/devicetree/bindings/iommu/ |
| D | rockchip,iommu.txt | 17 - clocks : A list of clocks required for the IOMMU to be accessible by
|
| /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/arm/ |
| D | coresight-cpu-debug.txt | 39 domain are accessible.
|
| D | pmu.yaml | 75 (SDER) is accessible. This will cause the driver to do
|
| /Documentation/devicetree/bindings/mtd/ |
| D | nxp-spifi.txt | 6 mode. In memory mode the Flash is accessible from the CPU as
|
| D | gpmi-nand.txt | 48 turned on may not be accessible by the BootROM
|
| /Documentation/devicetree/bindings/remoteproc/ |
| D | wkup_m3_rproc.txt | 14 (l4_wkup) through which it is accessible to the MPU.
|
| /Documentation/virt/kvm/arm/ |
| D | hyp-abi.txt | 16 SVC/EL1. These stubs are accessible by using a 'hvc #0' instruction,
|
| /Documentation/media/uapi/v4l/ |
| D | dev-osd.rst | 23 The OSD function is accessible through the same character special file
47 accessible as a framebuffer device (``/dev/fbN``). Given a V4L2 device,
|
| /Documentation/powerpc/ |
| D | cxlflash.rst | 70 | User Accessible |
74 | Trusted Process accessible |
77 | Trusted Process accessible |
246 When a LUN is accessible from more than one port, this ioctl will
318 context (still resident/accessible in the parent process) following the
|
| /Documentation/devicetree/bindings/power/ |
| D | renesas,sysc-rmobile.txt | 18 - The first block refers to the normally accessible registers,
|
| /Documentation/ide/ |
| D | ide-tape.rst | 25 include/linux/mtio.h, is accessible through the character device.
|
1234567