Searched full:section (Results 1 – 25 of 686) sorted by relevance
12345678910>>...28
| /Documentation/firmware-guide/acpi/apei/ |
| D | output_format.rst | 13 section: <integer>, severity: <integer>, <severity string>
15 <section flags strings>
18 section_type: <section type string>
19 <section data>
23 <section flags strings># :=
27 <section type string> := generic processor error | memory error | \
30 <section data> :=
31 <generic processor section data> | <memory section data> | \
32 <pcie section data> | <null>
34 <generic processor section data> :=
[all …]
|
| /Documentation/livepatch/ |
| D | module-elf-format.rst | 29 Since apply_relocate_add() requires access to a module's section header
30 table, symbol table, and relocation section indices, ELF information is
31 preserved for livepatch modules (see section 5). Livepatch manages its own
52 relas reference are special livepatch symbols (see section 2 and 3). The
87 relocation section(s) to the driver once it loads.
92 between a livepatch relocation section and the target section (usually the
93 text section of a function) to which the relocation(s) apply. It is
98 Since ELF information is preserved for livepatch modules (see Section 5), a
99 livepatch relocation section can be applied simply by passing in the
100 appropriate section index to apply_relocate_add(), which then uses it to
[all …]
|
| /Documentation/locking/ |
| D | seqlock.rst | 15 read side critical section is even and the same sequence count value is
16 read again at the end of the critical section. The data in the set must
17 be copied out inside the read side critical section. If the sequence
18 count has changed between the start and the end of the critical section,
22 critical section. After starting the critical section the sequence count
24 the end of the write side critical section the sequence count becomes
27 A sequence counter write side critical section must never be preempted
48 write side section. If the read section can be invoked from hardirq or
50 disabled before entering the write section.
76 /* ... [[write-side critical section]] ... */
[all …]
|
| /Documentation/arch/arm64/ |
| D | acpi_object_usage.rst | 8 If a section number is used, it refers to a section number in the ACPI
12 outside of the UEFI Forum (see Section 5.2.6 of the specification).
51 BERT Section 18.3 (signature == "BERT")
64 BGRT Section 5.2.22 (signature == "BGRT")
78 CPEP Section 5.2.18 (signature == "CPEP")
105 DSDT Section 5.2.11.1 (signature == "DSDT")
127 ECDT Section 5.2.16 (signature == "ECDT")
136 EINJ Section 18.6 (signature == "EINJ")
146 ERST Section 18.5 (signature == "ERST")
161 FACS Section 5.2.10 (signature == "FACS")
[all …]
|
| D | arm-acpi.rst | 34 section we summarize a blog post [3] from Grant Likely that outlines the
165 Hardware reduced mode (see Section 4.1 of the ACPI 6.1 specification) will
173 tables (all section numbers refer to the ACPI 6.5 specification):
175 - RSDP (Root System Description Pointer), section 5.2.5
177 - XSDT (eXtended System Description Table), section 5.2.8
179 - FADT (Fixed ACPI Description Table), section 5.2.9
181 - DSDT (Differentiated System Description Table), section
184 - MADT (Multiple APIC Description Table), section 5.2.12
186 - GTDT (Generic Timer Description Table), section 5.2.24
188 - PPTT (Processor Properties Topology Table), section 5.2.30
[all …]
|
| /Documentation/arch/x86/ |
| D | exception-tables.rst | 85 ".section .fixup,\"ax\"\n"
89 ".section __ex_table,\"a\"\n"
99 ".section .fixup,\"ax\"\n"
103 ".section __ex_table,\"a\"\n"
113 ".section .fixup,\"ax\"\n"
117 ".section __ex_table,\"a\"\n"
146 > .section .fixup,"ax"
150 > .section __ex_table,"a"
161 memory. But what does the .section stuff do?????
165 > objdump --section-headers vmlinux
[all …]
|
| /Documentation/RCU/ |
| D | lockdep.rst | 9 critical section. Each flavor of RCU is tracked separately (but note
33 Check for RCU read-side critical section.
35 Check for RCU-bh read-side critical section.
37 Check for RCU-sched read-side critical section.
39 Check for SRCU read-side critical section.
83 1. An RCU read-side critical section (implicit), or
99 complain even if this was used in an RCU read-side critical section unless
108 critical section. However, a lockdep expression can be passed to them
111 false and they are called from outside any RCU read-side critical section.
114 either within an RCU read-side critical section or with wq->mutex held.
|
| D | lockdep-splat.rst | 15 RCU read-side critical section or (2) holding the right update-side lock.
73 section, but the "other info" list above shows that this is not the
84 code was invoked either from within an RCU read-side critical section
90 section. In this case, the critical section must span the use of the
104 read-side critical section, which again would have suppressed the
|
| /Documentation/bpf/ |
| D | llvm_reloc.rst | 17 Elf64_Addr r_offset; // Offset from the beginning of section.
23 int g1 __attribute__((section("sec")));
24 int g2 __attribute__((section("sec")));
25 static volatile int l1 __attribute__((section("sec")));
26 static volatile int l2 __attribute__((section("sec")));
55 Relocation section '.rel.text' at offset 0x190 contains 4 entries:
74 4: 0000000000000000 0 SECTION LOCAL DEFAULT 4 sec
85 section where the initial value of the global variable ``g2`` is stored.
88 and ``l2``. From the ``.rel.text`` section above, it is not clear
91 and represents a section. So for a static variable or function,
[all …]
|
| D | btf.rst | 47 __u32 type_off; /* offset of type section */
48 __u32 type_len; /* length of type section */
49 __u32 str_off; /* offset of string section */
50 __u32 str_len; /* length of string section */
62 The first string in the string section must be a null string. The rest of
68 The type id ``0`` is reserved for ``void`` type. The type section is parsed
86 #define BTF_KIND_DATASEC 15 /* Section */
92 Note that the type section encodes debug info, not just pure types.
433 * static variables with or without section attributes
434 * global variables with section attributes
[all …]
|
| /Documentation/core-api/ |
| D | cpu_hotplug.rst | 174 * The PREPARE section
176 The PREPARE section covers the state space from CPUHP_OFFLINE to
179 The startup callbacks in this section are invoked before the CPU is
196 The teardown callbacks in this section are not allowed to fail.
198 * The STARTING section
200 The STARTING section covers the state space between CPUHP_BRINGUP_CPU + 1
203 The startup callbacks in this section are invoked on the hotplugged CPU
209 The callbacks in this section are not allowed to fail.
214 * The ONLINE section
216 The ONLINE section covers the state space between CPUHP_AP_ONLINE + 1 and
[all …]
|
| /Documentation/userspace-api/media/ |
| D | fdl-appendix.rst | 61 A "Secondary Section" is a named appendix or a front-matter section of
66 the Document is in part a textbook of mathematics, a Secondary Section
136 :ref:`section 3 <fdl-section3>`.
204 (which should, if there were any, be listed in the History section of
245 Preserve the section entitled "History", and its title, and add to it
248 :ref:`Title Page <fdl-title-page>`. If there is no section entitled
260 section. You may omit a network location for a work that was
265 In any section entitled "Acknowledgements" or "Dedications", preserve
266 the section's title, and preserve in the section all the substance
273 their titles. Section numbers or the equivalent are not considered
[all …]
|
| /Documentation/gpu/ |
| D | msm-crash-dump.rst | 12 and all the contents of a section will be indented two spaces from the header.
13 Each section might have multiple array entries the start of which is designated
43 Section containing the contents of each ringbuffer. Each ringbuffer is
47 Ringbuffer ID (0 based index). Each ringbuffer in the section
98 Same format as the register section.
|
| /Documentation/gpu/rfc/ |
| D | index.rst | 2 GPU RFC Section
6 design issues before getting lost in the code details. This section is meant to
9 * Each RFC should be a section in this file, explaining the goal and main design
|
| /Documentation/filesystems/nfs/ |
| D | nfs41-server.rst | 53 … | ACCESS | REQ | | Section 18.1 |
55 … | BACKCHANNEL_CTL | REQ | | Section 18.33 |
57 … | BIND_CONN_TO_SESSION | REQ | | Section 18.34 |
59 … | CLOSE | REQ | | Section 18.2 |
61 … | COMMIT | REQ | | Section 18.3 |
63 … | CREATE | REQ | | Section 18.4 |
65 … | CREATE_SESSION | REQ | | Section 18.36 |
67 … | DELEGPURGE | OPT | FDELG (REQ) | Section 18.5 |
69 … | DELEGRETURN | OPT | FDELG, | Section 18.6 |
75 … | DESTROY_CLIENTID | REQ | | Section 18.50 |
[all …]
|
| /Documentation/mm/ |
| D | memory-model.rst | 70 sections. A section is represented with struct mem_section
73 that aids the sections management. The section size and maximal number
74 of section is specified using `SECTION_SIZE_BITS` and
85 NR\_MEM\_SECTIONS = 2 ^ {(MAX\_PHYSMEM\_BITS - SECTION\_SIZE\_BITS)}
108 The classic sparse encodes the section number of a page in page->flags
109 and uses high bits of a PFN to access the section that maps that page
110 frame. Inside a section, the PFN is the index to the array of pages.
158 this lack of user-api constraint to allow sub-section sized memory
160 memory hotplug. Sub-section support allows for 2MB as the cross-arch
|
| /Documentation/devicetree/bindings/sound/ |
| D | ti,ts3a227e.yaml | 32 description: Intended MICBIAS voltage (datasheet section 9.6.7).
45 description: key release debounce time in ms (datasheet section 9.6.7).
52 description: key press debounce time in ms (datasheet section 9.6.7).
61 description: headset insertion debounce time in ms (datasheet section 9.6.5).
|
| D | cirrus,cs42l51.yaml | 36 description: phandle to voltage regulator of digital interface section
39 description: phandle to voltage regulator of digital internal section
42 description: phandle to voltage regulator of analog internal section
|
| /Documentation/ABI/testing/ |
| D | devlink-resource-mlxsw | 17 Description: The linear section of the KVD is managed by software as a
24 Description: The hash based section of the KVD is managed by the switch
32 Description: The hash based section of the KVD is managed by the switch
|
| /Documentation/userspace-api/media/dvb/ |
| D | dmx-set-filter.rst | 37 to wait for a section to be loaded. A value of 0 means that no timeout
39 state whether a section should be CRC-checked, whether the filter should
41 stopped after the first section is received, and whether the filtering
|
| D | dmx-fread.rst | 35 This system call returns filtered data, which might be section or Packetized
42 if a section filter created with
69 - The section was not loaded within the stated timeout period.
|
| /Documentation/admin-guide/ |
| D | index.rst | 10 This initial section contains overall information, including the README
25 This section describes CPU vulnerabilities and their mitigations.
52 This is the beginning of a section with information of interest to
61 This is the beginning of a section with information of interest to
|
| /Documentation/arch/sparc/oradax/ |
| D | dax-hv-api.txt | 45 …device node in the guest MD (Section 8.24.17, “Database Analytics Accelerators (DAX) virtual-device
77 …See Section 36.2.1, “Query CCB Command Formats” for the corresponding CCB input and output formats.
106 …See Section 36.2.1, “Query CCB Command Formats” for the corresponding CCB input and output formats.
114 …guest MD (Section 8.24.17, “Database Analytics Accelerators (DAX) virtual-device node”). If the de…
378 …enabled in memory. By setting the appropriate flag in CCB_SUBMIT (Section 36.3.1, “ccb_submit”) it…
441 … [31:28] Primary Input Format (see Section 36.2.1.1.1, “Primary Input
443 … [27:23] Primary Input Element Size (see Section 36.2.1.1.2, “Primary
445 … [22:20] Primary Input Starting Offset (see Section 36.2.1.1.5, “Input
447 … [19] Secondary Input Format (see Section 36.2.1.1.3, “Secondary
449 … [18:16] Secondary Input Starting Offset (see Section 36.2.1.1.5, “Input
[all …]
|
| /Documentation/devicetree/bindings/mtd/partitions/ |
| D | partition.yaml | 69 boundary within the containing section or image. For example ‘align =
72 the containing section but is not included in the entry, meaning that
88 entry itself (the padding is performed only when its parent section is
100 to the containing section. It must be a power of 2.
107 parent section is assembled), the end result is that the entry ends
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-ima.rst | 145 'Supported targets' section.
180 dm_version_str := As described in the 'Table load' section above.
181 device_metadata := As described in the 'Table load' section above.
219 dm_version_str := As described in the 'Table load' section above.
221 … The format is same as 'device_metadata' described in the 'Table load' section above.
223 … The format is same as 'device_metadata' described in the 'Table load' section above.
225 … The format is same as 'active_table_hash' described in the 'Device resume' section above.
227 … The format is same as 'active_table_hash' described in the 'Device resume' section above.
259 dm_version_str := As described in the 'Table load' section above.
261 … The format is same as 'device_metadata' described in the 'Table load' section above.
[all …]
|
12345678910>>...28