On Tue, 6 Nov 2018 17:54:17 +0100 Halil Pasic <pasic@xxxxxxxxxxxxx> wrote: > On Thu, 25 Oct 2018 14:37:45 +0200 > Michael Mueller <mimu@xxxxxxxxxxxxx> wrote: > > > This metric will allow to identify how many vcpus are currently > > running for a given kvm in SIE context. Its value is between 0 and > > the number of vcpus defined for the kvm guest, but never lager than > > the number of cpus available to the KVM host in total. > > > > This metric is required to decide if the GISA IAM has to be restored > > from the kvm arch field of the guest. That will be the case when no > > vcpu is in SIE context. (vcpus_in_sie == 0) > > > > Mimu, we just spoke about -- thus a reminder for us, and a FYI for > the rest. vcpus_in_sie != 0 does not necessarily mean that FW can > deliver GISA interrupts to the guest (and thus we don't have to > dispatch a suitable vcpu): if all cpus in SIE mask IO interrupts it > does not really matter that they are in SIE. I.e. we should still get > alerted and try to dispatch an eligible vcpu. So, do we need to restore the IAM as well if all cpus in SIE have I/O interrupts masked? Or is it just some dispatching we have to do?
