On 10/28/2009 12:20 PM, Michael S. Tsirkin wrote:
Hmm. If we want to rely on this, we have to play with memory barriers to write/read it. Doable, but hard to get right. Can we always have the irqchip object exist? It doesn't use a lot of memory, does it? Maybe have it inline, save an extra indirection on fastpath ...
Good idea. Note we still need to check irqchip_in_kernel() for correctness (for example hlt behaviour changes).
-- 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
