On 13/01/2026 18:19, Samuel Thibault wrote:
which makes sure to put the content of save_data on the stack instead of
in xmm0, while calling mach_msg().

So we have something that clobbers xmm0 somehow, and this is only a dumb
workaround that only avoids the issue in the notable but still
particular case of blocking RPCs.

This description might also apply to the similar situation that I am seeing with the stress-ng tests. The asm generated from the stress-ng code in function stress_vm_incdec makes use of a number of %xmm registers.

Mike.


Reply via email to