| /linux/lib/ |
| H A D | Kconfig.kfence | 66 performance has carefully been evaluated with this option.
68 Using static keys comes with trade-offs that need to be carefully
|
| /linux/arch/mips/include/asm/ |
| H A D | edac.h | 17 * Very carefully read and write to memory atomically in edac_atomic_scrub()
|
| /linux/drivers/net/ethernet/sfc/siena/ |
| H A D | efx.h | 95 * efx_filter_remove_id_safe - remove a filter by ID, carefully
111 * efx_filter_get_filter_safe - retrieve a filter by ID, carefully
|
| /linux/arch/powerpc/include/asm/ |
| H A D | edac.h | 26 /* Very carefully read and write to memory atomically in edac_atomic_scrub()
|
| /linux/arch/arm/include/asm/ |
| H A D | edac.h | 23 /* Very carefully read and write to memory atomically in edac_atomic_scrub()
|
| H A D | checksum.h | 88 tst %2, #15 @ do this carefully \n\ in ip_fast_csum()
|
| /linux/drivers/md/dm-vdo/indexer/ |
| H A D | sparse-cache.h | 21 * not change between the carefully coordinated calls to uds_update_sparse_cache() from the zone
|
| /linux/Documentation/arch/riscv/ |
| H A D | boot.rst | 139 those macros before the final virtual mapping is installed must be carefully
157 That code must be very carefully compiled as:
|
| /linux/include/linux/ |
| H A D | circ_buf.h | 23 /* Return count up to the end of the buffer. Carefully avoid
|
| /linux/arch/arm/mach-pxa/ |
| H A D | mfp-pxa3xx.c | 42 * NOTE: the last 3 bits DxS are write-1-to-clear so carefully in pxa3xx_mfp_resume()
|
| /linux/drivers/gpu/drm/i915/gt/ |
| H A D | intel_timeline_types.h | 61 * held to the request, users must carefully acquire a reference to
|
| /linux/Documentation/admin-guide/media/ |
| H A D | cafe_ccic.rst | 57 ten. That number was carefully picked out of a hat and should not be
|
| /linux/Documentation/kbuild/ |
| H A D | Kconfig.recursion-issue-02 | 19 # core requirements are not carefully synced, as drivers evolve features
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | vidioc-subscribe-event.rst | 105 Think carefully when you set this flag so you won't get into
|
| /linux/Documentation/virt/kvm/ |
| H A D | vcpu-requests.rst | 205 This solution also requires memory barriers to be placed carefully in both
230 compiler doesn't interfere with ``vcpu->mode``'s carefully planned
|
| /linux/arch/arc/lib/ |
| H A D | memset-archs.S | 13 * line lengths (32B and 128B) you should rewrite code carefully checking
|
| /linux/kernel/rcu/ |
| H A D | rcu_segcblist.c | 164 * Therefore, ->len transitions from 1->0 and 0->1 have to be carefully
172 * be handled carefully. Without the full memory barriers after the ->len
193 * 1->0, which is one of the transitions that must be handled carefully.
|
| /linux/arch/sh/boards/mach-x3proto/ |
| H A D | ilsel.c | 36 * to the interrupt level, the level map is carefully managed to ensure a
|
| /linux/Documentation/arch/arm/ |
| H A D | porting.rst | 39 The initial part of the kernel is carefully coded to be position
|
| /linux/fs/jfs/ |
| H A D | jfs_types.h | 23 * Don't change these without carefully considering the impact on the
|
| /linux/Documentation/dev-tools/kunit/api/ |
| H A D | functionredirection.rst | 23 devices, the filesystem, or some hardware state. Tests need to either carefully
|
| /linux/Documentation/bpf/ |
| H A D | prog_flow_dissector.rst | 101 can be called for both cases and would have to be written carefully to
|
| /linux/Documentation/locking/ |
| H A D | pi-futex.rst | 68 even if all critical sections are coded carefully to be deterministic
|
| /linux/arch/powerpc/kernel/ |
| H A D | pci-hotplug.c | 133 * it carefully tries to add only new devices. (And that
|
| /linux/Documentation/filesystems/nfs/ |
| H A D | nfsd-io-modes.rst | 100 As always, your mileage may vary and so it is important to carefully
|