| /linux/tools/perf/Documentation/ |
| H A D | callchain-overhead-calculation.txt | 3 The CPU overhead can be shown in two columns as 'Children' and 'Self'
101 So '\_\_libc_start_main' and 'main' are shown first since they have
105 Since v3.16 the 'children' overhead is shown by default and the output
|
| /linux/Documentation/RCU/Design/Memory-Ordering/ |
| H A D | Tree-RCU-Memory-Ordering.rst | 197 shown below, which is one of several functions that enforce ordering of
275 portion of RCU's grace period guarantee is shown in the following
285 period until a later call to ``rcu_accelerate_cbs()``, as shown in the
288 One set of code paths shown on the left invokes ``rcu_accelerate_cbs()``
342 counter, as shown below:
370 to the newly advanced value from the ``rcu_state`` structure, as shown
410 non-idle CPUs report their own quiescent states, as shown in the
425 its leaf ``rcu_node`` lock. Therefore, all execution shown in this
462 traverses up the ``rcu_node`` tree as shown at the bottom of the
486 effects are as shown below:
[all …]
|
| /linux/Documentation/devicetree/bindings/bus/ |
| H A D | ti,da850-mstpri.txt | 15 Example for da850-lcdk is shown below.
|
| H A D | mvebu-mbus.txt | 139 In the shown example, the translation entry in the 'ranges' property is what
193 of 0xf0000000, or 0xd0000000 for the NOR device shown above, if such region is
214 See the example below, where a more complete device tree is shown:
|
| /linux/arch/arm/boot/dts/sigmastar/ |
| H A D | mstar-infinity3.dtsi | 16 // overclock frequencies below, shown to work fine up to 1.3 GHz
|
| /linux/Documentation/kbuild/ |
| H A D | gendwarfksyms.rst | 182 (as shown in **--dump-dies** output).
209 (as shown in **--dump-dies** output) and the name of the
234 (as shown in **--dump-dies** output) and the name of the
270 (as shown in **--dump-dies** output).
306 (as shown in **--dump-dies** output) or symbol.
307 - `value`: A valid type string (as shown in **--symtypes**) output)
|
| /linux/Documentation/pcmcia/ |
| H A D | driver.rst | 9 runtime as shown below::
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-event_source-devices-caps | 21 maximum number of counters which can be shown in the u64 counters
|
| H A D | sysfs-class-rc | 28 Enabled protocols are shown in [] brackets.
89 The enabled wakeup protocol is shown in [] brackets.
|
| /linux/Documentation/sound/designs/ |
| H A D | procfile.rst | 110 shown also when the invalid H/W pointer is detected at the
197 ports. The connection status and the running status are shown
224 - set-up of PCM, shown in hw_parms, sw_params, and status in the PCM
|
| /linux/Documentation/ABI/removed/ |
| H A D | sysfs-selinux-checkreqprot | 8 March 2023, the original deprecation notice is shown below.
|
| H A D | sysfs-selinux-disable | 8 in March 2023, the original deprecation notice is shown below.
|
| /linux/Documentation/accounting/ |
| H A D | cgroupstats.rst | 26 has been developed, the sample output of the utility is shown below::
|
| /linux/drivers/greybus/ |
| H A D | Kconfig | 9 ARA project, a module phone system, but has shown up in other
|
| /linux/Documentation/driver-api/cxl/linux/example-configurations/ |
| H A D | multi-interleave.rst | 144 which has the same interleave configuration as :code:`region0` (shown later).
147 which has the same interleave configuration as :code:`region0` (shown later).
|
| /linux/tools/memory-model/Documentation/ |
| H A D | recipes.txt | 221 the desired MP ordering. The general approach is shown below:
252 pointers. The general approach is shown below:
280 (address dependency, as shown above), the value written by a later store
297 to understand their use cases. The general approach is shown below:
385 The A/D pairing from the ring-buffer use case shown earlier also
499 values of 0, but providing both full barriers as shown above prevents
|
| /linux/Documentation/leds/ |
| H A D | ledtrig-usbport.rst | 32 This trigger can be activated from user space on led class devices as shown
|
| H A D | ledtrig-oneshot.rst | 20 The trigger can be activated from user space on led class devices as shown
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | selection-api-intro.rst | 21 and the cropping target is a part of an image to be shown on a display.
|
| /linux/Documentation/admin-guide/media/ |
| H A D | usb-cardlist.rst | 35 some of the drivers have sub-drivers, not shown at this table.
38 as shown at :doc:`gspca card list <gspca-cardlist>`.
|
| /linux/Documentation/filesystems/ |
| H A D | hfsplus.rst | 18 Specifies the creator/type values as shown by the MacOS finder
|
| /linux/Documentation/devicetree/bindings/sound/ |
| H A D | rt5663.txt | 32 R channel accordingly. Example is shown as following.
|
| /linux/Documentation/admin-guide/ |
| H A D | svga.rst | 84 case your chipset has been detected, some chipset-specific modes are shown as
104 modes are not listed at all and the modes revealed by ``scan`` are shown before
113 by entering its mode directly if you know it even if it isn't shown on the menu.
125 0x0100. All VESA modes should be autodetected and shown on the menu.
|
| /linux/Documentation/userspace-api/media/ |
| H A D | intro.rst | 12 A typical media device hardware is shown at :ref:`typical_media_device`.
|
| /linux/Documentation/admin-guide/auxdisplay/ |
| H A D | cfag12864b.rst | 49 The common wiring is done to the parallel port as shown::
|