Searched full:tables (Results 1 – 25 of 254) sorted by relevance
1234567891011
| /Documentation/admin-guide/acpi/ |
| D | initrd_table_override.rst | 4 Upgrading ACPI tables via initrd
11 upgrade the ACPI execution environment that is defined by the ACPI tables
12 via upgrading the ACPI tables provided by the BIOS with an instrumented,
13 modified, more recent version one, or installing brand new ACPI tables.
19 For a full list of ACPI tables that can be upgraded/installed, take a look
21 drivers/acpi/tables.c.
23 All ACPI tables iasl (Intel's ACPI compiler and disassembler) knows should
37 allows you to upgrade the buggy tables before your platform/BIOS vendor
45 platform provided ACPI tables or inserting new ACPI tables.
55 # Extract the machine's ACPI tables:
[all …]
|
| D | ssdt-overlays.rst | 13 recompiling the firmware image with updated ACPI tables, neither is practical:
19 user defined SSDT tables that contain the board specific information.
76 It works in a similar way with initrd based ACPI tables override/upgrade: SSDT
79 in loading multiple tables. Only SSDT and OEM tables are allowed. See
84 # Add the raw ACPI tables to an uncompressed cpio archive.
176 New tables can be loading by creating new directories in /sys/kernel/config/acpi/table
|
| /Documentation/ABI/testing/ |
| D | sysfs-firmware-dmi-tables | 1 What: /sys/firmware/dmi/tables/
13 The dmi/tables provides raw SMBIOS entry point and DMI tables
18 /sys/firmware/dmi/tables/smbios_entry_point
19 /sys/firmware/dmi/tables/DMI
22 tables.
|
| D | sysfs-firmware-efi | 26 Tables found via the EFI System Table. The order in
27 which the tables are printed forms an ABI and newer
32 What: /sys/firmware/efi/tables/rci2
|
| D | sysfs-firmware-dmi-entries | 6 SMBIOS tables to the operating system. Getting at this
11 information in these tables being correct. It equally
32 'T' in the DMI tables (adjacent or spread apart, it
|
| /Documentation/arch/x86/ |
| D | pti.rst | 15 page tables for use only when running userspace applications. When
17 page tables are switched to the full "kernel" copy. When the system
20 The userspace page tables contain only a minimal amount of kernel
36 When PTI is enabled, the kernel manages two sets of page tables.
41 Although _complete_, the user portion of the kernel page tables is
46 The userspace page tables map only the kernel data needed to enter
52 page tables like normal. The only difference is when the kernel
55 userspace page tables' PGD.
58 layers of the page tables. This leaves a single, shared set of
59 userspace page tables to manage. One PTE to lock, one set of
[all …]
|
| D | orc-unwinder.rst | 15 The ORC data consists of unwind tables which are generated by objtool.
56 that it needs more memory to store the ORC unwind tables: roughly 2-4MB
77 unwind tables take up ~50% more RAM (+1.3MB on an x86 defconfig kernel)
78 than DWARF-based eh_frame tables.
102 special sections like exception tables.
|
| D | index.rst | 15 exception-tables
|
| /Documentation/firmware-guide/acpi/ |
| D | acpi-lid.rst | 15 using a control method lid device. To implement this, the AML tables issue
31 However the word of "current" has ambiguity, some buggy AML tables return
35 initial returning value. When the AML tables implement this control method
42 There are buggy AML tables never notifying when the lid device state is
44 it is guaranteed that the AML tables always notify "closed" when the lid
47 tested, it is reliable from all AML tables.
85 isn't ready to handle the buggy AML tables.
107 opens given that some AML tables do not send "opened" notifications
114 handle the buggy AML tables.
|
| /Documentation/mm/ |
| D | split_page_table_lock.rst | 5 Originally, mm->page_table_lock spinlock protected all page tables of the
12 tables. Access to higher level tables protected by mm->page_table_lock.
40 Split page table lock for PTE tables is enabled compile-time if
42 If split lock is disabled, all tables are guarded by mm->page_table_lock.
44 Split page table lock for PMD tables is enabled, if it's enabled for PTE
45 tables and the architecture supports it (see below).
|
| D | page_tables.rst | 4 Page Tables
13 Page tables map virtual addresses as seen by the CPU into physical addresses
16 Linux defines page tables as a hierarchy which is currently five levels in
51 remains unused. By using hierarchical page tables large holes in the virtual
99 page tables were first introduced, so the *pte* is the lowermost page
106 the other levels to handle 4-level page tables. It is potentially unused,
110 handle 5-level page tables after the *pud* was introduced. Now it was clear
113 is only used on systems which actually have 5 levels of page tables, otherwise
147 which means skipped, and all operations performed on page tables will be
223 Linux kernel handles these page faults, creates tables and tables' entries,
[all …]
|
| /Documentation/crypto/ |
| D | descore-readme.rst | 62 - 30us per encryption (options: 64k tables, no IP/FP)
63 - 33us per encryption (options: 64k tables, FIPS standard bit ordering)
64 - 45us per encryption (options: 2k tables, no IP/FP)
65 - 48us per encryption (options: 2k tables, FIPS standard bit ordering)
66 - 275us to set a new key (uses 1k of key tables)
80 - 53us per encryption (uses 2k of tables)
81 - 96us to set a new key (uses 2.25k of key tables)
106 - 68us per encryption (uses 2k of tables)
107 - 96us to set a new key (uses 2.25k of key tables)
126 he claims to use 280k of tables but the iteration calculation seems
[all …]
|
| /Documentation/networking/devlink/ |
| D | devlink-dpipe.rst | 46 modeled as a graph of match/action tables. Each table represents a specific
62 filter new tables should be created describing those regions.
70 * tables
80 Drivers can register and unregister tables at run time, in order to support
120 different Virtual Routing and Forwarding (VRF) tables can be mapped to
155 match/action values and specific counter. By dumping the tables content the
156 interactions between tables can be resolved.
169 The LPM algorithm can be implemented as a list of hash tables. Each hash
177 The ``meta.lpm_prefix`` field is used to connect two LPM tables.
237 tables this table does multiple operations like TTL decrease and MTU check.
|
| /Documentation/arch/arm64/ |
| D | arm-acpi.rst | 123 Booting using ACPI tables
125 The only defined method for passing ACPI tables to the kernel on Arm
129 When an Arm system boots, it can either have DT information, ACPI tables,
132 present, the kernel will try to use ACPI tables, but only if they are present.
134 on the command line, the kernel will attempt to use ACPI tables first, but
135 fall back to DT if there are no ACPI tables present. The basic idea is that
138 Processing of ACPI tables may be disabled by passing acpi=off on the kernel
141 In order for the kernel to load and use ACPI tables, the UEFI implementation
145 kernel has, in effect, determined that ACPI tables are not present at that
151 The ACPI core will then locate and map in all other ACPI tables provided by
[all …]
|
| D | cpu-hotplug.rst | 39 arm64's ACPI tables assume that everything described is ``present``.
62 The ACPI tables must describe all the resources of the virtual machine. CPUs
76 re-read the static properties of the system from these static tables, and
|
| /Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-jpeg.rst | 70 quantization tables. In cases where a driver uses quantization tables
98 - Quantization tables segment.
100 - Huffman tables segment.
|
| D | vidioc-g-jpegcomp.rst | 51 jpeg_markers describes whether the huffman tables, quantization tables
105 - Define Huffman Tables
108 - Define Quantization Tables
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | nvidia,tegra20-emc.yaml | 61 If present, the emc-tables@ sub-nodes will be addressed.
79 Either an opaque enumerator to tell different tables apart, or
148 "^emc-tables@[a-f0-9-]+$":
154 An opaque enumerator to tell different tables apart.
213 emc-tables@0 {
239 emc-tables@1 {
|
| /Documentation/admin-guide/pm/ |
| D | intel_idle.rst | 58 ``intel_idle`` can use two sources of information: static tables of idle states
59 for different processor models included in the driver itself and the ACPI tables
65 tables with any processor model recognized by it; see
68 If the ACPI tables are going to be used for building the list of available idle
82 coming from the ACPI tables. [This step is skipped if ``intel_idle`` is
83 configured to ignore the ACPI tables; see `below <intel-idle-parameters_>`_.]
94 using the ACPI tables for the enumeration of idle states is not required
99 preliminary list of idle states coming from the ACPI tables. In that case user
105 not been exposed by the platform firmware (through the ACPI tables).
109 tables is used for building the final list that will be supplied to the
[all …]
|
| /Documentation/driver-api/mtd/ |
| D | spi-nor.rst | 11 standard set of internal read-only parameter tables.
13 The SPI NOR driver queries the SFDP tables in order to determine the
14 flash's parameters and settings. If the flash defines the SFDP tables
22 that is not covered by the SFDP tables (e.g. Block Protection), or
72 Please dump the SFDP tables using ``xxd -p``. It enables us to do
|
| /Documentation/devicetree/bindings/display/ |
| D | renesas,cmm.yaml | 16 It provides image enhancement functions such as 1-D look-up tables (LUT),
17 3-D look-up tables (CLU), 1D-histogram generation (HGO), and color
|
| /Documentation/staging/ |
| D | crc32.rst | 129 When space is more constrained, smaller tables can be used, e.g. two
133 technique, because tables larger than 256 entries use too much memory and,
147 two different 256-entry tables. Each contains the remainder required
148 to cancel out the corresponding byte. The tables are different because the
156 This can be extended to "slicing by 4" using 4 256-entry tables.
158 broken into bytes and looked up in the tables. Because the 32-bit shift
|
| /Documentation/gpu/amdgpu/ |
| D | amdgpu-glossary.rst | 56 Graphics Translation Tables. This is a memory pool managed through TTM
59 table for use by the kernel driver or into per process GPUVM page tables
|
| /Documentation/features/ |
| D | arch-support.txt | 6 The meaning of entries in the tables is:
|
| /Documentation/admin-guide/mm/ |
| D | concepts.rst | 48 pages. These mappings are described by page tables that allow
50 memory address. The page tables are organized hierarchically.
52 The tables at the lowest level of the hierarchy contain physical
53 addresses of actual pages used by the software. The tables at higher
78 and the third level page tables. In Linux such pages are called
|
1234567891011