On Wed, 25 May 2011, Ingo Molnar wrote: > That particular change was still under discussion and i'm not at all > sure we want to do it like that. So please repost the latest version. I had not seen such discussion; I had the impression that having dealt with my feedback about making the thing more visible to the user, Youquan considered the patch complete. I am more than happy to absolve responsibility for this patch altogether and drop it from tree, though. It is *absolutely* the wrong approach, in my opinion. If the BIOS is broken and cannot cope with x2apic, the solution is to line the "engineers" responsible up against the wall and shoot them. And then to implement a "quiesce all SMI" feature that the OS can invoke, and make it mandatory. Presumably that's the underlying problem they were trying to solve? The answer certainly isn't to add a flag in the DMAR table to opt out of x2apic use, when afaict the kernel is capable of using x2apic in some cases even when the *is* no DMAR. (Either that, or we have a lot of dead code in that area which *looks* like it copes with x2apic+!dmar). I'll drop this patch from my tree when I get home and happily wash my hands of it. It's all yours; have fun :) -- dwmw2 -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
