xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: "Zhang, Yang Z" <yang.z.zhang@intel.com>
Cc: Ian Jackson <ian.jackson@citrix.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [PATCH] xentrace: add a tool to break down the result of vmexit
Date: Fri, 9 Aug 2013 10:10:19 +0100	[thread overview]
Message-ID: <5204B1FB.6020609@eu.citrix.com> (raw)
In-Reply-To: <A9667DDFB95DB7438FA9D7D576C3D87E0A8DFB94@SHSMSX104.ccr.corp.intel.com>

On 09/08/13 09:54, Zhang, Yang Z wrote:
> Zhang, Yang Z wrote on 2013-08-09:
>> George Dunlap wrote on 2013-08-09:
>>> On Fri, Aug 9, 2013 at 7:34 AM, Yang Zhang <yang.z.zhang@intel.com>
>> wrote:
>>>> From: Yang Zhang <yang.z.zhang@Intel.com>
>>>>
>>>> The tool is able to provide a summary of vmexit. Currently, it only
>>>> supports to summay one VCPU result at a time.
>>> Have you seen xenalyze?
>>>
>>> hg clone http://xenbits.xen.org/ext/xenalyze
>> Thanks. Now I see it. It's a great tool.
> Does it integrate to Xen source? If no, it's better to add it to tool/xentrace/ instead use a separate repo to let more people know it. :)

Yes, this has been suggested before.  The original reason for having it 
be a separate repo is that most of the xenalyze development happened 
after a Xen release.  But I think it has more or less reached a 1.0 
level some time ago, and isn't seeing as many changes.

I'm not sure what it would take to get it checked into the main repo.  
At the moment the code is just one massive file (with a couple of helper 
files), and no doubt has a number of coding style inconsistencies - 
though I there is certainly worse code in the tree. :-)

Ian / Ian, any thoughts?

  -George

  reply	other threads:[~2013-08-09  9:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-09  6:34 [PATCH] xentrace: add a tool to break down the result of vmexit Yang Zhang
2013-08-09  8:47 ` George Dunlap
2013-08-09  8:51   ` Zhang, Yang Z
2013-08-09  8:54   ` Zhang, Yang Z
2013-08-09  9:10     ` George Dunlap [this message]
2013-08-09 13:28       ` Konrad Rzeszutek Wilk
2013-08-12 12:57         ` George Dunlap
2013-08-19 14:26           ` Ian Jackson
2013-08-19 14:38             ` George Dunlap
2013-08-19 16:51               ` Ian Jackson

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=5204B1FB.6020609@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@citrix.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=yang.z.zhang@intel.com \
    /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).