Jens Axboe wrote:
Xen could just stuff that bit into its arch_send_call_function_ipi(), something like the below should be fine. My question to Jeremy was more of the order of whether it should be kept or not, I guess it's safer to just keep it and retain the existing behaviour (and let Jeremy/others evaluate it at will later on). Note that I got rid of the yield bool and break when we called the hypervisor.
Yes, it's a nice cleanup.
Jeremy, shall I add this?
Hold off for now. Given that its effects are unmeasured, I'm not even sure its the right thing to do. For example, it will yield if you're sending an IPI to a vcpu which wants to run but can't, but does nothing for an idle vcpu. And always yielding may be a performance problem if the IPI doesn't involve any cpu contention.
It's easy to add back if it turns out to be useful. J -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
