Sorryï it seems that my mailer doesn't have this function.
My question is :
1ãhow is the blocked time of a domain computed? And how is the blocked time of a vcpu computed ?
2ãIn Runstates, there are many terms , such as partial run, full run, partial contention, concurrency_hazard, full contention, wake, preempt,lostã What do they mean?
3ãin log volume summary, why are there so many hvms ? in fact there are only three hvm guest and one domain0 in this machine. Also, the terms such as gen, sched, verbose, hvm, handler means what ï
-----éäåä-----
åää: dunlapg@xxxxxxxxx [mailto:dunlapg@xxxxxxxxx] äè George Dunlap
åéæé: 2015å5æ12æ 17:31
æää: èéä(èå)
æé: xen-devel@xxxxxxxxxxxxxxxxxxx; xen-devel@xxxxxxxxxxxxx
äé: Re: [Xen-devel] çå: çå: çå: about xenalyze
On Tue, May 12, 2015 at 3:18 AM, èéä(èå) <xiongwei.jiang@xxxxxxxxxxxxxxx> wrote:
> I try again with "-e 0xaf000", and run xenalyze --summary. The attached is the output.
Again, please don't top-post: configure your mailer to quote properly, and reply in-line (as I am doing now).
So it looks like now it works. :-)
You can find a bit about what the output is from the xenalyze.html wiki inside the repo. In particular, look for "Quickstart - Generate a summary".
-George
>
> -----éäåä-----
> åää: dunlapg@xxxxxxxxx [mailto:dunlapg@xxxxxxxxx] äè George Dunlap
> åéæé: 2015å5æ11æ 18:05
> æää: èéä(èå)
> æé: xen-devel@xxxxxxxxxxxxxxxxxxx; xen-devel@xxxxxxxxxxxxx
> äé: Re: [Xen-devel] çå: çå: about xenalyze
>
> On Fri, May 8, 2015 at 3:41 AM, èéä(èå) <xiongwei.jiang@xxxxxxxxxxxxxxx> wrote:
>> $xenalyze --summary trace_file_discuz.bin
>
> [snip]
>
>> This is the full output.
>
> Don't top-post please.
>
> I probably should have said "attach the full output", rather than including it inline.
>
> So actually -- it looks like you've set the trace to only collect HVM-related tracing information ("-e 0x8f000" from your command-line below); but to get the output that you want (with the per-domain and per-vcpu summaries), it also needs the scheduling traces, so that it knows which vcpu is running where.
>
> Can you try this again with "-e 0xaf000" and see what you get?
>
>Â -George
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxx
> http://lists.xen.org/xen-devel
>
