[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH RFC for-4.13 04/10] xen/arm: Ensure the SSBD workaround is re-enabled right after exiting a guest
On 30/09/2019 13:14, Volodymyr Babchuk wrote: Hi Julien, Julien Grall writes:At the moment, SSBD workaround is re-enabled for Xen after interrupts are unmasked. This means we may end up to execute some part of the hypervisor if an interrupt is received before the workaround is re-enabled. As the rest of enter_hypervisor_from_guest() does not require to have interrupts masked, the function is now split in two parts: 1) enter_hypervisor_from_guest_noirq() called with interrupts masked.To summarize our discussion in this mail thread: providing that you'll rename enter_hypervisor_from_guest_noirq to enter_hypervisor_from_guest_preirq(): Reviewed-by: Volodymyr Babchuk <volodymyr_babchuk@xxxxxxxx> Thank you. I will try to summarize the discussion we had in the commit message. So we know the rationale of the split here. Cheers, -- Julien Grall _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |