From: George Dunlap <george.dunlap@eu.citrix.com>
To: Julien Grall <julien.grall@citrix.com>, Olaf Hering <olaf@aepfle.de>
Cc: Ian Campbell <ian.campbell@citrix.com>, xen-devel@lists.xen.org
Subject: Re: [PATCH v4 0/9] add xenalyze to staging
Date: Tue, 9 Jun 2015 12:38:35 +0100 [thread overview]
Message-ID: <5576D03B.1060801@eu.citrix.com> (raw)
In-Reply-To: <5576CE9B.4050101@citrix.com>
On 06/09/2015 12:31 PM, Julien Grall wrote:
> Hi Olaf,
>
> On 09/06/2015 06:18, Olaf Hering wrote:
>> On Wed, Jun 03, Julien Grall wrote:
>>
>>> xentrace is not working as we don't have the infrastructure for ARM
>>> in Xen.
>>
>> Why is that? After a very quick look __trace_var is available
>> unconditionally.
>
> Multiple reasons, the shared page for trace is not correctly exposed,
> __trace_var/__trace_hypercall is not even used on ARM. I may miss some
> other bugs that I didn't spot while looking to the code.
Code in xen/common will generate traces (e.g., the scheduling code), so
useful traces are already in place for ARM, even if no arm-specific code
has trace points yet.
> So I don't think we should build a non-working binary until someone
> fixes the various problem of the trace system on ARM.
If the shared page really doesn't work, then yes, we should probably not
build it on ARM for the release.
Would it be very difficult to get working?
-George
next prev parent reply other threads:[~2015-06-09 11:38 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-23 8:24 [PATCH v4 0/9] add xenalyze to staging Olaf Hering
2015-05-23 8:24 ` [PATCH v4 1/9] xentrace: install into sbin Olaf Hering
2015-05-25 8:33 ` Wei Liu
2015-06-02 17:03 ` George Dunlap
2015-05-23 8:24 ` [PATCH v4 2/9] xenalyze: add to tools/xentrace/ Olaf Hering
2015-05-25 8:34 ` Wei Liu
2015-06-02 17:06 ` George Dunlap
2015-05-23 8:24 ` [PATCH v4 3/9] xenalyze: increase NR_CPUS to 256 Olaf Hering
2015-05-23 8:24 ` [PATCH v4 4/9] xenalyze: print newline after unknown hvm events Olaf Hering
2015-05-23 8:24 ` [PATCH v4 5/9] xenalyze: include odd mmio states in default output Olaf Hering
2015-05-23 8:24 ` [PATCH v4 6/9] xenalyze: handle TRC_TRACE_WRAP_BUFFER Olaf Hering
2015-05-23 8:24 ` [PATCH v4 7/9] xenalyze: handle more events in sched_process Olaf Hering
2015-06-02 17:12 ` George Dunlap
2015-06-09 10:44 ` Olaf Hering
2015-05-23 8:24 ` [PATCH v4 8/9] xenalyze: remove traling whitespaces Olaf Hering
2015-05-23 8:24 ` [PATCH v4 9/9] xenalyze: remove argp_program_version Olaf Hering
2015-06-02 17:16 ` [PATCH v4 0/9] add xenalyze to staging George Dunlap
2015-06-03 10:33 ` Ian Campbell
2015-06-03 10:10 ` Ian Campbell
2015-06-03 10:15 ` Ian Campbell
2015-06-03 10:33 ` George Dunlap
2015-06-03 10:59 ` Ian Campbell
2015-06-03 11:16 ` George Dunlap
2015-06-03 11:21 ` George Dunlap
2015-06-03 11:34 ` Ian Campbell
2015-06-03 10:35 ` Julien Grall
2015-06-03 10:38 ` Andrew Cooper
2015-06-03 10:38 ` George Dunlap
2015-06-03 10:41 ` Andrew Cooper
2015-06-03 10:42 ` George Dunlap
2015-06-03 10:49 ` George Dunlap
2015-06-09 10:18 ` Olaf Hering
2015-06-09 11:31 ` Julien Grall
2015-06-09 11:38 ` George Dunlap [this message]
2015-06-09 23:21 ` Julien Grall
2015-06-15 9:23 ` George Dunlap
2015-06-15 12:44 ` Julien Grall
2015-06-15 13:46 ` George Dunlap
2015-06-16 7:21 ` Roger Pau Monné
2015-06-09 6:54 ` Olaf Hering
2015-06-09 11:07 ` Olaf Hering
2015-06-10 21:23 ` Julien Grall
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=5576D03B.1060801@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=julien.grall@citrix.com \
--cc=olaf@aepfle.de \
--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.