xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: George Dunlap <george.dunlap@eu.citrix.com>, xen-devel@lists.xen.org
Subject: Re: [PATCH v4 0/9] add xenalyze to staging
Date: Wed, 3 Jun 2015 11:15:13 +0100	[thread overview]
Message-ID: <1433326513.7108.55.camel@citrix.com> (raw)
In-Reply-To: <1433326259.7108.53.camel@citrix.com>

On Wed, 2015-06-03 at 11:10 +0100, Ian Campbell wrote:
> On Sat, 2015-05-23 at 08:24 +0000, Olaf Hering wrote:
> > Having xenalyze in the source tree makes it much easier to keep private
> > debug code in hypervisor and xenalyze in sync. It helped alot while
> > debugging the root cause for commit 607e8494c42397fb249191904066cace6ac9a880.
> 
> I'm afraid it doesn't build on arm64.

BTW, it did build on arm32, I think it should be built for both arm* (so
fixed on arm64) or neither (so not build for arm32) though.

  reply	other threads:[~2015-06-03 10:15 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 [this message]
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
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=1433326513.7108.55.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=george.dunlap@eu.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 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).