On Jan 20, 2008 7:37 PM, Jeremy Fitzhardinge <[EMAIL PROTECTED]> wrote: > xming wrote: > > ok I have done some of them, but I still don't know what I should be looking > > at. Do you mean code related to xen or code related to > > have_vcpu_info_placement? > > Please be patient with me :) > > > > I just paste some of the result (around those addresses) here: > > > > Thanks, that answers that particular question; the vcpu is blocked > waiting for something to happen, which probably means it missed the > event which was supposed to wake it up. Why is another question. At > least there's a workaround, and that workaround gives me some clue where > to look.
Want me to test it? > BTW, is it an SMP or UP domain? Does it make a difference? It doesn't matter, I tried vcpu=1 and vcpu=2, unless you want me to try to recompile a UP kernel? > >> OK, good. I Didn't Break It (tm) ;) > > > So no fix from you? :) > > Maybe when I have nothing else to do. I'll wait, or should I poke xen-devel? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
