On 04/14/2010 01:27 PM, Sheng Yang wrote:
Yes, interesting to see what the latency is. If it's reasonably short
(and I expect it will be so), we can do the busy wait solution.
If we have an NMI counter somewhere, we can simply wait until it changes.
Good idea. Of course we have one(at least on x86). There is
irq_stat.irq__nmi_count for per cpu. :)
Okay, but kvm doesn't want to know about it. How about a new arch
function, invoke_nmi_sync(), that will trigger the NMI and wait for it?
--
error compiling committee.c: too many arguments to function
--
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
