xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Chao Gao <chao.gao@intel.com>
To: xen-devel@lists.xen.org, George Dunlap <George.Dunlap@eu.citrix.com>
Subject: Re: encounter a problem about xenalyze
Date: Tue, 23 May 2017 17:49:25 +0800	[thread overview]
Message-ID: <20170523094923.GA14837@skl-2s3> (raw)
In-Reply-To: <20170519105338.GA31359@skl-2s3.sh.intel.com>

On Fri, May 19, 2017 at 06:53:39PM +0800, Chao Gao wrote:
>Hi, George.
>
>Per your suggesion, I tried to add some code to xenalyze.c to analyze
>some newly added events. To have more understanding, you can read the
>patch at the bottom. In this patch, I try to count how many times a
>given vcpu is added and removed from a pi blocking list. After
>collecting some data, I compared the result of different decoder,
>xenalyze and xentrace_format. I found that xentrace_format shows
>one vcpu is added and removed 2499 times respectively. But xenalyze
>shows the identical vcpu is added 2499 times and removed only about
>700 times. Some other vcpus also encounter this weird thing.

Hi, George. I found the cause. It is for removing one vcpu from
pi blocking list can happen in various contexts. Some contexts
can't pass toplevel_assert_check().

Thanks
Chao

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

      reply	other threads:[~2017-05-23  9:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-19 10:53 encounter a problem about xenalyze Chao Gao
2017-05-23  9:49 ` Chao Gao [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170523094923.GA14837@skl-2s3 \
    --to=chao.gao@intel.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).