Searched +full:use +full:- +full:guard +full:- +full:pages (Results 1 – 13 of 13) sorted by relevance
| /Documentation/mm/ |
| D | vmalloced-kernel-stacks.rst | 1 .. SPDX-License-Identifier: GPL-2.0 12 -------- 19 ------------ 23 it difficult to isolate and root-cause. 25 Virtually mapped kernel stacks with guard pages cause kernel stack 30 support for virtually mapped stacks with guard pages. This feature 40 -------------------- 45 - vmalloc space must be large enough to hold many kernel stacks. This 46 may rule out many 32-bit architectures. 47 - Stacks in vmalloc space need to work reliably. For example, if [all …]
|
| /Documentation/arch/arm64/ |
| D | memory.rst | 12 with the 4KB page configuration, allowing 39-bit (512GB) or 48-bit 14 64KB pages, only 2 levels of translation tables, allowing 42-bit (4TB) 23 contains only user (non-global) mappings. The swapper_pg_dir address is 27 AArch64 Linux memory layout with 4KB pages + 4 levels (48-bit):: 29 Start End Size Use 30 ----------------------------------------------------------------------- 37 fffffbfffe000000 fffffbfffe7fffff 8MB [guard region] 39 fffffbffff800000 fffffbffffffffff 8MB [guard region] 41 fffffe0000000000 ffffffffffffffff 2TB [guard region] 44 AArch64 Linux memory layout with 64KB pages + 3 levels (52-bit with HW support):: [all …]
|
| /Documentation/dev-tools/ |
| D | kfence.rst | 1 .. SPDX-License-Identifier: GPL-2.0 4 Kernel Electric-Fence (KFENCE) 7 Kernel Electric-Fence (KFENCE) is a low-overhead sampling-based memory safety 8 error detector. KFENCE detects heap out-of-bounds access, use-after-free, and 9 invalid-free errors. 15 non-production test workloads. One way to quickly achieve a large enough total 19 ----- 26 ``kfence.sample_interval`` to non-zero value), configure the kernel with:: 46 causes CPU wake-ups when the system is completely idle. This may be undesirable 47 on power-constrained systems. The boot parameter ``kfence.deferrable=1`` [all …]
|
| /Documentation/devicetree/bindings/reserved-memory/ |
| D | qcom,rmtfs-mem.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/reserved-memory/qcom,rmtfs-mem.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 15 - Bjorn Andersson <bjorn.andersson@linaro.org> 18 - $ref: reserved-memory.yaml 22 const: qcom,rmtfs-mem 24 qcom,client-id: 27 identifier of the client to use this region for buffers 29 qcom,use-guard-pages: [all …]
|
| /Documentation/arch/x86/ |
| D | sgx.rst | 1 .. SPDX-License-Identifier: GPL-2.0 4 Software Guard eXtensions (SGX) 10 Software Guard eXtensions (SGX) hardware enables for user space applications 13 * Privileged (ring-0) ENCLS functions orchestrate the construction of the 15 * Unprivileged (ring-3) ENCLU functions allow an application to enter and 37 SGX utilizes an *Enclave Page Cache (EPC)* to store pages that are associated 38 with an enclave. It is contained in a BIOS-reserved region of physical memory. 39 Unlike pages used for regular memory, pages can only be accessed from outside of 49 ------------------ 56 Regular EPC pages contain the code and data of an enclave. [all …]
|
| /Documentation/admin-guide/mm/ |
| D | pagemap.rst | 12 physical frame each virtual page is mapped to. It contains one 64-bit 16 * Bits 0-54 page frame number (PFN) if present 17 * Bits 0-4 swap type if swapped 18 * Bits 5-54 swap offset if swapped 19 * Bit 55 pte is soft-dirty (see 20 Documentation/admin-guide/mm/soft-dirty.rst) 22 * Bit 57 pte is uffd-wp write-protected (since 5.13) (see 23 Documentation/admin-guide/mm/userfaultfd.rst) 24 * Bit 58 pte is a guard region (since 6.15) (see madvise (2) man page) 25 * Bits 59-60 zero [all …]
|
| /Documentation/arch/arm/ |
| D | memory.rst | 11 free for platforms to use, and which are used by generic code. 18 certain regions of VM space for use for new facilities; therefore 22 Start End Use 24 ffff8000 ffffffff copy_user_page / clear_user_page use. 31 Platforms must not use this address range. 39 in proc-xscale.S to flush the whole data 51 ffc00000 ffc7ffff Guard region 53 ff800000 ffbfffff Permanent, fixed read-only mapping of the 59 VMALLOC_START VMALLOC_END-1 vmalloc() / ioremap() space. 68 PAGE_OFFSET high_memory-1 Kernel direct-mapped RAM region. [all …]
|
| /Documentation/virt/hyperv/ |
| D | coco.rst | 1 .. SPDX-License-Identifier: GPL-2.0 5 Hyper-V can create and run Linux guests that are Confidential Computing 9 CoCo VMs on Hyper-V share the generic CoCo VM threat model and security 10 objectives described in Documentation/security/snp-tdx-threat-model.rst. Note 11 that Hyper-V specific code in Linux refers to CoCo VMs as "isolated VMs" or 14 A Linux CoCo VM on Hyper-V requires the cooperation and interaction of the 19 * The hardware runs a version of Windows/Hyper-V with support for CoCo VMs 25 * AMD processor with SEV-SNP. Hyper-V does not run guest VMs with AMD SME, 26 SEV, or SEV-ES encryption, and such encryption is not sufficient for a CoCo 27 VM on Hyper-V. [all …]
|
| /Documentation/driver-api/ |
| D | vfio.rst | 2 VFIO - "Virtual Function I/O" [1]_ 7 allotted. This includes x86 hardware with AMD-Vi and Intel VT-d, 12 safe [2]_, non-privileged, userspace drivers. 14 Why do we want that? Virtual machines often make use of direct device 18 significantly reduced latency, higher bandwidth, and direct use of 19 bare-metal device drivers [3]_. 22 field, also benefit from low-overhead, direct device access from 23 userspace. Examples include network adapters (often non-TCP/IP based) 26 driver, be maintained out of tree, or make use of the UIO framework, 36 --------------------------- [all …]
|
| /Documentation/admin-guide/media/ |
| D | vivid.rst | 1 .. SPDX-License-Identifier: GPL-2.0 13 Each input can be a webcam, TV capture device, S-Video capture device or an HDMI 14 capture device. Each output can be an S-Video output device or an HDMI output 18 allows you to use this driver as a test input for application development, since 23 - Support for read()/write(), MMAP, USERPTR and DMABUF streaming I/O. 24 - A large list of test patterns and variations thereof 25 - Working brightness, contrast, saturation and hue controls 26 - Support for the alpha color component 27 - Full colorspace support, including limited/full RGB range 28 - All possible control types are present [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 35 2: use 2nd APIC table, if available 36 1,0: use 1st APIC table [all …]
|
| /Documentation/virt/kvm/ |
| D | api.rst | 1 .. SPDX-License-Identifier: GPL-2.0 4 The Definitive KVM (Kernel-based Virtual Machine) API Documentation 13 - System ioctls: These query and set global attributes which affect the 17 - VM ioctls: These query and set attributes that affect an entire virtual 24 - vcpu ioctls: These query and set attributes that control the operation 32 - device ioctls: These query and set attributes that control the operation 80 facility that allows backward-compatible extensions to the API to be 86 set of ioctls is available for application use. 104 the ioctl returns -ENOTTY. 122 ----------------------- [all …]
|
| /Documentation/filesystems/xfs/ |
| D | xfs-online-fsck-design.rst | 1 .. SPDX-License-Identifier: GPL-2.0 8 Heading 3 uses "----" 25 - To help kernel distributors understand exactly what the XFS online fsck 28 - To help people reading the code to familiarize themselves with the relevant 31 - To help developers maintaining the system by capturing the reasons 59 - Provide a hierarchy of names through which application programs can associate 62 - Virtualize physical storage media across those names, and 64 - Retrieve the named data blobs at any time. 66 - Examine resource usage. 79 cross-references different types of metadata records with each other to look [all …]
|