Hi Jan, On 05/01/2021 13:10, Jan Beulich wrote:
Global vIRQ-s have their event channel association tracked on vCPU 0. Per-vCPU vIRQ-s can't have their notify_vcpu_id changed. Hence it is well-known which vCPU's virq_to_evtchn[] needs updating.
I went through the history and couldn't find a reason for looping the vCPUs.I have also looked at the code and agree with the analysis provided in the commit message.
Reviewed-by: Julien Grall <jgr...@amazon.com> Cheers, -- Julien Grall
