From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: [PATCH] xenalyze: increase MAX_CPUS Date: Thu, 14 Jul 2011 12:53:03 +0100 Message-ID: <1310644383.448.20.camel@elijah> References: <1d7a842aecc538c794c7.1310472961@probook.site> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1d7a842aecc538c794c7.1310472961@probook.site> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Olaf Hering Cc: George Dunlap , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org Applied, thanks. -George On Tue, 2011-07-12 at 13:16 +0100, Olaf Hering wrote: > # HG changeset patch > # User Olaf Hering > # Date 1310472861 -7200 > # Node ID 1d7a842aecc538c794c78db93d141cdc5683882c > # Parent 275dd17a6a36023ffa4e25f1b0d358c22af098b8 > xenalyze: increase MAX_CPUS > > On a large system xenalyze will refuse to process the trace file because it > has an hardcoded limit of 32 cpus. The default of NR_CPUS in xen-unstable is > 128. Increase the limit to match xen-unstable and also add an option to > override the macro with a gcc cmdline option. > > Signed-off-by: Olaf Hering > > diff -r 275dd17a6a36 -r 1d7a842aecc5 xenalyze.c > --- a/xenalyze.c > +++ b/xenalyze.c > @@ -1618,7 +1618,9 @@ struct cr3_value_struct { > } destroy; > }; > > -#define MAX_CPUS 32 > +#ifndef MAX_CPUS > +#define MAX_CPUS 128 > +#endif > typedef uint32_t cpu_mask_t; > > #define IDLE_DOMAIN 32767