Hi Olaf,
On 09/06/2015 07:23, Olaf Hering wrote:
To match the hypervisor default which was introduced in
9da0c5b63933b9912e3903190601661813954d0d, bump the limit.
Signed-off-by: Olaf Hering <o...@aepfle.de>
Acked-by: George Dunlap <george.dun...@eu.citrix.com>
Acked-by: Wei Liu <wei.l...@citrix.com>
Cc: Ian Jackson <ian.jack...@eu.citrix.com>
Cc: Stefano Stabellini <stefano.stabell...@eu.citrix.com>
Cc: Ian Campbell <ian.campb...@citrix.com>
Cc: Wei Liu <wei.l...@citrix.com>
---
tools/xentrace/analyze.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/xentrace/analyze.h b/tools/xentrace/analyze.h
index 40ee551..64b1911 100644
--- a/tools/xentrace/analyze.h
+++ b/tools/xentrace/analyze.h
@@ -16,7 +16,7 @@
#define TRC_LOST_RECORDS_END (TRC_GEN + 50)
-#define NR_CPUS 128
+#define NR_CPUS 256
You are updating NR_CPUS but this is only used for cpumask_t which is
never used within xenalyze.
Only cpu_mask_t is used and alias to a uint32_t. Or did I miss something?
There is also a variable MAX_CPUS defined to 256. which is used every.
Regards,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
