From: Olaf Hering <olaf@aepfle.de>
To: Wei Liu <wei.liu2@citrix.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH v3 1/8] xenalyze: add to tools/xentrace/
Date: Fri, 22 May 2015 13:32:01 +0200 [thread overview]
Message-ID: <20150522113201.GA23914@aepfle.de> (raw)
In-Reply-To: <20150522112532.GM19083@zion.uk.xensource.com>
On Fri, May 22, Wei Liu wrote:
> On Fri, May 22, 2015 at 08:19:32AM +0000, Olaf Hering wrote:
> > BIN = xentrace xentrace_setsize
> > +SBIN = xenalyze
>
> Why is xenalyze not placed in the same directory as xentrace? My
> impression is that they are closely related. What did I miss?
>
> And given that xenalyze only analyse the log it shouldn't require
> privilege to run so it should be placed in BIN?
Perhaps that should be flipped then, xentrace needs be run as root AFAIK.
Olaf
next prev parent reply other threads:[~2015-05-22 11:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 8:19 [PATCH v3 0/8] add xenalyze to staging Olaf Hering
2015-05-22 8:19 ` [PATCH v3 1/8] xenalyze: add to tools/xentrace/ Olaf Hering
2015-05-22 11:25 ` Wei Liu
2015-05-22 11:32 ` Olaf Hering [this message]
2015-05-22 11:38 ` Wei Liu
2015-05-22 8:19 ` [PATCH v3 2/8] xenalyze: increase NR_CPUS to 256 Olaf Hering
2015-05-22 8:19 ` [PATCH v3 3/8] xenalyze: print newline after unknown hvm events Olaf Hering
2015-05-22 8:19 ` [PATCH v3 4/8] xenalyze: include odd mmio states in default output Olaf Hering
2015-05-22 8:19 ` [PATCH v3 5/8] xenalyze: handle TRC_TRACE_WRAP_BUFFER Olaf Hering
2015-05-22 8:19 ` [PATCH v3 6/8] xenalyze: handle more events in sched_process Olaf Hering
2015-05-22 11:19 ` Wei Liu
2015-05-22 8:19 ` [PATCH v3 7/8] xenalyze: remove traling whitespaces Olaf Hering
2015-05-22 8:19 ` [PATCH v3 8/8] xenalyze: remove argp_program_version Olaf Hering
2015-05-22 11:15 ` 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=20150522113201.GA23914@aepfle.de \
--to=olaf@aepfle.de \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@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 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.