| /openbmc/linux/Documentation/ |
| H A D | memory-barriers.txt | 520 Note that these are the _minimum_ guarantees. Different architectures may give
2548 between multiple architectures and bus implementations, the kernel offers a
2623 architectures (notably x86). The port number of the peripheral being
2626 Since many CPU architectures ultimately access these peripherals via an
2634 returning. This is not guaranteed by all architectures and is therefore
2651 architectures.
2865 are -not- optional in the above example, as there are architectures
2867 On such architectures, READ_ONCE() and WRITE_ONCE() do whatever is
|
| /openbmc/linux/tools/memory-model/Documentation/ |
| H A D | explanation.txt | 91 Different architectures have differing memory models, and the Linux
92 kernel supports a variety of architectures. The LKMM has to be fairly
94 architectures also has to be allowed by the LKMM.
215 performance optimizations. On ARM and PowerPC architectures, for
250 x86, Alpha, and other architectures. However, it is different in
813 most architectures, the local caches process stores in
1094 To be fair about it, all Linux-supported architectures do execute
1129 However, none of the architectures supported by the Linux kernel do
1202 incoming stores in FIFO order. By contrast, other architectures
2160 architectures supported by the Linux kernel, albeit for various
|
| /openbmc/qemu/docs/ |
| H A D | nvdimm.txt | 86 architectures, so the broken memory-backend-file can work again.
|
| /openbmc/openbmc/meta-ibm/meta-palmetto/conf/templates/default/ |
| H A D | local.conf.sample | 113 # you can build the SDK packages for architectures other than the machine you are
|
| /openbmc/openbmc/meta-yadro/meta-nicole/conf/templates/default/ |
| H A D | local.conf.sample | 93 # you can build the SDK packages for architectures other than the machine you are
|
| /openbmc/openbmc/meta-ufispace/meta-ncplite/conf/templates/default/ |
| H A D | local.conf.sample | 113 # you can build the SDK packages for architectures other than the machine you are
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/documentation/corstone1000/ |
| H A D | software-architecture.rst | 238 .. _FF-M: https://developer.arm.com/architectures/Firmware%20Framework%20for%20M-Profile
|
| /openbmc/linux/Documentation/devicetree/bindings/arm/ |
| H A D | cpus.yaml | 48 On uniprocessor ARM architectures previous to v7
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | dax.rst | 290 The DAX code does not work correctly on architectures which have virtually
|
| /openbmc/linux/Documentation/livepatch/ |
| H A D | module-elf-format.rst | 25 livepatch more easily portable to other architectures and reduce the amount
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | this_cpu_ops.rst | 220 this_cpu ops are interrupt safe. Some architectures do not support
|
| /openbmc/linux/Documentation/arch/x86/ |
| H A D | exception-tables.rst | 354 This is not just a boot time optimization, some architectures require this
|
| /openbmc/linux/Documentation/bpf/ |
| H A D | ringbuf.rst | 158 wrap around on 32-bit architectures, that's not a problem):
|
| /openbmc/linux/Documentation/admin-guide/mm/ |
| H A D | ksm.rst | 122 the performance on architectures with coloured zero pages,
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | devices.rst | 186 card on those architectures for which the frame buffer devices
|
| H A D | ras.rst | 249 Some architectures have ECC detectors for L1, L2 and L3 caches,
985 On older Intel architectures, the memory controller was part of the North
987 newer Intel architectures integrated an enhanced version of the memory
|
| /openbmc/linux/Documentation/admin-guide/hw-vuln/ |
| H A D | core-scheduling.rst | 146 too late on some architectures, but this has not been observed in the case of
|
| /openbmc/linux/Documentation/admin-guide/sysctl/ |
| H A D | vm.rst | 450 This is only active on architectures/platforms with advanced machine
535 resulting from mmap allocations on architectures which support
549 compatibility mode on architectures which support tuning address
|
| /openbmc/u-boot/tools/buildman/ |
| H A D | README | 425 toolchains from kernel.org. First list the available architectures:
432 Available architectures: alpha am33_2.0 arm bfin cris crisv32 frv h8300
475 At the time of writing, U-Boot has these architectures:
1119 The <list of things to build> can include board names, architectures or the
|
| /openbmc/linux/Documentation/userspace-api/ |
| H A D | unshare.rst | 243 d) Registration of system call number for different architectures
|
| /openbmc/linux/Documentation/fb/ |
| H A D | fbcon.rst | 11 some even treat it as a toy. For other architectures, it is the only available
|
| /openbmc/linux/Documentation/userspace-api/ioctl/ |
| H A D | hdio.rst | 98 unsigned short, meaning that on most architectures, this
|
| /openbmc/openbmc/meta-hpe/meta-rl300-g11/conf/templates/default/ |
| H A D | local.conf.sample | 119 # you can build the SDK packages for architectures other than the machine you are
|
| /openbmc/openbmc/meta-hpe/meta-dl360-g11/conf/templates/default/ |
| H A D | local.conf.sample | 119 # you can build the SDK packages for architectures other than the machine you are
|
| /openbmc/openbmc/poky/meta-poky/conf/templates/default/ |
| H A D | local.conf.sample | 119 # you can build the SDK packages for architectures other than the machine you are
|