Searched +full:protect +full:- +full:exec (Results 1 – 12 of 12) sorted by relevance
| /Documentation/devicetree/bindings/arm/omap/ |
| D | mpu.txt | 1 * TI - MPU (Main Processor Unit) subsystem 8 - compatible : Should be "ti,omap3-mpu" for OMAP3 9 Should be "ti,omap4-mpu" for OMAP4 10 Should be "ti,omap5-mpu" for OMAP5 11 - ti,hwmods: "mpu" 14 - sram: Phandle to the ocmcram node 17 - pm-sram: Phandles to ocmcram nodes to be used for power management. 18 First should be type 'protect-exec' for the driver to use to copy 25 - For an OMAP5 SMP system: 28 compatible = "ti,omap5-mpu"; [all …]
|
| /Documentation/gpu/ |
| D | drm-vm-bind-locking.rst | 1 .. SPDX-License-Identifier: (GPL-2.0+ OR MIT) 30 meta-data. Typically one per client (DRM file-private), or one per 33 associated meta-data. The backing storage of a gpu_vma can either be 34 a GEM object or anonymous or page-cache pages mapped also into the CPU 40 is anonymous or page-cache pages as described above. 43 page-table entries point to that backing store. 47 the :doc:`dma-buf doc </driver-api/dma-buf>`. 53 allows deadlock-safe locking of multiple dma_resvs in arbitrary 55 :doc:`dma-buf doc </driver-api/dma-buf>`. 56 * ``exec function``: An exec function is a function that revalidates all [all …]
|
| /Documentation/devicetree/bindings/memory-controllers/ti/ |
| D | emif.txt | 3 EMIF - External Memory Interface - is an SDRAM controller used in 11 - compatible : Should be of the form "ti,emif-<ip-rev>" where <ip-rev> 14 "ti,emif-am3352" 15 "ti,emif-am4372" 16 "ti,emif-dra7xx" 17 "ti,emif-keystone" 19 - phy-type : <u32> indicating the DDR phy type. Following are the 24 - device-handle : phandle to a "lpddr2" node representing the memory part 26 - ti,hwmods : For TI hwmods processing and omap device creation 29 - interrupts : interrupt used by the controller [all …]
|
| /Documentation/arch/x86/ |
| D | shstk.rst | 1 .. SPDX-License-Identifier: GPL-2.0 4 Control-flow Enforcement Technology (CET) Shadow Stack 10 Control-flow Enforcement Technology (CET) covers several related x86 processor 12 can protect both applications and the kernel. 20 control-protection fault. IBT verifies indirect CALL/JMP targets are intended 22 Stack and Indirect Branch Tracking. Today in the 64-bit kernel, only userspace 45 from readelf/llvm-readelf output:: 47 readelf -n <application> | grep -a SHSTK 60 on a per-thread basis. The enablement status is inherited on clone, so if the 90 -EPERM if any of the passed feature are locked. [all …]
|
| /Documentation/devicetree/bindings/sram/ |
| D | sram.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Generic on-chip SRAM 10 - Rob Herring <robh@kernel.org> 19 Following the generic-names recommended practice, node names should 30 - mmio-sram 31 - amlogic,meson-gxbb-sram 32 - arm,juno-sram-ns 33 - atmel,sama5d2-securam [all …]
|
| /Documentation/userspace-api/ |
| D | mseal.rst | 1 .. SPDX-License-Identifier: GPL-2.0 17 such an attacker primitive can break control-flow integrity guarantees 18 since read-only memory that is supposed to be trusted can become writable 29 ----------------------- 34 - The start address must be in an allocated VMA. 35 - The start address must be page aligned. 36 - The end address (**addr** + **len**) must be in an allocated VMA. 37 - no gap (unallocated memory) between start and end address. 44 - **0**: Success. 45 - **-EINVAL**: [all …]
|
| /Documentation/filesystems/ |
| D | affs.rst | 1 .. SPDX-License-Identifier: GPL-2.0 19 in file names are case-insensitive, as they ought to be. 44 protect 107 Amiga -> Linux: 111 - R maps to r for user, group and others. On directories, R implies x. 113 - W maps to w. 115 - E maps to x. 117 - D is ignored. 119 - H, S and P are always retained and ignored under Linux. 121 - A is cleared when a file is written to. [all …]
|
| D | path-lookup.txt | 17 thus in every component during path look-up. Since 2.5.10 onwards, fast-walk 23 make dcache look-up lock-free. 30 are path-walk intensive tend to do path lookups starting from a common dentry 35 (including dcache look-up) completely "store-free" (so, no locks, atomics, or 36 even stores into cachelines of common dentries). This is known as "rcu-walk" 42 A name string specifies a start (root directory, cwd, fd-relative) and a 45 elements are sub-strings, separated by '/'. 49 the path given by the name's starting point (which we know in advance -- eg. 50 current->fs->cwd or current->fs->root) as the first parent of the lookup. Then 67 - find the start point of the walk; [all …]
|
| D | porting.rst | 5 --- 16 --- 20 New methods: ->alloc_inode() and ->destroy_inode(). 22 Remove inode->u.foo_inode_i 27 /* fs-private stuff */ 35 Use FOO_I(inode) instead of &inode->u.foo_inode_i; 37 Add foo_alloc_inode() and foo_destroy_inode() - the former should allocate 38 foo_inode_info and return the address of ->vfs_inode, the latter should free 39 FOO_I(inode) (see in-tree filesystems for examples). 41 Make them ->alloc_inode and ->destroy_inode in your super_operations. [all …]
|
| /Documentation/driver-api/ |
| D | dma-buf.rst | 1 Buffer Sharing and Synchronization (dma-buf) 4 The dma-buf subsystem provides the framework for sharing buffers for 14 interact with the three main primitives offered by dma-buf: 16 - dma-buf, representing a sg_table and exposed to userspace as a file 19 - dma-fence, providing a mechanism to signal when an asynchronous 21 - dma-resv, which manages a set of dma-fences for a particular dma-buf 22 allowing implicit (kernel-ordered) synchronization of work to 27 -------------------------------- 29 For more details on how to design your subsystem's API for dma-buf use, please 30 see Documentation/userspace-api/dma-buf-alloc-exchange.rst. [all …]
|
| /Documentation/admin-guide/sysctl/ |
| D | kernel.rst | 5 .. See scripts/check-sysctl-docs to keep this up to date 13 Documentation/admin-guide/sysctl/index.rst. 15 ------------------------------------------------------------------------------ 39 If BSD-style process accounting is enabled these values control 71 The machine hardware name, the same output as ``uname -m`` 129 Ctrl-Alt-Delete). Writing a value to this file which doesn't 130 correspond to a running process will result in ``-ESRCH``. 132 See also `ctrl-alt-del`_. 236 ctrl-alt-del 239 When the value in this file is 0, ctrl-alt-del is trapped and [all …]
|
| /Documentation/admin-guide/ |
| D | kernel-parameters.txt | 16 force -- enable ACPI if default was off 17 on -- enable ACPI but allow fallback to DT [arm64,riscv64] 18 off -- disable ACPI if default was on 19 noirq -- do not use ACPI for IRQ routing 20 strict -- Be less tolerant of platforms that are not 22 rsdt -- prefer RSDT over (default) XSDT 23 copy_dsdt -- copy DSDT to memory 24 nospcr -- disable console in ACPI SPCR table as 41 If set to vendor, prefer vendor-specific driver 73 Documentation/firmware-guide/acpi/debug.rst for more information about [all …]
|