On Fri, 2010-11-26 at 12:25 +0100, Stephane Eranian wrote:
Well, its either that or keeping a node wide state like we do for AMD
and serialize everything from there.
And I'm not sure what's most expensive, steering the interrupt to one
core only, or broadcasting every interrupt, I'd favour the first
The whole thing is a node-wide resource, so the user needs to think in
nodes anyway, we already do a cpu->node mapping for identifying the