Searched full:sections (Results 1 – 25 of 180) sorted by relevance
12345678
| /Documentation/livepatch/ |
| D | module-elf-format.rst | 32 relocation sections and symbols, which are described in this document. The
33 ELF constants used to mark livepatch symbols and relocation sections were
45 embedding special "dynrela" (dynamic rela) sections in the resulting patch
46 module ELF output. Using these dynrela sections, livepatch could resolve
51 relocation sections in place of dynrela sections, and the symbols that the
80 3. Livepatch relocation sections
83 A livepatch module manages its own ELF relocation sections to apply
90 multiple livepatch relocation sections associated with it (e.g. patches to
95 sections, as in the case of the sample livepatch module (see
110 Livepatch relocation sections must be marked with the SHF_RELA_LIVEPATCH
[all …]
|
| /Documentation/userspace-api/media/ |
| D | fdl-appendix.rst | 75 The "Invariant Sections" are certain
76 :ref:`Secondary Sections <fdl-secondary>` whose titles are designated,
77 as being those of Invariant Sections, in the notice that says that the
192 of the :ref:`Document <fdl-document>` under the conditions of sections
237 :ref:`Invariant Sections <fdl-invariant>` and required
271 Preserve all the :ref:`Invariant Sections <fdl-invariant>` of the
285 front-matter sections or appendices that qualify as
286 :ref:`Secondary Sections <fdl-secondary>` and contain no material
288 of these sections as invariant. To do this, add their titles to the list
289 of :ref:`Invariant Sections <fdl-invariant>` in the Modified Version's
[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
80 The maximal number of sections is denoted `NR_MEM_SECTIONS` and
90 sections:
98 all the memory sections.
101 initialize the memory sections and the memory maps.
152 While `SPARSEMEM` presents memory as a collection of sections,
|
| /Documentation/litmus-tests/rcu/ |
| D | RCU+sync+read.litmus | 7 * sees all stores done in prior RCU read-side critical sections. Such
8 * read-side critical sections would have ended before the grace period ended.
|
| /Documentation/ABI/testing/ |
| D | devlink-resource-mlxsw | 8 is divided into two sections, the first is hash-based table
10 between the linear and hash-based sections is static and
|
| /Documentation/RCU/ |
| D | whatisRCU.rst | 59 with example uses should focus on Sections 3 and 4. People who need to
104 critical sections.
169 can preempt RCU read-side critical sections. Any RCU-protected
181 section. Note that RCU read-side critical sections may be nested
190 all pre-existing RCU read-side critical sections on all CPUs
193 sections to complete. For example, consider the following
206 read-side critical sections to complete, not necessarily for
225 critical sections have completed. This callback variant is
481 read-side critical sections.
498 RCU read-side critical sections that might be referencing that
[all …]
|
| D | rcu.rst | 36 read-side critical sections. So, if we remove an item from a
44 RCU read-side critical sections. SRCU also uses CPU-local
46 critical sections. These variants of RCU detect grace periods
|
| D | checklist.rst | 59 2. Do the RCU read-side critical sections make proper use of
338 locks. RCU read-side critical sections are delimited by
403 sections, you should be using RCU rather than SRCU, because RCU
415 sections governed by srcu_read_lock() and srcu_read_unlock()
417 is what makes sleeping read-side critical sections tolerable --
420 system than RCU would be if RCU's read-side critical sections
423 The ability to sleep in read-side critical sections does not
464 read-side critical sections. It is the responsibility of the
|
| /Documentation/locking/ |
| D | seqlock.rst | 28 or interrupted by read side sections. Otherwise the reader will spin for
43 multiple writers. Write side critical sections must thus be serialized
96 sections must be serialized and non-preemptible. This variant of
99 side critical sections are properly serialized.
152 Use seqcount_latch_t when the write side sections cannot be protected
|
| /Documentation/sound/soc/ |
| D | index.rst | 5 The documentation is spilt into the following sections:-
|
| /Documentation/admin-guide/ |
| D | spkguide.txt | 16 Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
97 See the sections on loading modules and software synthesizers later in
1283 The "Invariant Sections" are certain Secondary Sections whose titles
1284 are designated, as being those of Invariant Sections, in the notice
1288 Invariant Sections. If the Document does not identify any Invariant
1289 Sections then there are none.
1400 the conditions of sections 2 and 3 above, provided that you release
1424 G. Preserve in that license notice the full lists of Invariant Sections
1445 L. Preserve all the Invariant Sections of the Document,
1454 If the Modified Version includes new front-matter sections or
[all …]
|
| /Documentation/dev-tools/kunit/api/ |
| D | index.rst | 15 following sections:
|
| /Documentation/arch/x86/ |
| D | orc-unwinder.rst | 21 information to the .orc_unwind and .orc_unwind_ip sections.
23 The per-object ORC sections are combined at link time and are sorted and
102 special sections like exception tables.
146 structs, and writes them to the .orc_unwind and .orc_unwind_ip sections
|
| /Documentation/litmus-tests/locking/ |
| D | RM-fixed.litmus | 7 * to locking, where code can be freely moved into critical sections,
|
| D | RM-broken.litmus | 7 * to locking, where code can be freely moved into critical sections,
|
| /Documentation/gpu/rfc/ |
| D | index.rst | 17 the main core, helper or driver sections.
|
| /Documentation/trace/coresight/ |
| D | coresight-perf.rst | 18 a perf.data trace file. That file would have AUX sections if CoreSight
24 You should find some sections of this file have AUX data blocks like::
115 These statistic files log some aspects of the AUX data sections in
|
| /Documentation/userspace-api/media/dvb/ |
| D | dmx-set-buffer-size.rst | 35 filtered data. The default size is two maximum sized sections, i.e. if
|
| /Documentation/RCU/Design/Requirements/ |
| D | Requirements.rst | 74 of all pre-existing RCU read-side critical sections. An RCU read-side
387 #. Wait for all pre-existing RCU read-side critical sections to complete
517 | Given that multiple CPUs can start RCU read-side critical sections at |
604 | critical sections. Given such rearrangement, if a given RCU read-side |
606 | read-side critical sections are done? Won't the compiler |
618 | sections, no matter how aggressively the compiler scrambles the code. |
685 infinitely long, however, the following sections list a few
692 #. `Grace Periods Don't Partition Read-Side Critical Sections`_
693 #. `Read-Side Critical Sections Don't Partition Grace Periods`_
809 Grace Periods Don't Partition Read-Side Critical Sections
[all …]
|
| /Documentation/hwmon/ |
| D | vexpress.rst | 12 * "Hardware Description" sections of the Technical Reference Manuals
|
| D | userspace-tools.rst | 29 1) compile all drivers in I2C and Hardware Monitoring sections as modules
|
| /Documentation/powerpc/ |
| D | vmemmap_dedup.rst | 22 Here's how things look like on device-dax after the sections are populated::
50 Here's how things look like on device-dax after the sections are populated::
79 Here's how things look like on device-dax after the sections are populated::
|
| /Documentation/fb/ |
| D | sa1100fb.rst | 27 options may not be enough to configure the display. Adding sections to
|
| /Documentation/userspace-api/media/v4l/ |
| D | io.rst | 39 The following sections describe the various I/O methods in more detail.
|
| D | dev-mem2mem.rst | 36 devices are given in the following sections.
|
12345678