Searched +full:mmu +full:- +full:type (Results 1 – 22 of 22) sorted by relevance
| /Documentation/xtensa/ |
| D | booting.rst | 7 tag value constants. First entry in the list must have type BP_TAG_FIRST, last
8 entry must have type BP_TAG_LAST. The address of the first list entry is
9 passed to the kernel in the register a2. The address type depends on MMU type:
11 - For configurations without MMU, with region protection or with MPU the
13 - For configurations with region translarion MMU or with MMUv3 and CONFIG_MMU=n
16 - For configurations with MMUv2 the address must be a virtual address in the
18 - For configurations with MMUv3 and CONFIG_MMU=y the address may be either a
|
| /Documentation/virt/kvm/ |
| D | locking.txt | 5 ---------------------
9 - kvm->lock is taken outside vcpu->mutex
11 - kvm->lock is taken outside kvm->slots_lock and kvm->irq_lock
13 - kvm->slots_lock is taken outside kvm->irq_lock, though acquiring
16 On x86, vcpu->mutex is taken outside kvm->arch.hyperv.hv_lock.
22 ------------
27 the mmu-lock on x86. Currently, the page fault can be fast in one of the
34 2. Write-Protection: The SPTE is present and the fault is
35 caused by write-protect. That means we just need to change the W bit of the
40 - SPTE_HOST_WRITEABLE means the gfn is writable on host.
[all …]
|
| D | mmu.txt | 1 The x86 kvm shadow mmu
4 The mmu (in arch/x86/kvm, files mmu.[ch] and paging_tmpl.h) is responsible
5 for presenting a standard x86 mmu to the guest, while translating guest
8 The mmu code attempts to satisfy the following requirements:
10 - correctness: the guest should not be able to determine that it is running
11 on an emulated mmu except for timing (we attempt to comply
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
[all …]
|
| D | hypercalls.txt | 4 KVM Hypercalls have a three-byte sequence of either the vmcall or the vmmcall
14 R2-R7 are used for parameters 1-6. In addition, R1 is used for hypercall
21 refer to Documentation/virt/kvm/s390-diag.txt.
24 It uses R3-R10 and hypercall number in R11. R4-R11 are used as output registers.
27 KVM hypercalls uses 4 byte opcode, that are patched with 'hypercall-instructions'
29 For more information refer to Documentation/virt/kvm/ppc-pv.txt
33 number in $2 (v0). Up to four arguments may be placed in $4-$7 (a0-a3) and
45 ------------------------
52 ------------------------
55 Purpose: Support MMU operations such as writing to PTE,
[all …]
|
| D | api.txt | 1 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/devicetree/bindings/riscv/ |
| D | cpus.yaml | 1 # 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/arm/ |
| D | interrupts.rst | 5 2.5.2-rmk5:
7 major architecture-specific subsystems.
10 MMU TLB. Each MMU TLB variant is now handled completely separately -
21 machine type that we currently have.
26 SA1100 ------------> Neponset -----------> SA1111
28 -----------> USAR
30 -----------> SMC9196
33 exclusive of each other - if you're processing one interrupt from the
36 IDE PIO-based interrupt on the SA1111 excludes all other SA1111 and
37 SMC9196 interrupts until it has finished transferring its multi-sector
[all …]
|
| D | booting.rst | 9 The following documentation is relevant to 2.4.18-rmk6 and beyond.
21 3. Detect the machine type.
28 ---------------------------
44 -----------------------------
60 Documentation/admin-guide/kernel-parameters.rst.
63 3. Detect the machine type
64 --------------------------
69 MANDATORY except for DT-only platforms
71 The boot loader should detect the machine type its running on by some
75 value to the kernel. (see linux/arch/arm/tools/mach-types). This
[all …]
|
| /Documentation/driver-api/ |
| D | device_link.rst | 1 .. |struct dev_pm_domain| replace:: :c:type:`struct dev_pm_domain <dev_pm_domain>`
2 .. |struct generic_pm_domain| replace:: :c:type:`struct generic_pm_domain <generic_pm_domain>`
61 device ``->probe`` callback or a boot-time PCI quirk.
65 ``->probe`` callback while the supplier hasn't started to probe yet: Had the
69 non-presence. [Note that it is valid to create a link from the consumer's
70 ``->probe`` callback while the supplier is still probing, but the consumer must
76 is added in the ``->probe`` callback of the supplier or consumer driver, it is
77 typically deleted in its ``->remove`` callback for symmetry. That way, if the
91 link is added from the consumer's ``->probe`` callback: ``DL_FLAG_RPM_ACTIVE``
97 Similarly, when the device link is added from supplier's ``->probe`` callback,
[all …]
|
| /Documentation/devicetree/bindings/misc/ |
| D | fsl,qoriq-mc.txt | 3 The Freescale Management Complex (fsl-mc) is a hardware resource
5 network-oriented packet processing applications. After the fsl-mc
12 For an overview of the DPAA2 architecture and fsl-mc bus see:
16 same hardware "isolation context" and a 10-bit value called an ICID
21 between ICIDs and IOMMUs, so an iommu-map property is used to define
28 For arm-smmu binding, see:
33 - compatible
34 Value type: <string>
35 Definition: Must be "fsl,qoriq-mc". A Freescale Management Complex
40 - reg
[all …]
|
| /Documentation/powerpc/ |
| D | cxl.rst | 28 +----------+ +---------+
34 +----------+ +---------+
36 | +------+ | PSL |
37 | | CAPP |<------>| |
38 +---+------+ PCIE +---------+
65 - POWER8 and PSL Version 8 are compliant to the CAIA Version 1.0.
66 - POWER9 and PSL Version 9 are compliant to the CAIA Version 2.0.
70 * Interaction with the nest MMU on the P9 chip.
85 When using dedicated mode only one MMU context is supported. In
123 The WED is a 64-bit parameter passed to the AFU when a context is
[all …]
|
| D | bootwrapper.rst | 16 used firmware type on general purpose PowerPC systems from Apple, IBM and
17 others. U-Boot is typically found on embedded PowerPC hardware, but there
28 U-Boot (for versions that don't understand the device
31 are all embedded inside the U-Boot uImage file format
37 bd_info structure used in the old U-Boot interfaces,
39 U-Boot platform has a different platform init file
70 kernel with this image type and it depends entirely on
78 and that the MMU is either off or has RAM mapped to
88 simpleImage.virtex405-* targets will add the
89 virtex405-head.S initialization code (This also means
[all …]
|
| /Documentation/sparc/ |
| D | adi.rst | 20 addresses ADI is being enabled on. MMU checks the version tag only
33 bits of the virtual address being presented to the MMU. For example on
34 SPARC M7 processor, MMU uses bits 63-60 for version tags and ADI block
37 virtual addresses that contain 0xa in bits 63-60.
58 - Version tag values of 0x0 and 0xf are reserved. These values match any
61 - Version tags are set on virtual addresses from userspace even though
66 - When a task frees a memory page it had set version tags on, the page
67 goes back to free page pool. When this page is re-allocated to a task,
73 - ADI tag mismatches are not detected for non-faulting loads.
75 - Kernel does not set any tags for user pages and it is entirely a
[all …]
|
| /Documentation/translations/zh_CN/arm/ |
| D | Booting | 11 ---------------------------------------------------------------------
24 ---------------------------------------------------------------------
32 以下文档适用于 2.4.18-rmk6 及以上版本。
42 3、检测机器的类型（machine type）。
48 -------------------
60 -----------------------------
71 Documentation/admin-guide/kernel-parameters.rst。
75 --------------------------
83 (详见 linux/arch/arm/tools/mach-types )。
86 ------------------
[all …]
|
| /Documentation/gpu/ |
| D | drm-mm.rst | 6 frame buffers, textures, vertices and other graphics-related data. Given
13 manager to be developed and tried to be a one-size-fits-them all
20 GEM started as an Intel-sponsored project in reaction to TTM's
22 providing a solution to every graphics memory-related problems, GEM
34 ------------------
39 Drivers wishing to support TTM must pass a filled :c:type:`ttm_bo_driver
46 The :c:type:`struct drm_global_reference <drm_global_reference>` is made
49 .. code-block:: c
62 memory manager at runtime. Your global TTM should have a type of
65 point at your driver-specific init and release routines, which probably
[all …]
|
| /Documentation/devicetree/ |
| D | booting-without-of.txt | 2 --------------------------------------------------
7 Freescale Semiconductor, FSL SOC and 32-bit additions
14 I - Introduction
21 II - The DT block format
27 III - Required content of the device tree
40 IV - "dtc", the device tree compiler
42 V - Recommendations for a bootloader
44 VI - System-on-a-chip devices and nodes
48 VII - Specifying interrupt information for devices
50 2) interrupt-parent property
[all …]
|
| /Documentation/x86/ |
| D | exception-tables.rst | 1 .. SPDX-License-Identifier: GPL-2.0
14 int verify_area(int type, const void * addr, unsigned long size)
19 in type (read or write). To do this, verify_read had to look up the
27 hardware present in every Linux-capable CPU handle this test.
51 (i.e. regs->eip) to find an address where the execution can continue
53 return address (again regs->eip) and returns. The execution will
73 long __gu_err = - 14 , __gu_val = 0;
75 if (((((0 + current_set[0])->tss.segment) == 0x18 ) ||
77 ((unsigned long)(__gu_addr ) <= 0xC0000000UL - (sizeof(*(buf)))))))
93 ( __gu_addr )) ), "i"(- 14 ), "0"( __gu_err )) ;
[all …]
|
| /Documentation/core-api/ |
| D | xarray.rst | 1 .. SPDX-License-Identifier: GPL-2.0+
12 The XArray is an abstract data type which behaves like a very large array
15 next or previous entry in a cache-efficient manner. In contrast to a
16 resizable array, there is no need to copy data or change MMU mappings in
17 order to grow the array. It is more memory-efficient, parallelisable
18 and cache friendly than a doubly-linked list. It takes advantage of
25 ``ULONG_MAX`` then the XArray is not the data type for you. The most
28 Each non-``NULL`` entry in the array has three bits associated with
32 Normal pointers may be stored in the XArray directly. They must be 4-byte
34 alloc_page(). It isn't true for arbitrary user-space pointers,
[all …]
|
| /Documentation/kernel-hacking/ |
| D | hacking.rst | 20 this document, being grossly under-qualified, but I always wanted to
30 - not associated with any process, serving a hardware interrupt;
32 - not associated with any process, serving a softirq or tasklet;
34 - running in kernel space, associated with a process (user context);
36 - running a process in user space.
45 to become truly non-preemptable.
48 ------------
69 -------------------------------
74 handler is never re-entered: if the same interrupt arrives, it is queued
88 -------------------------------------------------
[all …]
|
| /Documentation/translations/it_IT/kernel-hacking/ |
| D | hacking.rst | 1 .. include:: ../disclaimer-ita.rst
4 :ref:`Documentation/kernel-hacking/hacking.rst <kernel_hacking_hack>`
6 :Original: :ref:`Documentation/kernel-hacking/hacking.rst <kernel_hacking_hack>`
38 - non associata ad alcun processo, servendo un'interruzione hardware;
40 - non associata ad alcun processo, servendo un softirq o tasklet;
42 - in esecuzione nello spazio kernel, associata ad un processo
45 - in esecuzione di un processo nello spazio utente;
58 ---------------
81 ---------------------------------
102 ---------------------------------------------------
[all …]
|
| /Documentation/filesystems/ |
| D | proc.txt | 1 ------------------------------------------------------------------------------
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
38 3.2 /proc/<pid>/oom_score - Display current oom-killer score
[all …]
|
| /Documentation/admin-guide/ |
| D | kernel-parameters.txt | 5 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
119 Disable auto-serialization of AML methods
122 auto-serialization feature.
[all …]
|