| /linux/tools/memory-model/litmus-tests/ |
| H A D | WRC+pooncerelease+fencermbonceonce+Once.litmus | 8 * a release and a read memory barrier, it should be forbidden. More
9 * specifically, this litmus test is forbidden because smp_store_release()
|
| H A D | README | 28 variable by a different process? This litmus test is forbidden
144 The second is forbidden because smp_store_release() is
|
| /linux/drivers/net/wireless/intel/iwlwifi/mei/ |
| H A D | iwl-mei.h | 315 void (*roaming_forbidden)(void *priv, bool forbidden);
|
| /linux/Documentation/devicetree/bindings/media/xilinx/ |
| H A D | xlnx,v-tpg.txt | 34 synthesized with two ports and forbidden when synthesized with one port.
|
| /linux/Documentation/driver-api/ |
| H A D | frame-buffer.rst | 25 importance for fb_monospecs. This allowed for forbidden things such as
|
| /linux/arch/x86/mm/pat/ |
| H A D | set_memory.c | 626 pgprotval_t forbidden, res; in static_protections() local
641 forbidden = res; in static_protections()
652 forbidden |= res; in static_protections()
658 forbidden |= res; in static_protections()
662 forbidden |= res; in static_protections()
664 return __pgprot(pgprot_val(prot) & ~forbidden); in static_protections()
|
| /linux/tools/memory-model/ |
| H A D | README | 178 Specifies what reorderings are forbidden by memory references,
181 More formally, this file specifies what executions are forbidden
|
| /linux/Documentation/arch/arm64/ |
| H A D | tagged-pointers.rst | 45 forbidden, and using a non-zero address tag for sp is strongly
|
| /linux/mm/ |
| H A D | madvise.c | 873 unsigned int forbidden = VM_PFNMAP; in madvise_dontneed_free_valid_vma() local
876 forbidden |= VM_LOCKED; in madvise_dontneed_free_valid_vma()
878 return !(vma->vm_flags & forbidden); in madvise_dontneed_free_valid_vma()
|
| /linux/drivers/misc/mei/ |
| H A D | main.c | 439 bool forbidden = dev->override_fixed_address ? in mei_ioctl_connect_client() local
441 if (forbidden) { in mei_ioctl_connect_client()
|
| /linux/tools/memory-model/Documentation/ |
| H A D | glossary.txt | 84 are all equal to zero is forbidden by LKMM.
|
| H A D | explanation.txt | 1748 a forbidden cycle. Thus the "rcu" axiom rules out this violation of
1786 forbidden cycle, violating the "rcu" axiom. Hence the outcome is not
1824 L2 ->rcu-link U0. However this cycle is not forbidden, because the
2500 something the compiler is forbidden to do. Augmenting a store with a
|
| /linux/Documentation/driver-api/gpio/ |
| H A D | consumer.rst | 169 It is strictly forbidden to use a descriptor after calling these functions.
469 Freeing a GPIO obtained by one API with the other API is forbidden and an
|
| /linux/drivers/net/wireless/intel/iwlwifi/mvm/ |
| H A D | ops.c | 1129 static void iwl_mvm_mei_roaming_forbidden(void *priv, bool forbidden) in iwl_mvm_mei_roaming_forbidden() argument
1136 iwl_mvm_send_roaming_forbidden_event(mvm, mvm->csme_vif, forbidden); in iwl_mvm_mei_roaming_forbidden()
|
| /linux/Documentation/RCU/Design/Memory-Ordering/ |
| H A D | Tree-RCU-Memory-Ordering.rst | 482 Due to energy-efficiency considerations, RCU is forbidden from
505 RCU is also forbidden from disturbing offline CPUs, which might well be
|
| /linux/Documentation/admin-guide/cifs/ |
| H A D | usage.rst | 193 would be forbidden. Samba 3.0.6 server or later includes the ability to create
266 would be forbidden for Windows/CIFS semantics) as long as the server is
567 characters forbidden in typical CIFS filenames, without
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | thin-provisioning.rst | 95 device when reloading is not forbidden at the moment, things will go
|
| /linux/Documentation/filesystems/ |
| H A D | idmappings.rst | 306 idmapset indicates a userspace id. So the following translations are forbidden::
|
| /linux/Documentation/driver-api/media/drivers/ |
| H A D | cx2341x-devel.rst | 1221 - '0000' forbidden
|