| /linux/drivers/target/ |
| H A D | target_core_alua.c | 33 int *primary, int explicit);
35 struct se_lun *lun, int explicit, int offline);
728 core_alua_check_transition(int state, int valid, int *primary, int explicit) in core_alua_check_transition() argument
770 if (!(valid & ALUA_T_SUP) || explicit) in core_alua_check_transition()
979 int explicit) in core_alua_do_transition_tg_pt() argument
990 if (explicit && new_state == ALUA_ACCESS_STATE_TRANSITION) { in core_alua_do_transition_tg_pt()
1001 tg_pt_gp->tg_pt_gp_alua_access_status = (explicit) ? in core_alua_do_transition_tg_pt()
1040 " from primary access state %s to %s\n", (explicit) ? "explicit" : in core_alua_do_transition_tg_pt()
1058 int explicit) in core_alua_do_port_transition() argument
1071 explicit) != 0) in core_alua_do_port_transition()
[all …]
|
| /linux/Documentation/devicetree/bindings/sound/ |
| H A D | tdm-slot.txt | 18 to specify an explicit mapping of the channels and the slots. If it's absent
26 The explicit masks are given as array of integers, where the first
|
| /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/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/include/trace/events/ |
| H A D | block.h | 445 TP_PROTO(struct request_queue *q, unsigned int depth, bool explicit),
447 TP_ARGS(q, depth, explicit),
473 TP_PROTO(struct request_queue *q, unsigned int depth, bool explicit),
475 TP_ARGS(q, depth, explicit)
|
| /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/devicetree/bindings/mtd/partitions/ |
| H A D | brcm,bcm963xx-imagetag.txt | 6 needs to be used with an explicit firmware partition.
|
| /linux/arch/arm/lib/ |
| H A D | clear_user.S | 43 it ne @ explicit IT needed for the label
|
| /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/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/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/userspace-api/media/dvb/ |
| H A D | fe-get-property.rst | 54 parameters used. If the actual parameters are needed, an explicit
|
| /linux/scripts/coccinelle/iterators/ |
| H A D | device_node_continue.cocci | 3 /// explicit put causes a double put.
|
| /linux/virt/kvm/ |
| H A D | Kconfig | 23 # put any explicit constraint on userspace ordering. They can also
|
| /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/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/ABI/testing/ |
| H A D | sysfs-firmware-gsmi | 6 that provides callback functionality via explicit SMI
|
| /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
|