From: Wei Liu <wei.liu2@citrix.com>
To: George Dunlap <george.dunlap@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] tools: delete gtraceview and gtracestat
Date: Fri, 2 Sep 2016 12:07:44 +0100 [thread overview]
Message-ID: <20160902110744.GN21282@citrix.com> (raw)
In-Reply-To: <7770abe5-ba4c-0abe-7be9-db7aa3dadba6@citrix.com>
On Fri, Sep 02, 2016 at 12:05:49PM +0100, George Dunlap wrote:
> On 30/08/16 13:50, Ian Jackson wrote:
> > Wei Liu writes ("[PATCH] tools: delete gtraceview and gtracestat"):
> >> There has not been any substantial update to them since 2011. My quick
> >> check shows that they don't work.
> >>
> >> Just delete them. It would be easy to resurrect them from git log should
> >> people still need them.
> >
> > I'm not sure what these are. git log is not particularly
> > illuminating. gtraceview.c and some of the commit messages talk about
> > "Cx events" or "x86 Cx" and there is an Intel copyright notice, but
> > not Intel email addresses.
> >
> > There is also some discussion of xentrace in the source code.
> >
> > Are these the only in-tool consumer of some kind of hypervisor
> > -generated or -mediated data ? If so it should be retained IMO, or
> > the corresponding hypervisor code removed too.
> >
> > I have added George to the CC in the hope that he may know more...
>
> Well I'd never looked at it before, but it does indeed seem to be
> something about skimming through xentrace records.
>
> The help for both functions says to run "xentrace -e 0x80f000", which
> will capture all events of type TRC_HW, which includes TRC_PM. The code
> (again for both) then seems to parse events of type TRC_PM_IDLE_ENTRY,
> TRC_PM_IDLE_EXIT, and TRC_PM_FREQ_CHANGE.
>
> gtraceview seems to be an ncurses-based browser; gtracestat seems to be
> a xenalyze-style statistical analysis thing.
>
> So it would seem to be the case that they consume hypervisor-generated
> data, but they are not the *only* consumers of that data
> (xentrace_format and xenalyze being the other ones).
>
> When you say they "don't work", what do you mean?
>
Tried to run it. It failed to produce anything useful. It is bit-rotten.
Wei.
> -George
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-09-02 11:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 15:27 [PATCH] tools: delete gtraceview and gtracestat Wei Liu
2016-08-30 12:50 ` Ian Jackson
2016-09-02 11:05 ` George Dunlap
2016-09-02 11:07 ` Wei Liu [this message]
2016-09-02 11:13 ` George Dunlap
2016-09-02 11:15 ` Wei Liu
2016-09-02 11:36 ` Ian Jackson
2016-09-02 13:35 ` Wei Liu
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=20160902110744.GN21282@citrix.com \
--to=wei.liu2@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.