| /openbmc/linux/Documentation/mm/ |
| H A D | transhuge.rst | 59 pmd_offset. It's trivial to make the code transparent hugepage aware
64 hugepage aware.
72 Example to make mremap.c transparent hugepage aware with a one liner
86 Locking in hugepage aware code
89 We want as much code as possible hugepage aware, as calling
92 To make pagetable walks huge pmd aware, all you need to do is to call
|
| /openbmc/linux/Documentation/driver-api/usb/ |
| H A D | dma.rst | 14 the 2.4 (and earlier) kernels, or they can now be DMA-aware.
16 DMA-aware usb drivers:
18 - New calls enable DMA-aware drivers, letting them allocate dma buffers and
25 - "usbcore" will map this DMA address, if a DMA-aware driver didn't do
|
| /openbmc/linux/tools/testing/selftests/kvm/aarch64/ |
| H A D | debug-exceptions.c | 183 /* Setup a context-aware breakpoint for Linked Context ID Match */ in install_wp_ctx()
189 /* Setup a linked watchpoint (linked to the context-aware breakpoint) */ in install_wp_ctx()
204 /* Setup a context-aware breakpoint for Linked Context ID Match */ in install_hw_bp_ctx()
212 * to the context-aware breakpoint. in install_hw_bp_ctx()
534 * context-aware breakpoint# with the given ID_AA64DFR0_EL1 configuration.
548 /* Number of context aware breakpoints */ in test_guest_debug_exceptions_all()
554 /* Number of normal (non-context aware) breakpoints */ in test_guest_debug_exceptions_all()
557 /* Lowest context aware breakpoint number */ in test_guest_debug_exceptions_all()
|
| /openbmc/linux/tools/testing/selftests/drivers/net/mlxsw/ |
| H A D | vxlan.sh | 116 log_test "vxlan device with a vlan-aware bridge"
873 log_test "vlan-aware - enslavement to vlan-aware bridge"
882 log_test "vlan-aware - two vnis mapped to the same vlan"
896 log_test "vlan-aware - failed enslavement to vlan-aware bridge"
902 # (i.e., different TTL) are enslaved to the same VLAN-aware bridge,
917 log_test "vlan-aware - failed enslavement to bridge due to conflict"
929 # Create a simple setup with two VxLAN devices and a single VLAN-aware
974 log_info "vxlan entry offload indication - vlan-aware"
1172 log_info "offload indication - replay & cleanup - vlan aware"
|
| H A D | extack.sh | 125 # Test with VLAN-aware bridge.
163 # Only one VLAN-aware bridge is supported, so this should fail with
169 log_test "extack - multiple VLAN-aware bridges creation"
|
| /openbmc/linux/Documentation/mm/damon/ |
| H A D | index.rst | 19 access-aware fashion. Because the features are also exposed to the user space,
26 feature, DAMON users in both kernel and user spaces can do access-aware system
|
| H A D | design.rst | 17 and access-aware system operations on top of the operations set layer, and
226 One common purpose of data access monitoring is access-aware system efficiency
406 The programming interface for kernel space data access-aware applications.
409 access-aware applications using DAMON's core features. For this, DAMON exposes
422 for general purpose DAMON control and special purpose data access-aware system
424 user space. The user space can build their efficient data access-aware
455 Special-Purpose Access-aware Kernel Modules
461 in runtime. For each special-purpose system-wide data access-aware system
|
| /openbmc/linux/Documentation/admin-guide/mm/ |
| H A D | shrinker_debugfs.rst | 59 If the shrinker is not memcg-aware or CONFIG_MEMCG is off, 0 is printed
60 as cgroup inode id. If the shrinker is not numa-aware, 0's are printed
112 For a non-memcg-aware shrinker or on a system with no memory
|
| /openbmc/linux/Documentation/scheduler/ |
| H A D | sched-capacity.rst | 2 Capacity Aware Scheduling
132 Capacity aware scheduling requires an expression of a task's requirements with
247 This means that while the capacity aware scheduling criteria will be written
251 3. Capacity aware scheduling requirements
268 As stated in 2.2, capacity-aware scheduling requires a frequency-invariant task
276 when the kernel is aware of the switched-to frequency (also employed by
330 5. Capacity aware scheduling implementation
369 Wakeup CPU selection in CFS can be eclipsed by Energy Aware Scheduling
|
| /openbmc/u-boot/board/logicpd/omap3som/ |
| H A D | README | 20 afterwards) along with a Falcon Mode aware MLO and the FAT partition has
47 along with a Falcon Mode aware MLO written to the correct locations for
|
| /openbmc/linux/include/asm-generic/ |
| H A D | rwonce.h | 5 * READ_ONCE and WRITE_ONCE, but only when the compiler is aware of some
6 * particular ordering. One way to make the compiler aware of ordering is to
|
| /openbmc/linux/arch/arm/mach-sa1100/include/mach/ |
| H A D | irqs.h | 86 * Neponset, SA1111 and UCB1x00 are sparse IRQ aware, so can dynamically
89 * LoCoMo has 4 additional IRQs, but is not sparse IRQ aware, and so has
|
| /openbmc/linux/Documentation/devicetree/bindings/arm/ |
| H A D | secure.txt | 5 kernel) are not TrustZone aware and run entirely in either the Normal
7 TrustZone aware and need to be able to determine whether devices are
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | MirOS | 42 property of third parties, if you were not aware of the fact, act ap‐
43 propriately as soon as you become aware of that problem, seek an ami‐
|
| /openbmc/linux/drivers/gpu/drm/ |
| H A D | drm_self_refresh_helper.c | 31 * &drm_connector_state.self_refresh_aware to true at runtime if it is SR-aware
47 * connectors must be SR aware and all will enter/exit SR mode at the same time.
49 * If the crtc and connector are SR aware, but the panel connected does not
|
| /openbmc/linux/Documentation/timers/ |
| H A D | timers-howto.rst | 60 quirks you should be aware of.
71 it is something to be aware of.
|
| /openbmc/linux/Documentation/admin-guide/pm/ |
| H A D | intel_uncore_frequency_scaling.rst | 62 SoCs with TPMI (Topology Aware Register and PM Capsule Interface)
76 SoCs with the support of TPMI (Topology Aware Register and PM Capsule
|
| /openbmc/linux/include/linux/ |
| H A D | shrinker.h | 18 /* current node being shrunk (for NUMA aware shrinkers) */
35 /* current memcg being shrunk (for memcg aware shrinkers) */
|
| /openbmc/linux/fs/zonefs/ |
| H A D | Kconfig | 9 device (e.g. host-managed or host-aware SMR disk drives) as files.
|
| /openbmc/linux/Documentation/ABI/stable/ |
| H A D | sysfs-block | 162 segment. For a zoned block device, either host-aware or
388 "host-managed" or "host-aware"), the sum of zones belonging to
427 "host-managed" or "host-aware"), the sum of zones belonging to
507 block device ("host-aware" or "host-managed" zone model). For
691 "host-aware"). This value is always 0 for regular block devices.
701 devices and "host-aware" or "host-managed" for zoned block
702 devices. The characteristics of host-aware and host-managed
|
| /openbmc/docs/designs/mctp/ |
| H A D | mctp.md | 45 stack needing to be aware of the hardware implementation. These higher levels
46 only need to be aware that they are communicating with a certain entity, defined
|
| /openbmc/qemu/docs/devel/ |
| H A D | secure-coding-practices.rst | 5 be aware of so that they can develop safe code and audit existing code
18 it's critical to be aware of common classes of security bugs.
|
| /openbmc/linux/Documentation/locking/ |
| H A D | futex-requeue-pi.rst | 53 In order to support PI-aware pthread_condvar's, the kernel needs to
106 to be requeued to a PI-aware futex. The implementation is the
|
| /openbmc/linux/include/linux/mailbox/ |
| H A D | zynqmp-ipi-message.h | 13 * Client is supposed to be aware of this.
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-daemons/tftp-hpa/files/ |
| H A D | tftp-xinetd | 4 # workstations, download configuration files to network-aware printers, \
|