> On 05/03/2016 09:50 AM, Wanpeng Li wrote:
> > 2016-05-02 18:42 GMT+08:00 Christian Borntraeger <borntraeger@xxxxxxxxxx>:
> > [...]
> >> Some wakeups should not be considered a sucessful poll. For example on
> >> s390 I/O interrupts are usually floating, which means that _ALL_ CPUs
> >> would be considered runnable - letting all vCPUs poll all the time for
> >> transactional like workload, even if one vCPU would be enough.
> >> This can result in huge CPU usage for large guests.
> >> This patch lets architectures provide a way to qualify wakeups if they
> >> should be considered a good/bad wakeups in regard to polls.
> >>
> >> For s390 the implementation will fence of halt polling for anything but
> >> known good, single vCPU events. The s390 implementation for floating
> >> interrupts does a wakeup for one vCPU, but the interrupt will be delivered
> >> by whatever CPU comes first. To limit the halt polling we only mark the
> >
> > If the floating interrupt means that the 'CPU comes first' will
> > deliver the interrupt to all vCPUs?
>
> No. All CPUs do the normal vcpu_run loop. And before entering the guest
> every CPU will try to deliver pending interrupts
>
> static int __vcpu_run(struct kvm_vcpu *vcpu)
> {
> [...]
> do {
> rc = vcpu_pre_run(vcpu); ---------------------+
> if (rc) |
> break; |
> [...] |
> exit_reason = sie64a(vcpu->arch.sie_block, |
> vcpu->run->s.regs.gprs); |
> [...] |
> } |
> |
> static int vcpu_pre_run(struct kvm_vcpu *vcpu) <-------+
> {
> [...]
> if (!kvm_is_ucontrol(vcpu->kvm)) {
> rc = kvm_s390_deliver_pending_interrupts(vcpu); <----
> if (rc)
> return rc;
> [...]
> }
>
>
>
> and whichever comes first, will dequeue that interrupt and deliver it
> by doing the PSW swap (jumping to the interrupt handler address)
>
> (other CPUs will then not deliver this interrupt as it is already dequeued)
>
>
And regarding to questions if we should exclude floating IRQs from the blocked
check: That must not be done as floating IRQ (groups) can be disabled only on
certain CPUs.
An operating system is free to setup only certain CPUs to check for interrupts
(and disable it on the others). So all VCPUs have to check for floating IRQs,
otherwise situations might be provoked where floating IRQs are pending but not
delivered to any VCPU.
David
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
