Searched full:section (Results 1 – 25 of 504) sorted by relevance
12345678910>>...21
| /Documentation/filesystems/nfs/ |
| D | nfs41-server.txt | 50 | ACCESS | REQ | | Section 18.1 |
51 I | BACKCHANNEL_CTL | REQ | | Section 18.33 |
52 I | BIND_CONN_TO_SESSION | REQ | | Section 18.34 |
53 | CLOSE | REQ | | Section 18.2 |
54 | COMMIT | REQ | | Section 18.3 |
55 | CREATE | REQ | | Section 18.4 |
56 I | CREATE_SESSION | REQ | | Section 18.36 |
57 NS*| DELEGPURGE | OPT | FDELG (REQ) | Section 18.5 |
58 | DELEGRETURN | OPT | FDELG, | Section 18.6 |
61 I | DESTROY_CLIENTID | REQ | | Section 18.50 |
[all …]
|
| /Documentation/livepatch/ |
| D | module-elf-format.rst | 13 3.1 Livepatch relocation section format
18 6. Symbol table and Elf section access
36 Since apply_relocate_add() requires access to a module's section header
37 table, symbol table, and relocation section indices, Elf information is
38 preserved for livepatch modules (see section 5). Livepatch manages its own
59 relas reference are special livepatch symbols (see section 2 and 3). The
94 relocation section(s) to the driver once it loads.
99 between a livepatch relocation section and the target section (usually the
100 text section of a function) to which the relocation(s) apply. It is
105 Since Elf information is preserved for livepatch modules (see Section 5), a
[all …]
|
| /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/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).
30 BERT Section 18.3 (signature == "BERT")
43 BGRT Section 5.2.22 (signature == "BGRT")
50 CPEP Section 5.2.18 (signature == "CPEP")
77 DSDT Section 5.2.11.1 (signature == "DSDT")
99 ECDT Section 5.2.16 (signature == "ECDT")
108 EINJ Section 18.6 (signature == "EINJ")
118 ERST Section 18.5 (signature == "ERST")
133 FACS Section 5.2.10 (signature == "FACS")
[all …]
|
| D | arm-acpi.rst | 33 section we summarize a blog post [2] from Grant Likely that outlines the
164 Hardware reduced mode (see Section 4.1 of the ACPI 6.1 specification) will
172 tables (all section numbers refer to the ACPI 6.1 specification):
174 - RSDP (Root System Description Pointer), section 5.2.5
176 - XSDT (eXtended System Description Table), section 5.2.8
178 - FADT (Fixed ACPI Description Table), section 5.2.9
180 - DSDT (Differentiated System Description Table), section
183 - MADT (Multiple APIC Description Table), section 5.2.12
185 - GTDT (Generic Timer Description Table), section 5.2.24
188 Table), section 5.2.6, specifically Table 5-31.
[all …]
|
| /Documentation/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/ABI/testing/ |
| D | sysfs-devices-memory | 37 is read-only and contains the section ID in hexadecimal
39 memory section directory name.
47 online/offline state of the memory section. When written,
49 memory section (see removable file description above)
58 by root to offline that section.
80 memory section 9 on node0:
91 memory section directory. For example, the following symbolic
92 link is created for memory section 9 on node0.
|
| 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/RCU/ |
| D | lockdep.txt | 5 critical section. Each flavor of RCU is tracked separately (but note
27 Check for RCU read-side critical section.
29 Check for RCU-bh read-side critical section.
31 Check for RCU-sched read-side critical section.
33 Check for SRCU read-side critical section.
76 1. An RCU read-side critical section (implicit), or
92 complain if this was used in an RCU read-side critical section unless one
101 being in an RCU read-side critical section. In the future, separate
|
| D | lockdep-splat.txt | 9 RCU read-side critical section or (2) holding the right update-side lock.
68 section, but the "other info" list above shows that this is not the
79 code was invoked either from within an RCU read-side critical section
85 section. In this case, the critical section must span the use of the
99 read-side critical section, which again would have suppressed the
|
| D | whatisRCU.txt | 37 Section 1, though most readers will profit by reading this section at
39 experiment with should focus on Section 2. People who prefer to start
41 understand the RCU implementation should focus on Section 5, then dive
43 focus on Section 6. Section 7 serves as an index to the docbook API
44 documentation, and Section 8 is the traditional answer key.
46 So, start with the section that makes the most sense to you and your
143 entering an RCU read-side critical section. It is illegal
144 to block while in an RCU read-side critical section, though
147 accessed during an RCU read-side critical section is guaranteed to
148 remain unreclaimed for the full duration of that critical section.
[all …]
|
| D | UP.rst | 69 the same critical section, then the code would need to create
109 list, and is therefore within an RCU read-side critical section.
111 read-side critical section, and is not permitted to block.
127 the process-context critical section. This would result in
140 of an RCU read-side critical section. If synchronize_rcu()
|
| /Documentation/media/uapi/ |
| D | fdl-appendix.rst | 68 A “Secondary Section” is a named appendix or a front-matter section of
73 the Document is in part a textbook of mathematics, a Secondary Section
143 :ref:`section 3 <fdl-section3>`.
211 (which should, if there were any, be listed in the History section of
252 Preserve the section entitled “History”, and its title, and add to it
255 :ref:`Title Page <fdl-title-page>`. If there is no section entitled
267 section. You may omit a network location for a work that was
272 In any section entitled “Acknowledgements” or “Dedications”, preserve
273 the section's title, and preserve in the section all the substance
280 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/bpf/ |
| 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 */
88 Note that the type section encodes debug info, not just pure types.
424 * static variables with or without section attributes
425 * global variables with section attributes
[all …]
|
| /Documentation/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/vm/ |
| D | memory-model.rst | 115 sections. A section is represented with :c:type:`struct mem_section`
118 that aids the sections management. The section size and maximal number
119 of section is specified using `SECTION_SIZE_BITS` and
130 NR\_MEM\_SECTIONS = 2 ^ {(MAX\_PHYSMEM\_BITS - SECTION\_SIZE\_BITS)}
156 The classic sparse encodes the section number of a page in page->flags
157 and uses high bits of a PFN to access the section that maps that page
158 frame. Inside a section, the PFN is the index to the array of pages.
206 this lack of user-api constraint to allow sub-section sized memory
208 memory hotplug. Sub-section support allows for 2MB as the cross-arch
|
| /Documentation/media/uapi/dvb/ |
| D | dmx-set-filter.rst | 44 to wait for a section to be loaded. A value of 0 means that no timeout
46 state whether a section should be CRC-checked, whether the filter should
48 stopped after the first section is received, and whether the filtering
|
| D | dmx-fread.rst | 43 This system call returns filtered data, which might be section or Packetized
50 if a section filter created with
78 - The section was not loaded within the stated timeout period.
|
| /Documentation/admin-guide/ |
| D | index.rst | 9 This initial section contains overall information, including the README
21 This section describes CPU vulnerabilities and their mitigations.
45 This is the beginning of a section with information of interest to
|
| /Documentation/ABI/stable/ |
| D | sysfs-driver-usb-usbtmc | 10 (USBTMC) Revision 1.0" section 4.2.1.8.
24 USB488 Specification (USBTMC-USB488) Revision 1.0" section
|
| /Documentation/devicetree/bindings/sound/ |
| D | cs35l35.txt | 79 See Section 4.3 Internal Class H Algorithm in the Datasheet.
84 Section 7.29 Class H Control
89 Section 7.30 Class H Headroom Control
92 Section 7.31 Class H Release Rate
95 Section 7.32 Class H Weak FET Drive Control
100 Section 7.34 Class H VP Control
|
| /Documentation/networking/ |
| D | multiqueue.txt | 5 Section 1: Base driver requirements for implementing multiqueue support
12 Section 1: Base driver requirements for implementing multiqueue support
28 Section 2: Qdisc support for multiqueue devices
48 Section 3: Brief howto using MULTIQ for multiqueue devices
|
| D | altera_tse.txt | 136 Section 5.2.2.1.2. This statistics is the count of frames that are successfully
140 Section 5.2.2.1.5. This statistic is the count of frames that are successfully
145 802.3-2012, Section 5.2.2.1.6. This statistic is the count of frames that are
150 Section 5.2.2.1.7. This statistic is the count of frames that are not an
155 Section 5.2.2.1.8. This statistic is the count of data and pad bytes
159 Section 5.2.2.1.14. This statistic is the count of data and pad bytes
163 802.3-2012, Section 30.3.4.2. This statistic is a count of PAUSE frames
167 802.3-2012, Section 30.3.4.3. This statistic is a count of PAUSE frames
|
| /Documentation/devicetree/bindings/usb/ |
| D | samsung-hsotg.txt | 23 - vusb_d-supply: phandle to voltage regulator of digital section,
24 - vusb_a-supply: phandle to voltage regulator of analog section.
|
12345678910>>...21