From: Ian Campbell <ian.campbell@citrix.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: Wei Liu <wei.liu2@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
George Dunlap <george.dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
xen-devel@lists.xen.org, Julien Grall <julien.grall@citrix.com>
Subject: Re: [PATCH v5 2/8] xenalyze: increase NR_CPUS to 256
Date: Tue, 16 Jun 2015 09:33:55 +0100 [thread overview]
Message-ID: <1434443635.13744.47.camel@citrix.com> (raw)
In-Reply-To: <20150615175828.GA11759@aepfle.de>
On Mon, 2015-06-15 at 19:58 +0200, Olaf Hering wrote:
> On Mon, Jun 15, Andrew Cooper wrote:
>
> > In an ideal world, userspace tools like this should not really be tied
> > to NR_CPUS or MAX_CPUS. They should get max_cpu_id from Xen and
> > dynamically allocate a bitmap of sufficient size.
>
> The dumps are taken on one machine and get inspected on another, which
> may not even be a dom0. I like the idea with dynamically allocate the
> array size, based on a cmdline option. Once I find the time I will
> implement it.
Perhaps we should split out "get xenalyze in tree" out from actual
improvements and development work? The former ought to be pretty easy to
achieve, no?
Ian.
next prev parent reply other threads:[~2015-06-16 8:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 11:23 [PATCH v5 0/8] add xenalyze to staging Olaf Hering
2015-06-09 11:23 ` [PATCH v5 1/8] xenalyze: add to tools/xentrace/ Olaf Hering
2015-06-11 15:23 ` George Dunlap
2015-06-11 16:04 ` Olaf Hering
2015-06-09 11:23 ` [PATCH v5 2/8] xenalyze: increase NR_CPUS to 256 Olaf Hering
2015-06-10 20:29 ` Julien Grall
2015-06-11 6:12 ` Olaf Hering
2015-06-11 11:03 ` Julien Grall
2015-06-11 14:35 ` George Dunlap
2015-06-15 16:14 ` Olaf Hering
2015-06-15 17:19 ` Andrew Cooper
2015-06-15 17:58 ` Olaf Hering
2015-06-16 8:33 ` Ian Campbell [this message]
2015-06-16 8:35 ` Olaf Hering
2015-06-09 11:23 ` [PATCH v5 3/8] xenalyze: print newline after unknown hvm events Olaf Hering
2015-06-09 11:23 ` [PATCH v5 4/8] xenalyze: include odd mmio states in default output Olaf Hering
2015-06-09 11:23 ` [PATCH v5 5/8] xenalyze: handle TRC_TRACE_WRAP_BUFFER Olaf Hering
2015-06-09 11:23 ` [PATCH v5 6/8] xenalyze: handle more events in sched_process Olaf Hering
2015-06-09 11:23 ` [PATCH v5 7/8] xenalyze: remove trailing whitespaces Olaf Hering
2015-06-09 11:23 ` [PATCH v5 8/8] xenalyze: remove argp_program_version Olaf Hering
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=1434443635.13744.47.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=julien.grall@citrix.com \
--cc=olaf@aepfle.de \
--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.