Re: [Xen-devel] Problem with simple scheduler

[Manohar Vanga <manohar.vanga@xxxxxxxxx>]

Hi Andrew,

Thanks for the quick reply! My comments are inline:

Â

Using printk()s in the code is going to skew the timing terribly.

Would this affect the boot process of dom0 in any way? Other than that, it doesn't seem like it would cause any problems right?

Â

A serial console and the 'q' debug key is probably a good start, to see some vcpu state.

I'll give this a try but the problem is that I'm not entirely sure what I'm looking for. As I mentioned, the vcpu of dom0 goes idle after the crash-point.

Â

Beyond that, writing a custom keyhandler to dump all of the xfair state is probably the next thing to try.

Hmm any hints on what I should be looking for? It's clear to me that the vcpu goes idle after that point where dom0 stops booting. Is there anything else I need to keep an eye out for? I'll also look into whether the skewed timing can possibly lead to a broken dom0 boot.

Also, in case you glanced at the code, do you happen to see any glaringly obvious bugs that you might have encountered? Otherwise I guess I'm looking for some odd corner-case behavior.

Thanks and best regards!

--
/mvanga

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel