>>> This complexifies migration because we have to guess at >>> post load if we should claim the IPI in KVM or not. The >>> simple presence of the vCPU isn't enough : we need to >>> guess if the guest actually configured the IPI or not. >> >> The EAT will be transferred from the source and the call to >> kvmppc_xive_source_reset_one() should initialize the KVM >> device correctly on the target for all interrupts. >> > > Except that the EAS appears as valid for all IPIs, even > though the source didn't claim them at the KVM level.
why ? we would stop claiming IPIs in spapr_irq_init() and so they won't appear as being valid anymore, at boot time or restore time. C.
