There were two (probably unimportant, given that we've run a billion or
two Xen guests on this now without noticing except by code inspection)
ways in which the KVM implementation of SCHEDOP_poll differs from Xen:
1. Xen allows a vCPU to poll a port which is targeted at another vCPU.
2. Xen explicitly wakes a polling vCPU even when the event is unmasked.
I can't imagine why the first would ever be used, but the second could
theoretically be important. KVM currently wouldn't actually deliver an
interrupt to the target vCPU if another port was already pending, but
if the poll was being used to handle spinlock contention inside another
interrupt handler, the wakeup might never happen and lead to a deadlock.
Signed-off-by: David Woodhouse <dwmw@amazon.co.uk>