Home
last modified time | relevance | path

Searched +full:i +full:- +full:tlb +full:- +full:size (Results 1 – 18 of 18) sorted by relevance

/Documentation/devicetree/bindings/riscv/
Dcpus.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR MIT)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: RISC-V bindings for 'cpus' DT nodes
10 - Paul Walmsley <paul.walmsley@sifive.com>
11 - Palmer Dabbelt <palmer@sifive.com>
14 This document uses some terminology common to the RISC-V community
18 mandated by the RISC-V ISA: a PC and some registers. This
28 - items:
29 - enum:
[all …]
/Documentation/core-api/
Dcachetlb.rst2 Cache and TLB Flushing Under Linux
7 This document describes the cache/tlb flushing interfaces called
17 thinking SMP cache/tlb flushing must be so inefficient, this is in
23 First, the TLB flushing interfaces, since they are the simplest. The
24 "TLB" is abstracted under Linux as something the cpu uses to cache
25 virtual-->physical address translations obtained from the software
27 possible for stale translations to exist in this "TLB" cache.
44 the TLB. After running, this interface must make sure that
47 there will be no entries in the TLB for 'mm'.
57 address translations from the TLB. After running, this
[all …]
/Documentation/arm/
Dinterrupts.rst5 2.5.2-rmk5:
7 major architecture-specific subsystems.
10 MMU TLB. Each MMU TLB variant is now handled completely separately -
11 we have TLB v3, TLB v4 (without write buffer), TLB v4 (with write buffer),
12 and finally TLB v4 (with write buffer, with I TLB invalidate entry).
14 allow more flexible TLB handling for the future.
26 SA1100 ------------> Neponset -----------> SA1111
28 -----------> USAR
30 -----------> SMC9196
33 exclusive of each other - if you're processing one interrupt from the
[all …]
/Documentation/devicetree/bindings/iommu/
Dsamsung,sysmmu.txt4 physical memory chunks visible as a contiguous region to DMA-capable peripheral
5 devices like MFC, FIMC, FIMD, GScaler, FIMC-IS and so forth.
10 another capabilities like L2 TLB or block-fetch buffers to minimize translation
13 System MMUs are in many to one relation with peripheral devices, i.e. single
31 - compatible: Should be "samsung,exynos-sysmmu"
32 - reg: A tuple of base address and size of System MMU registers.
33 - #iommu-cells: Should be <0>.
34 - interrupts: An interrupt specifier for interrupt signal of System MMU,
37 - clock-names: Should be "sysmmu" or a pair of "aclk" and "pclk" to gate
42 - clocks: Phandles for respective clocks described by clock-names.
[all …]
/Documentation/virt/kvm/
Dmmu.txt10 - correctness: the guest should not be able to determine that it is running
13 a particular implementation such as tlb size)
14 - security: the guest must not be able to touch host memory not assigned
16 - performance: minimize the performance penalty imposed by the mmu
17 - scaling: need to scale to large memory and large vcpu guests
18 - hardware: support the full range of x86 virtualization hardware
19 - integration: Linux memory management code must be in control of guest memory
22 - dirty tracking: report writes to guest memory to enable live migration
23 and framebuffer-based displays
24 - footprint: keep the amount of pinned kernel memory low (most memory
[all …]
Dapi.txt1 The Definitive KVM (Kernel-based Virtual Machine) API Documentation
5 ----------------------
10 - System ioctls: These query and set global attributes which affect the
14 - VM ioctls: These query and set attributes that affect an entire virtual
21 - vcpu ioctls: These query and set attributes that control the operation
29 - device ioctls: These query and set attributes that control the operation
36 -------------------
73 -------------
77 facility that allows backward-compatible extensions to the API to be
87 ------------------
[all …]
/Documentation/sparc/
Dadi.rst19 2. Set TTE.mcd bit on any TLB entries that correspond to the range of
25 given tag for one ADI block size number of bytes. This step must
28 ADI block size for the platform is provided by the hypervisor to kernel
34 SPARC M7 processor, MMU uses bits 63-60 for version tags and ADI block
35 size is same as cacheline size which is 64 bytes. A task that sets ADI
37 virtual addresses that contain 0xa in bits 63-60.
43 ASI_MCD_PRIMARY or ASI_MCD_ST_BLKINIT_PRIMARY. ADI block size is
45 ADI block size to userspace using auxiliary vector along with other ADI
49 AT_ADI_BLKSZ ADI block size. This is the granularity and
58 - Version tag values of 0x0 and 0xf are reserved. These values match any
[all …]
/Documentation/x86/x86_64/
Dboot-options.rst1 .. SPDX-License-Identifier: GPL-2.0
22 due to the shared banks, i.e. you might get duplicated
39 Do not opt-in to Local MCE delivery. Use legacy method
62 Don't overwrite the bios-set CMCI threshold. This boot option
69 Force-enable recoverable machine check code paths
80 Use IO-APIC. Default
83 Don't use the IO-APIC.
92 See Documentation/x86/i386/IO-APIC.rst
98 Don't check the IO-APIC timer. This can work around
176 numa=fake=<size>[MG]
[all …]
/Documentation/networking/
Dbonding.txt7 Corrections, HA extensions : 2000/10/03-15 :
8 - Willy Tarreau <willy at meta-x.org>
9 - Constantine Gavrilov <const-g at xpert.com>
10 - Chad N. Tindel <ctindel at ieee dot org>
11 - Janice Girouard <girouard at us dot ibm dot com>
12 - Jay Vosburgh <fubar at us dot ibm dot com>
16 - Mitch Williams <mitch.a.williams at intel.com>
29 the original tools from extreme-linux and beowulf sites will not work
114 -----------------------------------------------
130 -------------------------------------
[all …]
/Documentation/driver-api/
Dvfio.rst2 VFIO - "Virtual Function I/O" [1]_
6 to help ensure I/O devices behave within the boundaries they've been
7 allotted. This includes x86 hardware with AMD-Vi and Intel VT-d,
12 safe [2]_, non-privileged, userspace drivers.
16 I/O performance. From a device and host perspective, this simply
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)
36 ---------------------------
38 Devices are the main target of any I/O driver. Devices typically
[all …]
/Documentation/
DDMA-API-HOWTO.txt10 with example pseudo-code. For a concise description of the API, see
11 DMA-API.txt.
23 The virtual memory system (TLB, page tables, etc.) translates virtual
30 I/O devices use a third kind of address: a "bus address". If a device has
39 supports 64-bit addresses for main memory and PCI BARs, it may use an IOMMU
40 so devices only need to use 32-bit DMA addresses.
49 +-------+ +------+ +------+
52 C +-------+ --------> B +------+ ----------> +------+ A
54 +-----+ | | | | bridge | | +--------+
55 | | | | +------+ | | | |
[all …]
/Documentation/ia64/
Daliasing.rst2 Memory Attribute Aliasing on IA-64
14 The attribute is part of the virtual translation, i.e., it is
15 contained in the TLB entry. The ones of most interest to the Linux
19 WB Write-back (cacheable)
21 WC Write-coalescing
25 used for memory-mapped I/O devices. The WC attribute is uncacheable
41 supported attributes for each region. At boot-time, the kernel uses
62 boot-time information is required for kexec.
75 Therefore, kern_memmap contains only full granule-sized regions that
88 page size allows more flexibility because only 16K or 64K has to be
[all …]
Derr_inject.rst50 #corrected, data cache, hier-2, physical addr(assigned by tool code).
55 #corrected, data cache, hier-2, physical addr(assigned by tool code).
60 #recoverable, DTR0, hier-2.
111 #define ERR_DATA_BUFFER_SIZE 3 // Three 8-byte.
132 return -1;
152 u64 mode : 3, /* 0-2 */
153 err_inj : 3, /* 3-5 */
154 err_sev : 2, /* 6-7 */
155 err_struct : 5, /* 8-12 */
156 struct_hier : 3, /* 13-15 */
[all …]
/Documentation/filesystems/
Dproc.txt1 ------------------------------------------------------------------------------
2 T H E /proc F I L E S Y S T E M
3 ------------------------------------------------------------------------------
9 ------------------------------------------------------------------------------
11 Kernel version 2.4.0-test11-pre4
12 ------------------------------------------------------------------------------
16 -----------------
23 1.1 Process-Specific Subdirectories
35 3 Per-Process Parameters
36 3.1 /proc/<pid>/oom_adj & /proc/<pid>/oom_score_adj - Adjust the oom-killer
[all …]
/Documentation/powerpc/
Dultravisor.rst1 .. SPDX-License-Identifier: GPL-2.0
16 (PVR=0x004e1203) or greater will be PEF-capable. A new ISA release
25 +------------------+
29 +------------------+
31 +------------------+
33 +------------------+
35 +------------------+
75 +---+---+---+---------------+
79 +---+---+---+---------------+
81 +---+---+---+---------------+
[all …]
/Documentation/sparc/oradax/
Doracle-dax.rst25 the accompanying document, dax-hv-api.txt, which is a plain text
27 Specification" version 3.0.20+15, dated 2017-09-25.
86 made accessible via mmap(), and are read-only for the application.
109 equal to the number of bytes given in the call. Otherwise -1 is
113 -----------
122 --------
129 --------
138 ---------------------------------------------
140 A write() whose length is a multiple of the CCB size is treated as a
143 pwrite() system call. If -1 is returned then errno is set to indicate
[all …]
/Documentation/admin-guide/
Dkernel-parameters.txt5 force -- enable ACPI if default was off
6 on -- enable ACPI but allow fallback to DT [arm64]
7 off -- disable ACPI if default was on
8 noirq -- do not use ACPI for IRQ routing
9 strict -- Be less tolerant of platforms that are not
11 rsdt -- prefer RSDT over (default) XSDT
12 copy_dsdt -- copy DSDT to memory
56 Documentation/firmware-guide/acpi/debug.rst for more information about
63 Enable AML "Debug" output, i.e., stores to the Debug
92 size limitation.
[all …]
/Documentation/RCU/
DRTFP.txt4 This document describes RCU-related publications, and is followed by
19 with short-lived threads, such as the K42 research operating system.
20 However, Linux has long-lived tasks, so more is needed.
23 serialization, which is an RCU-like mechanism that relies on the presence
27 that these overheads were not so expensive in the mid-80s. Nonetheless,
28 passive serialization appears to be the first deferred-destruction
30 has lapsed, so this approach may be used in non-GPL software, if desired.
34 In 1987, Rashid et al. described lazy TLB-flush [RichardRashid87a].
36 this paper helped inspire the update-side batching used in the later
38 a description of Argus that noted that use of out-of-date values can
[all …]