| /Documentation/mm/ |
| D | split_page_table_lock.rst | 2 Split page table lock
8 scalability, split page table lock was introduced.
10 With split page table lock we have separate per-table lock to serialize
11 access to the table. At the moment we use split lock for PTE and PMD
14 There are helpers to lock/unlock a table and other accessor functions:
17 maps PTE and takes PTE table lock, returns pointer to PTE with
18 pointer to its PTE table lock, or returns NULL if no PTE table;
20 maps PTE, returns pointer to PTE with pointer to its PTE table
21 lock (not taken), or returns NULL if no PTE table;
23 maps PTE, returns pointer to PTE with pointer to its PTE table
[all …]
|
| D | page_tables.rst | 39 sizes. When Linux was created, 4KB pages and a single page table called
42 this single table were referred to as *PTE*:s - page table entries.
44 The software page table hierarchy reflects the fact that page table hardware has
45 become hierarchical and that in turn is done to save page table memory and
48 One could of course imagine a single, linear page table with enormous amounts
49 of entries, breaking down the whole memory into single pages. Such a page table
52 address space does not waste valuable page table memory, because it will suffice
53 to mark large areas as unmapped at a higher level in the page table hierarchy.
55 Additionally, on modern CPUs, a higher level page table entry can point directly
57 megabytes or even gigabytes in a single high-level page table entry, taking
[all …]
|
| D | mmu_notifier.rst | 1 When do you need to notify inside page table lock ?
6 the page table lock. But that notification is not necessary in all cases.
9 thing like ATS/PASID to get the IOMMU to walk the CPU page table to access a
11 those secondary TLB while holding page table lock when clearing a pte/pmd:
14 B) a page table entry is updated to point to a new page (COW, write fault
23 - take page table lock
24 - clear page table entry and notify ([pmd/pte]p_huge_clear_flush_notify())
25 - set page table entry to point to new page
27 If clearing the page table entry is not followed by a notify before setting
53 CPU-thread-0 {COW_step1: {update page table to point to new page for addrA}}
[all …]
|
| D | page_table_check.rst | 4 Page Table Check
10 Page table check allows to harden the kernel by ensuring that some types of
13 Page table check performs extra verifications at the time when new pages become
14 accessible from the userspace by getting their page table entries (PTEs PMDs
15 etc.) added into the table.
18 performance and memory overhead associated with the page table check. Therefore,
20 extra hardening outweighs the performance costs. Also, because page table check
25 It can also be used to do page table entry checks over various flags, dump
49 Enabling Page Table Check
61 table support without extra kernel parameter.
[all …]
|
| /Documentation/arch/arm64/ |
| D | acpi_object_usage.rst | 10 the table signature (the first four bytes of the table) is the only portion
11 of the table recognized by the specification, and the actual table is defined
28 Table Usage for ARMv8 Linux
32 **Arm Error Source Table**
34 This table informs the OS of any error nodes in the system that are
39 **Arm Generic diagnostic Dump and Reset Device Interface Table**
41 This table describes a non-maskable event, that is used by the platform
46 **Arm Performance Monitoring Table**
48 This table describes the properties of PMU support implemented by
53 **Boot Error Record Table**
[all …]
|
| D | arm-acpi.rst | 62 table as hardware vendors and other OS vendors. In fact, there is no
126 is via the UEFI system configuration table. Just so it is explicit, this
142 MUST set the ACPI_20_TABLE_GUID to point to the RSDP table (the table with
148 If the pointer to the RSDP table is correct, the table will be mapped into
152 using the addresses in the RSDP table to find the XSDT (eXtended System
153 Description Table). The XSDT in turn provides the addresses to all other
155 this table and map in the tables listed.
157 The ACPI core will ignore any provided RSDT (Root System Description Table).
162 (Fixed ACPI Description Table). Any 32-bit address fields in the FADT will
177 - XSDT (eXtended System Description Table), section 5.2.8
[all …]
|
| /Documentation/networking/devlink/ |
| D | devlink-dpipe.rst | 46 modeled as a graph of match/action tables. Each table represents a specific
74 the packet. A ``table`` describes hardware blocks. An ``entry`` describes
75 the actual content of a specific table.
85 is hardware counting for a specific table.
90 * ``table_get``: Receive a table's description.
92 * ``entries_get``: Receive a table's current entries.
93 * ``counters_set``: Enable or disable counters on a table.
95 Table section in Model
98 The driver should implement the following operations for each table:
102 * ``entries_dump``: Dump the actual content of the table.
[all …]
|
| /Documentation/ABI/testing/ |
| D | configfs-acpi | 9 What: /config/acpi/table
15 tables. The attributes of a user define table are:
21 closed the table will be loaded and ACPI devices
28 after the table has been loaded by filling the aml entry:
31 - ASCII table signature
34 - length of table in bytes, including the header
43 - ASCII OEM table identification
|
| D | sysfs-firmware-efi | 5 EFI system table.
11 Description: It shows the physical address of runtime service table entry in
12 the EFI system table.
18 Description: It shows the physical address of config table entry in the EFI
19 system table.
26 Tables found via the EFI System Table. The order in
36 Table version 2 on Dell EMC PowerEdge systems in binary format
|
| D | sysfs-ibft | 5 files that expose the iSCSI Boot Firmware Table initiator data.
12 files that expose the iSCSI Boot Firmware Table target data.
22 files that expose the iSCSI Boot Firmware Table NIC data.
30 acpi table header of the iBFT structure. This will allow for
31 identification of the creator of the table which is useful in
|
| D | debugfs-intel-iommu | 50 This file dumps the table entries for Interrupt
60 IR table address:100900000
67 IR table address:100300000
76 IR table address:100900000
84 as root table, context table, PASID directory and PASID
85 table entries in debugfs. For legacy mode, it doesn't
95 IOMMU dmar1: Root Table Address: 0x103027000
105 IOMMU dmar0: Root Table Address: 0x103028000
226 This file dumps a specified page table of Intel IOMMU
230 page table by the debugfs file in the debugfs device
[all …]
|
| /Documentation/admin-guide/acpi/ |
| D | initrd_table_override.rst | 27 - ACPI_SIG_FACS (does not have an ordinary ACPI table header)
44 ACPI BIOS table compatibility with the Linux kernel by modifying old
61 # For example add this statement into a _PRT (PCI Routing Table) function
71 # archive. Note that if the table put here matches a platform table
72 # (similar Table Signature, and similar OEMID, and similar OEM Table ID)
73 # with a more recent OEM Revision, the platform table will be upgraded by
74 # this table. If the table put here doesn't match a platform table
75 # (dissimilar Table Signature, or dissimilar OEMID, or dissimilar OEM Table
76 # ID), this table will be appended.
94 [ 1.268089] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
|
| /Documentation/security/tpm/ |
| D | tpm_event_log.rst | 37 a custom configuration table defined by the stub itself. Unfortunately,
38 the events generated by ExitBootServices() don't end up in the table.
40 The firmware provides so called final events configuration table to sort
41 out this issue. Events gets mirrored to this table after the first time
46 final events table size while the stub is still running to the custom
47 configuration table so that the TPM driver can later on skip these events when
48 concatenating two halves of the event log from the custom configuration table
49 and the final events table.
|
| /Documentation/devicetree/bindings/regulator/ |
| D | pwm-regulator.yaml | 17 Voltage Table:
18 When in this mode, a voltage table (See below) of predefined voltage <=>
20 regulator can only operate at the voltages supplied in the table.
30 solution when compared with voltage-table mode above. This solution does
34 If voltage-table is provided, then the device will be used in Voltage Table
35 Mode. If no voltage-table is provided, then the device will be used in
48 voltage-table:
49 description: Voltage and Duty-Cycle table.
111 // Voltage Table Example:
120 voltage-table = <1114000 0>,
|
| /Documentation/devicetree/bindings/reserved-memory/ |
| D | nvidia,tegra210-emc-table.yaml | 4 $id: http://devicetree.org/schemas/reserved-memory/nvidia,tegra210-emc-table.yaml#
7 title: NVIDIA Tegra210 EMC Frequency Table
14 EMC frequency table via a reserved memory region.
21 const: nvidia,tegra210-emc-table
25 frequency table
|
| /Documentation/sphinx-static/ |
| D | theme_overrides.css | 47 /* Keep fields from being strangely far apart due to inheirited table CSS. */
48 .rst-content table.field-list th.field-name {
52 .rst-content table.field-list td.field-body {
67 /* table:
74 .wy-table-responsive table td { white-space: normal; }
75 .wy-table-responsive { overflow: auto; }
76 .rst-content table.docutils caption { text-align: left; font-size: 100%; }
84 caption, .wy-table caption, .rst-content table.field-list caption {
|
| /Documentation/devicetree/bindings/mtd/partitions/ |
| D | tplink,safeloader-partitions.yaml | 19 Partitions specified in partitions table cover whole flash space. Some
25 based partitions table. That offset is picked at manufacturing process
35 partitions-table-offset:
36 description: Flash offset of partitions table
44 - partitions-table-offset
52 partitions-table-offset = <0x100000>;
|
| /Documentation/filesystems/ext4/ |
| D | group_descr.rst | 10 the block group descriptor table unless the sparse_super feature flag
14 the inode table (i.e. they can float). This means that within a block
16 and the group descriptor table. The flex_bg mechanism uses this
45 .. list-table::
64 - Lower 32-bits of location of inode table.
80 - Block group flags. See the bgflags_ table below.
98 inode table for this group.
124 - Upper 32-bits of location of inodes table.
162 .. list-table::
169 - inode table and bitmap are not initialized (EXT4_BG_INODE_UNINIT).
[all …]
|
| D | bitmaps.rst | 9 The inode bitmap records which entries in the inode table are in use.
12 block or inode table entry. This implies a block group size of 8 *
23 Inode Table
26 descriptor points to the start of the table, and the superblock records
|
| /Documentation/networking/ |
| D | vrf.rst | 17 through the socket then use the routing table associated with the VRF
31 A VRF device is created with an associated route table. Network interfaces
35 | vrf-blue | ===> route table 10
66 1. VRF device is created with an association to a FIB table.
69 ip link add vrf-blue type vrf table 10
72 2. An l3mdev FIB rule directs lookups to the table associated with the device.
80 ip ru add oif vrf-blue table 10
81 ip ru add iif vrf-blue table 10
83 3. Set the default route for the table (and hence default route for the VRF)::
85 ip route add table 10 unreachable default metric 4278198272
[all …]
|
| D | vxlan.rst | 33 entry in the forwarding table. The destination port number is set to
48 forwarding table using the new bridge command.
50 1. Create forwarding table entry::
54 2. Delete forwarding table entry::
58 3. Show forwarding table::
80 UDP port table 0:
84 UDP port table 1:
|
| /Documentation/driver-api/ |
| D | mtdnand.rst | 425 with the bad block marker positions. See bad block table support for
428 Bad block table support
435 the first page in the block. This is time consuming so a bad block table
442 The bad block table contains all bad block information of the device
447 A bad block table is used per chip and contains the bad block
452 The bad block table is located at a fixed offset in the chip
457 The bad block table is automatically placed and detected either at
462 The bad block table is mirrored on the chip (device) to allow updates
463 of the bad block table without data loss.
466 nand_default_bbt() selects appropriate default bad block table
[all …]
|
| /Documentation/security/ |
| D | siphash.rst | 16 sequence numbers, secure cookies, or mask it off for use in a hash table.
59 void init_hashtable(struct some_hashtable *table)
61 get_random_bytes(&table->key, sizeof(table->key));
64 …static inline hlist_head *some_hashtable_bucket(struct some_hashtable *table, struct interesting_i…
66 …return &table->hashtable[siphash(input, sizeof(*input), &table->key) & (HASH_SIZE(table->hashtable…
181 void init_hashtable(struct some_hashtable *table)
183 get_random_bytes(&table->key, sizeof(table->key));
186 …static inline hlist_head *some_hashtable_bucket(struct some_hashtable *table, struct interesting_i…
188 …return &table->hashtable[hsiphash(input, sizeof(*input), &table->key) & (HASH_SIZE(table->hashtabl…
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-ima.rst | 91 1. Table load
94 #. Table clear
97 1. Table load:
99 When a new table is loaded in a device's inactive table slot,
101 targets in the table are measured.
127 Represents the data (as name=value pairs) from various targets in the table,
128 which is being loaded into the DM device's inactive table slot.
134 … Represents nth target in the table (from 0 to N-1 targets specified in <num_device_targets>)
149 For instance, if a linear device is created with the following table entries,
171 data from previous load of an active table are measured.
[all …]
|
| /Documentation/filesystems/ |
| D | squashfs.rst | 142 | inode table |
145 | table |
148 | table |
151 | table |
154 | lookup table |
157 | table |
199 in a directory table. Directories are accessed using the start address of
244 3.5 Fragment lookup table
248 location on disk and compressed size using a fragment lookup table. This
249 fragment lookup table is itself stored compressed into metadata blocks.
[all …]
|