Searched full:volatile (Results 1 – 25 of 107) sorted by relevance
12345
| /Documentation/process/ |
| D | volatile-considered-harmful.rst | 4 Why the "volatile" type class should not be used
7 C programmers have often taken volatile to mean that the variable could be
10 being used. In other words, they have been known to treat volatile types
11 as a sort of easy atomic variable, which they are not. The use of volatile in
14 The key point to understand with regard to volatile is that its purpose is
21 Like volatile, the kernel primitives which make concurrent access to data
24 need to use volatile as well. If volatile is still necessary, there is
26 code, volatile can only serve to slow things down.
45 If shared_data were declared volatile, the locking would still be
49 volatile. When dealing with shared data, proper locking makes volatile
[all …]
|
| /Documentation/translations/it_IT/process/ |
| D | volatile-considered-harmful.rst | 3 :Original: :ref:`Documentation/process/volatile-considered-harmful.rst <volatile_considered_harmful…
8 Perché la parola chiave "volatile" non dovrebbe essere usata
13 a volte saranno tentati dall'utilizzare *volatile* nel kernel per le
15 *volatile* come una variabile atomica di facile utilizzo, ma non è così.
16 L'uso di *volatile* nel kernel non è quasi mai corretto; questo documento ne
19 Il punto chiave da capire su *volatile* è che il suo scopo è quello di
27 Come *volatile*, le primitive del kernel che rendono sicuro l'accesso ai dati
30 non ci sarà bisogno di utilizzare *volatile*. Se vi sembra che *volatile* sia
32 In un pezzo di codice kernel scritto a dovere, *volatile* può solo servire a
52 Se il dato condiviso fosse stato dichiarato come *volatile*, la
[all …]
|
| /Documentation/block/ |
| D | writeback_cache_control.rst | 2 Explicit volatile write back cache control
8 Many storage devices, especially in the consumer market, come with volatile
10 operating system before data actually has hit the non-volatile storage. This
12 system needs to force data out to the non-volatile storage when it performs
24 the filesystem and will make sure the volatile cache of the storage device
26 guarantees that previously completed write requests are on non-volatile
38 signaled after the data has been committed to non-volatile storage.
52 For devices that do not support volatile write caches there is no driver
57 For devices with volatile write caches the driver needs to tell the block layer
|
| /Documentation/devicetree/bindings/pmem/ |
| D | pmem-region.txt | 35 - volatile; This property indicates that this region is actually
41 is backed by non-volatile memory.
48 * 0x5000 to 0x5fff that is backed by non-volatile memory.
57 * volatile (normal) memory.
63 volatile;
|
| /Documentation/devicetree/bindings/iio/potentiometer/ |
| D | microchip,mcp4531.yaml | 15 * volatile https://ww1.microchip.com/downloads/en/DeviceDoc/22096b.pdf
16 * non-volatile https://ww1.microchip.com/downloads/en/DeviceDoc/22107B.pdf
19 B = 3 (7-bit, volatile), 4 (7-bit, non-volatile),
20 5 (8-bit, volatile), 6 (8-bit, non-volatile),
|
| /Documentation/translations/zh_CN/process/ |
| D | volatile-considered-harmful.rst | 5 :Original: :ref:`Documentation/process/volatile-considered-harmful.rst
19 为什么不应该使用“volatile”类型
53 volatile —— 并且是有潜在危害的。
73 volatile。基本上，每一个访问函数调用它自己都是一个小的临界区域并且保证了按照
|
| /Documentation/translations/zh_TW/process/ |
| D | volatile-considered-harmful.rst | 7 :Original: :ref:`Documentation/process/volatile-considered-harmful.rst
22 爲什麼不應該使用“volatile”類型
56 volatile —— 並且是有潛在危害的。
76 volatile。基本上，每一個訪問函數調用它自己都是一個小的臨界區域並且保證了按照
|
| /Documentation/translations/zh_TW/arch/arm/ |
| D | kernel_user_helpers.txt | 136 int __kuser_cmpxchg(int32_t oldval, int32_t newval, volatile int32_t *ptr);
163 typedef int (__kuser_cmpxchg_t)(int oldval, int newval, volatile int *ptr);
166 int atomic_add(volatile int *ptr, int val)
230 volatile int64_t *ptr);
261 volatile int64_t *ptr);
264 int64_t atomic_add64(volatile int64_t *ptr, int64_t val)
|
| /Documentation/translations/zh_CN/arch/arm/ |
| D | kernel_user_helpers.txt | 136 int __kuser_cmpxchg(int32_t oldval, int32_t newval, volatile int32_t *ptr);
163 typedef int (__kuser_cmpxchg_t)(int oldval, int newval, volatile int *ptr);
166 int atomic_add(volatile int *ptr, int val)
230 volatile int64_t *ptr);
261 volatile int64_t *ptr);
264 int64_t atomic_add64(volatile int64_t *ptr, int64_t val)
|
| /Documentation/arch/powerpc/ |
| D | syscall64-abi.rst | 57 | r0 | Volatile | (System call number.) |
59 | r3 | Volatile | (Parameter 1, and return value.) |
61 | r4-r8 | Volatile | (Parameters 2-6.) |
63 | cr0 | Volatile | (cr0.SO is the return error condition.) |
75 | r0 | Volatile | (System call number.) |
77 | r3 | Volatile | (Parameter 1, and return value.) |
79 | r4-r8 | Volatile | (Parameters 2-6.) |
140 r0 Volatile
141 cr1, cr5-7 Volatile
142 lr Volatile
|
| /Documentation/arch/arm/ |
| D | kernel_user_helpers.rst | 123 int __kuser_cmpxchg(int32_t oldval, int32_t newval, volatile int32_t *ptr);
150 typedef int (__kuser_cmpxchg_t)(int oldval, int newval, volatile int *ptr);
153 int atomic_add(volatile int *ptr, int val)
215 volatile int64_t *ptr);
246 volatile int64_t *ptr);
249 int64_t atomic_add64(volatile int64_t *ptr, int64_t val)
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-nfit | 10 (RO) Serial number of the NVDIMM (non-volatile dual in-line
132 (RO) Sub-system vendor id of the NVDIMM non-volatile memory
141 (RO) Sub-system revision id of the NVDIMM non-volatile memory subsystem
142 controller, assigned by the non-volatile memory subsystem
151 (RO) Sub-system device id for the NVDIMM non-volatile memory
152 subsystem controller, assigned by the non-volatile memory
|
| /Documentation/translations/ja_JP/ |
| D | stable_api_nonsense.txt | 146 「引火性の高い」の原文は "volatile"。
147 volatile には「揮発性の」「爆発しやすい」という意味の他、「変わり
151 ある」ということを連想させる "volatile" という単語で表現している。
|
| /Documentation/driver-api/nvdimm/ |
| D | index.rst | 4 Non-Volatile Memory Device (NVDIMM)
|
| /Documentation/devicetree/bindings/nvmem/ |
| D | nvmem-provider.yaml | 7 title: NVMEM (Non Volatile Memory) Provider
|
| D | xlnx,zynqmp-nvmem.yaml | 7 title: Zynq UltraScale+ MPSoC Non Volatile Memory interface
|
| D | snvs-lpgpr.yaml | 7 title: Low Power General Purpose Register found in i.MX Secure Non-Volatile Storage
|
| D | nvmem-consumer.yaml | 7 title: NVMEM (Non Volatile Memory) Consumer
|
| /Documentation/devicetree/bindings/fuse/ |
| D | renesas,rcar-otp.yaml | 13 The E-FUSE is a type of non-volatile memory, which is accessible through the
|
| /Documentation/devicetree/bindings/iio/chemical/ |
| D | aosong,ags02ma.yaml | 10 AGS02MA is an TVOC (Total Volatile Organic Compounds) i2c sensor with default
|
| /Documentation/devicetree/bindings/nvmem/layouts/ |
| D | nvmem-layout.yaml | 7 title: NVMEM (Non Volatile Memory) layouts
|
| /Documentation/devicetree/bindings/crypto/ |
| D | fsl,sec-v4.0-mon.yaml | 8 title: Freescale Secure Non-Volatile Storage (SNVS)
47 Secure Non-Volatile Storage (SNVS) Low Power (LP) RTC Node
|
| /Documentation/devicetree/bindings/iio/dac/ |
| D | microchip,mcp4728.yaml | 15 Digital-to-Analog Converter with non-volatile
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | maxim,ds2760.yaml | 38 If not specified, the value stored in the non-volatile chip memory is used.
|
| /Documentation/networking/devlink/ |
| D | devlink-selftests.rst | 24 - Devices may have the firmware on non-volatile memory on the board, e.g.
|
12345