| /Linux-v5.10/tools/memory-model/litmus-tests/ |
| 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()
|
| D | README | 28 variable by a different process? This litmus test is forbidden
136 The second is forbidden because smp_store_release() is
|
| /Linux-v5.10/Documentation/devicetree/bindings/interrupt-controller/ |
| D | ti,omap4-wugen-mpu | 21 are explicitly forbidden.
|
| D | nvidia,tegra20-ictlr.txt | 28 are explicitly forbidden.
|
| /Linux-v5.10/Documentation/devicetree/bindings/media/xilinx/ |
| D | xlnx,v-tpg.txt | 34 synthesized with two ports and forbidden when synthesized with one port.
|
| /Linux-v5.10/Documentation/driver-api/ |
| D | frame-buffer.rst | 25 importance for fb_monospecs. This allowed for forbidden things such as
|
| /Linux-v5.10/arch/x86/mm/pat/ |
| D | set_memory.c | 530 pgprotval_t forbidden, res; in static_protections() local
545 forbidden = res; in static_protections()
556 forbidden |= res; in static_protections()
562 forbidden |= res; in static_protections()
566 forbidden |= res; in static_protections()
568 return __pgprot(pgprot_val(prot) & ~forbidden); in static_protections()
|
| /Linux-v5.10/Documentation/arm64/ |
| D | tagged-pointers.rst | 45 forbidden, and using a non-zero address tag for sp is strongly
|
| /Linux-v5.10/tools/memory-model/ |
| D | README | 195 Specifies what reorderings are forbidden by memory references,
198 More formally, this file specifies what executions are forbidden
|
| /Linux-v5.10/drivers/misc/mei/ |
| D | main.c | 431 bool forbidden = dev->override_fixed_address ? in mei_ioctl_connect_client() local
433 if (forbidden) { in mei_ioctl_connect_client()
|
| /Linux-v5.10/drivers/media/radio/ |
| D | radio-wl1273.c | 46 u8 forbidden; member
695 dev_dbg(dev, "Forbidden modes: 0x%02x\n", radio->forbidden); in wl1273_fm_set_mode()
698 if (mode & radio->forbidden) { in wl1273_fm_set_mode()
|
| /Linux-v5.10/Documentation/devicetree/bindings/clock/ |
| D | clock-bindings.txt | 167 a shared clock is forbidden.
|
| /Linux-v5.10/Documentation/driver-api/gpio/ |
| D | consumer.rst | 163 It is strictly forbidden to use a descriptor after calling these functions.
456 Freeing a GPIO obtained by one API with the other API is forbidden and an
|
| /Linux-v5.10/Documentation/RCU/Design/Memory-Ordering/ |
| D | Tree-RCU-Memory-Ordering.rst | 458 Due to energy-efficiency considerations, RCU is forbidden from
481 RCU is also forbidden from disturbing offline CPUs, which might well be
|
| /Linux-v5.10/Documentation/driver-api/serial/ |
| D | tty.rst | 121 The driver is forbidden from calling this directly
|
| /Linux-v5.10/Documentation/networking/ |
| D | filter.rst | 1180 on these pointers is forbidden.
1187 Arithmetic on these pointers is forbidden.
1193 skb->data + headlen; arithmetic forbidden.
1202 Arithmetic on these pointers is forbidden.
|
| /Linux-v5.10/Documentation/admin-guide/cifs/ |
| 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
565 characters forbidden in typical CIFS filenames, without
|
| /Linux-v5.10/Documentation/admin-guide/device-mapper/ |
| D | thin-provisioning.rst | 95 device when reloading is not forbidden at the moment, things will go
|
| /Linux-v5.10/tools/memory-model/Documentation/ |
| D | explanation.txt | 1665 a forbidden cycle. Thus the "rcu" axiom rules out this violation of
1703 forbidden cycle, violating the "rcu" axiom. Hence the outcome is not
1741 L2 ->rcu-link U0. However this cycle is not forbidden, because the
2256 something the compiler is forbidden to do. Augmenting a store with a
|
| /Linux-v5.10/Documentation/filesystems/ |
| D | fscrypt.rst | 1112 read(), write(), mmap(), fallocate(), and ioctl(), are also forbidden.
1133 Except for those special files, it is forbidden to have unencrypted
|
| /Linux-v5.10/Documentation/power/ |
| D | runtime_pm.rst | 167 (1) The callbacks are mutually exclusive (e.g. it is forbidden to execute
|
| D | pci.rst | 321 unsigned int no_d1d2:1; /* D1 and D2 are forbidden */
|
| /Linux-v5.10/Documentation/driver-api/media/drivers/ |
| D | cx2341x-devel.rst | 1221 - '0000' forbidden
|
| /Linux-v5.10/Documentation/RCU/Design/Requirements/ |
| D | Requirements.rst | 1094 | These are forbidden within Linux-kernel RCU read-side critical |
1153 it is absolutely forbidden to update a semaphore that has just been
|
| /Linux-v5.10/Documentation/admin-guide/laptops/ |
| D | thinkpad-acpi.rst | 1323 is out-of-bounds, and EPERM if it is forbidden. They may also return
|
