Lines Matching full:barrier

55 	 * functions as a barrier), but on which the hypervisor (KVM/Qemu) has  in setup_barrier_nospec()
56 	 * not been updated, we would like to enable the barrier. Dropping the  in setup_barrier_nospec()
58 	 * we potentially enable the barrier on systems where the host firmware  in setup_barrier_nospec()
191 			seq_buf_printf(&s, ", ori31 speculation barrier enabled");  in cpu_show_spectre_v1()
248  * Store-forwarding barrier support.
257 	pr_info("stf-barrier: disabled on command line.");  in handle_no_stf_barrier()
268 		/* Until firmware tells us, we have the barrier with auto */  in handle_ssbd()
320 		pr_info("stf-barrier: fallback barrier available\n");  in setup_stf_barrier()
322 		pr_info("stf-barrier: hwsync barrier available\n");  in setup_stf_barrier()
324 		pr_info("stf-barrier: eieio barrier available\n");  in setup_stf_barrier()
350 		return sprintf(buf, "Mitigation: Kernel entry/exit barrier (%s)\n", type);  in cpu_show_spec_store_bypass()
368 		 * We assume that if we're on another CPU, where the barrier is  in ssb_prctl_get()
374 		 * If we do have a barrier type then we are vulnerable. The  in ssb_prctl_get()
375 		 * barrier is not a global or per-process mitigation, so the  in ssb_prctl_get()