| /linux/tools/testing/selftests/powerpc/tm/ |
| H A D | tm-poison.c | 30 uint64_t poison = 0xdeadbeefc0dec0fe; in tm_poison_test() local
57 : : [poison] "r" (poison) : ); in tm_poison_test()
|
| H A D | Makefile | 8 tm-signal-context-force-tm tm-poison tm-signal-pagefault
29 $(OUTPUT)/tm-poison: CFLAGS += -m64
|
| H A D | .gitignore | 22 tm-poison
|
| /linux/Documentation/translations/zh_CN/mm/ |
| H A D | hwpoison.rst | 42 该代码由mm/memory-failure.c中的高级处理程序、一个新的页面poison位和虚拟机中的
43 各种检查组成，用来处理poison的页面。
133 page-types -p `pidof usemem` --hwpoison # poison its pages
136 当指定时，只有在((page_flags & mask) == value)的情况下才会poison页面。
|
| /linux/kernel/ |
| H A D | kstack_erase.c | 76 unsigned long poison) in __stackleak_poison() argument
79 *(unsigned long *)erase_low = poison; in __stackleak_poison()
|
| /linux/tools/mm/ |
| H A D | slabinfo.c | 35 int order, poison, reclaim_account, red_zone; member
93 int poison; variable
582 page_size << s->order, s->partial, onoff(s->poison), in report()
638 if (s->poison) in slabcache()
687 poison = 1; in debug_opt_scan()
701 if (poison) in debug_opt_scan()
703 poison = 1; in debug_opt_scan()
770 if (poison && !s->poison) { in slab_debug()
772 set_obj(s, "poison", in slab_debug()
[all...] |
| /linux/arch/arm64/kernel/ |
| H A D | vdso.c | 205 __le32 poison = cpu_to_le32(COMPAT_SIGPAGE_POISON_WORD); in aarch32_alloc_sigpage() local
212 memset32(sigpage, (__force u32)poison, PAGE_SIZE / sizeof(poison)); in aarch32_alloc_sigpage()
|
| /linux/arch/x86/kernel/cpu/sgx/ |
| H A D | main.c | 81 if (page->poison) { in __sgx_sanitize_pages()
615 if (page->poison) in sgx_free_epc_page()
650 section->pages[i].poison = 0; in sgx_setup_epc_section()
711 if (page->poison) in arch_memory_failure()
714 page->poison = 1; in arch_memory_failure()
|
| /linux/tools/testing/memblock/ |
| H A D | internal.h | 27 int poison, const char *s) in free_reserved_area()
28 free_reserved_area(void * start,void * end,int poison,const char * s) free_reserved_area() argument
|
| /linux/tools/lib/bpf/ |
| H A D | hashmap.c | 16 #pragma GCC poison u8 u16 u32 u64 s8 s16 s32 s64
19 #pragma GCC poison reallocarray
|
| H A D | relo_core.h | 53 bool poison; member
|
| H A D | libbpf_internal.h | 38 #pragma GCC poison u8 u16 u32 u64 s8 s16 s32 s64
41 #pragma GCC poison reallocarray
|
| H A D | libbpf_utils.c | 25 #pragma GCC poison u8 u16 u32 u64 s8 s16 s32 s64
|
| /linux/tools/perf/util/ |
| H A D | hashmap.c | 16 #pragma GCC poison u8 u16 u32 u64 s8 s16 s32 s64
19 #pragma GCC poison reallocarray
|
| /linux/tools/testing/selftests/bpf/ |
| H A D | bpf_util.h | 90 #pragma GCC poison gettid
|
| /linux/Documentation/mm/ |
| H A D | hwpoison.rst | 42 a new page poison bit and various checks in the VM to handle poisoned
148 page-types -p `pidof usemem` --hwpoison # poison its pages
151 When specified, only poison pages if ((page_flags & mask) ==
|
| /linux/mm/ |
| H A D | Kconfig.debug | 29 fill the pages with poison patterns after free_pages() and verify
150 Fill the pages with poison patterns after free_pages() and verify
156 Note that "poison" here is not the same thing as the "HWPoison"
160 checking the poison pattern on alloc, you can boot the kernel with
|
| /linux/Documentation/admin-guide/mm/ |
| H A D | slab.rst | 70 example, here's how you can poison the dentry cache as well as all kmalloc
111 P poison
263 typically contain poison values. Any non-poison value shows a
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-nfit | 183 the address (cache line) where the MCE happened to the poison
190 insert the address of the memory error into the poison and
|
| H A D | sysfs-bus-cxl | 575 memdev driver retrieves the poison list from the device. The
577 in poison if accessed, and the source of the poison. This
|
| H A D | sysfs-kernel-slab | 378 What: /sys/kernel/slab/<cache>/poison
384 The poison file specifies whether objects should be poisoned
|
| /linux/Documentation/admin-guide/hw-vuln/ |
| H A D | spectre.rst | 118 One other variant 2 attack vector is for the attacker to poison the
121 imbalanced subroutine call instructions might "poison" entries in the
134 Yet another variant 2 attack vector is for the attacker to poison the
203 A spectre variant 2 attacker can :ref:`poison <poison_btb>` the branch
284 For Spectre variant 2 attacks, rogue guests can :ref:`poison
|
| /linux/arch/x86/kernel/ |
| H A D | alternative.c | 1155 u32 poison = gen_endbr_poison(); in poison_endbr() local
1166 DUMP_BYTES(ENDBR, ((u8*)&poison), 4, "%px: repl: ", addr); in poison_endbr()
1167 text_poke_early(addr, &poison, 4); in poison_endbr()
|
| /linux/include/linux/ |
| H A D | mm.h | 3690 int poison, const char *s);
3717 static inline unsigned long free_initmem_default(int poison) in free_initmem_default() argument
3722 poison, "unused kernel image (initmem)"); in free_initmem_default()
|
| /linux/drivers/gpu/drm/amd/amdkfd/ |
| H A D | kfd_priv.h | 1011 atomic_t poison; member
|