Re: [Xen-users] xentop missing domain state marker

[Stefan Parvu <sparvu@xxxxxxxxxxxxxxxxxxxxxx>]

> My guess is that under load vcpus are being migrated between pcpus and
> that this "being migrated" state is one which isn't described.
> 

makes sense. But we probable need a better state 'm' to show the domains
are being migrated ?


> "------" pretty much is "NA".
> 

No it is not. If you have raw data collected from xentop / xenrec etc
and you try to do some numerical analysis with that you are doomed.
Or we have a valid state, say 'm' or we need to mark it as NA. Tools
like Mathematica, R etc will digest NA. They wont digest ------ or worse
this could lead some silent other bugs. Like in my case xenrec.

> You could propose a patch against
> xen.git/xen/common/domctl.c:getdomaininfo() to consider other states the
> VPF_blocked as blocked, (list is in xen/include/xen/sched.h) or
> introduce a new state to be propagated up to the tools (and patch the
> tools to consume it).
> 
> http://wiki.xen.org/wiki/Submitting_Xen_Patches for hints and tips about
> the patch submission process.

Thanks a lot. I will do that. As soon as Im repeating the tests and read
over all these things.

Thanks again for help,

-- 
Stefan Parvu <sparvu@xxxxxxxxxxxxxxxxxxxxxx>




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