Searched full:sections (Results 1 – 25 of 150) sorted by relevance
123456
| /Documentation/livepatch/ |
| D | module-elf-format.rst | 12 3. Livepatch relocation sections
38 relocation sections and symbols, which are described in this document. The
39 Elf constants used to mark livepatch symbols and relocation sections were
51 embedding special "dynrela" (dynamic rela) sections in the resulting patch
52 module Elf output. Using these dynrela sections, livepatch could resolve
57 relocation sections in place of dynrela sections, and the symbols that the
86 3. Livepatch relocation sections
89 A livepatch module manages its own Elf relocation sections to apply
96 multiple livepatch relocation sections associated with it (e.g. patches to
101 sections, as in the case of the sample livepatch module (see
[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 …]
|
| D | index.rst | 52 Invariant Sections. A copy of the license is included in the chapter
|
| /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/vm/ |
| D | memory-model.rst | 113 sections. A section is represented with struct mem_section
116 that aids the sections management. The section size and maximal number
123 The maximal number of sections is denoted `NR_MEM_SECTIONS` and
133 sections:
141 all the memory sections.
144 initialize the memory sections and the memory maps.
195 While `SPARSEMEM` presents memory as a collection of sections,
|
| /Documentation/RCU/ |
| D | whatisRCU.rst | 50 with example uses should focus on Sections 3 and 4. People who need to
95 critical sections.
160 read-side critical sections. Any RCU-protected data structure
172 read-side critical sections may be nested and/or overlapping.
180 read-side critical sections on all CPUs have completed.
182 any subsequent RCU read-side critical sections to complete.
195 read-side critical sections to complete, not necessarily for
213 after all ongoing RCU read-side critical sections have completed.
463 read-side critical sections.
480 RCU read-side critical sections that might be referencing that
[all …]
|
| D | rcu.rst | 37 read-side critical sections. So, if we remove an item from a
45 RCU read-side critical sections. SRCU also uses CPU-local
47 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
305 locks. RCU read-side critical sections are delimited by
353 sections, you should be using RCU rather than SRCU, because RCU
365 sections governed by srcu_read_lock() and srcu_read_unlock()
367 is what makes sleeping read-side critical sections tolerable --
370 system than RCU would be if RCU's read-side critical sections
373 The ability to sleep in read-side critical sections does not
408 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
|
| D | pi-futex.rst | 68 even if all critical sections are coded carefully to be deterministic
69 (i.e. all critical sections are short in duration and only execute a
|
| /Documentation/sound/soc/ |
| D | index.rst | 5 The documentation is spilt into the following sections:-
|
| /Documentation/devicetree/bindings/soc/rockchip/ |
| D | grf.txt | 6 From RK3368 SoCs, the GRF is divided into two sections,
13 ON RK3308 SoC, the GRF is divided into four 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
1238 The "Invariant Sections" are certain Secondary Sections whose titles
1239 are designated, as being those of Invariant Sections, in the notice
1243 Invariant Sections. If the Document does not identify any Invariant
1244 Sections then there are none.
1355 the conditions of sections 2 and 3 above, provided that you release
1379 G. Preserve in that license notice the full lists of Invariant Sections
1400 L. Preserve all the Invariant Sections of the Document,
1409 If the Modified Version includes new front-matter sections or
[all …]
|
| /Documentation/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/dev-tools/kunit/api/ |
| D | index.rst | 11 following sections:
|
| /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
386 #. Wait for all pre-existing RCU read-side critical sections to complete
516 | Given that multiple CPUs can start RCU read-side critical sections at |
603 | critical sections. Given such rearrangement, if a given RCU read-side |
605 | read-side critical sections are done? Won't the compiler |
617 | sections, no matter how aggressively the compiler scrambles the code. |
684 infinitely long, however, the following sections list a few
691 #. `Grace Periods Don't Partition Read-Side Critical Sections`_
692 #. `Read-Side Critical Sections Don't Partition Grace Periods`_
808 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/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 | 40 The following sections describe the various I/O methods in more detail.
|
| D | dev-mem2mem.rst | 36 devices are given in the following sections.
|
| /Documentation/admin-guide/mm/ |
| D | memory-hotplug.rst | 80 into chunks of the same size. These chunks are called "sections". The size of
84 Memory sections are combined into chunks referred to as "memory blocks". The
134 memory sections in this range are present and no memory holes exist in the
162 which will be performed on all sections in the block.
405 know nobody is in critical sections.
|
| /Documentation/RCU/Design/Memory-Ordering/ |
| D | Tree-RCU-Memory-Ordering.rst | 22 period that are within RCU read-side critical sections.
25 of that grace period that are within RCU read-side critical sections.
27 Note well that RCU-sched read-side critical sections include any region
43 of lock-based critical sections, memory barriers, and per-CPU
44 processing, as is described in the following sections.
51 ``->lock``. These critical sections use helper functions for lock
117 RCU read-side critical sections preceding and following the current
284 current task's or CPU's prior critical sections for any ``rcu_node``
468 ``->lock``. This means that any RCU read-side critical sections that
472 read-side critical sections that follow the idle period (the oval near
|
123456