| /linux/Documentation/locking/ |
| H A D | preempt-locking.rst | 15 requires explicit additional locking for very few additional situations.
21 RULE #1: Per-CPU data structures need explicit protection
32 First, since the data is per-CPU, it may not have explicit SMP locking, but
132 in doubt, rely on locking or explicit preemption disabling.
|
| /linux/tools/memory-model/litmus-tests/ |
| H A D | LB+poonceonces.litmus | 7 * be prevented even with no explicit ordering?
|
| /linux/arch/arm64/boot/dts/amlogic/ |
| H A D | meson-g12a-fbx8am-realtek.dtso | 20 /* No explicit compatible for rtl8822cs sdio */
|
| /linux/net/netlabel/ |
| H A D | Kconfig | 12 NetLabel provides support for explicit network packet labeling
|
| /linux/ |
| H A D | COPYING | 10 With an explicit syscall exception, as stated at:
|
| /linux/Documentation/userspace-api/ |
| H A D | dma-buf-alloc-exchange.rst | 27 format and modifier (implicit or explicit).
332 ``DRM_FORMAT_MOD_LINEAR``, which is an explicit guarantee that the image
340 as the sole member of a modifier list to declare that explicit modifiers are
345 at all) to declare that explicit modifiers are not supported and must not be
350 that the underlying layout is implementation-defined and that an explicit
357 not been allocated with an explicit modifier
361 explicit. For example, if a user wishes to allocate a buffer for use between
363 user **must not** allocate the buffer with explicit modifiers and attempt to
369 to explicit modifiers. For example, if the buffer is allocated with
371 ``gbm_bo_get_modifier`` and then use this modifier as an explicit modifier token
|
| /linux/arch/arm/lib/ |
| H A D | clear_user.S | 43 it ne @ explicit IT needed for the label
|
| /linux/scripts/coccinelle/api/ |
| H A D | vma_pages.cocci | 3 /// Use vma_pages function on vma object instead of explicit computation.
|
| H A D | resource_size.cocci | 4 /// instead of explicit computation.
|
| /linux/Documentation/devicetree/bindings/power/reset/ |
| H A D | ltc2952-poweroff.txt | 19 until an explicit kill signal is received
|
| /linux/scripts/coccinelle/misc/ |
| H A D | boolconv.cocci | 5 //# explicit conversion is overly verbose and unneeded.
|
| /linux/Documentation/block/ |
| H A D | writeback_cache_control.rst | 28 set on an otherwise empty bio structure, which causes only an explicit cache
45 worry if the underlying devices need any explicit cache flushing and how
|
| /linux/Documentation/filesystems/ |
| H A D | zonefs.rst | 311 * explicit-open
336 "explicit-open" option
341 implicit open, explicit open or closed conditions. This potential limitation
346 To avoid these potential errors, the "explicit-open" mount option forces zones
350 "explicit-open" mount option will result in a zone close command being issued
368 state of other zones. When the *explicit-open* mount option is used, zonefs
373 zone files open for writing. When the "explicit-open" mount option is used,
374 this number can never exceed *max_wro_seq_files*. If the *explicit-open*
382 is explicitly open (which happens only if the *explicit-open* mount option is
389 *nr_active_seq_files*, regardless of the use of the *explicit-open* mount
|
| /linux/Documentation/userspace-api/media/dvb/ |
| H A D | fe-get-property.rst | 54 parameters used. If the actual parameters are needed, an explicit
|
| /linux/virt/kvm/ |
| H A D | Kconfig | 24 # put any explicit constraint on userspace ordering. They can also
|
| /linux/scripts/coccinelle/iterators/ |
| H A D | device_node_continue.cocci | 3 /// explicit put causes a double put.
|
| /linux/drivers/gpu/drm/lima/ |
| H A D | lima_gem.c | 263 bool write, bool explicit) in lima_gem_sync_bo() argument
272 if (explicit) in lima_gem_sync_bo()
|
| /linux/Documentation/ABI/obsolete/ |
| H A D | sysfs-gpio | 8 userspace. GPIOs are only made available to userspace by an explicit
|
| /linux/usr/ |
| H A D | gen_initramfs.sh | 33 <cpio_source> options so an explicit "-u 0 -g 0" is required
|
| /linux/Documentation/arch/arm/ |
| H A D | cluster-pm-race-avoidance.rst | 153 a) an explicit hardware power-up operation, resulting
189 The CPU remains in this state until an explicit policy decision
197 explicit policy decision
309 a) an explicit hardware power-up operation, resulting
398 a) an explicit hardware power-up operation,
|
| /linux/Documentation/driver-api/usb/ |
| H A D | anchors.rst | 31 An association of URBs to an anchor is made by an explicit
|
| /linux/tools/memory-model/Documentation/ |
| H A D | control-dependencies.txt | 22 from "a". This means that an explicit read barrier is required, for example
92 you must use explicit memory ordering, for example, smp_store_release():
103 Without explicit memory ordering, control-dependency-based ordering is
|
| /linux/Documentation/networking/devlink/ |
| H A D | index.rst | 10 Driver facing APIs are currently transitioning to allow more explicit
|
| /linux/Documentation/devicetree/bindings/powerpc/ |
| H A D | ibm,powerpc-cpu-features.txt | 122 If no bits are set, the hypervisor must have explicit/custom support for
141 If no bits are set, the operating system must have explicit/custom support
|
| /linux/drivers/block/ |
| H A D | zloop.c | 238 bool explicit) in zloop_open_closed_or_empty_zone() argument
242 if (explicit) { in zloop_open_closed_or_empty_zone()
275 struct zloop_zone *zone, bool explicit) in zloop_do_open_zone() argument
280 if (explicit) in zloop_do_open_zone()
286 return zloop_open_closed_or_empty_zone(zlo, zone, explicit); in zloop_do_open_zone()
|