[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [PATCH v3] Support CPU-list parsing in xentrace.
Hey George and Ian, Since v2 (http://lists.xen.org/archives/html/xen-devel/2014-06/msg01835.html) I've modified it per the reviews I've received. Hopefully this is the last round of reviews :-) The purpose of these patches is to allow users of xentrace to narrow down a specific CPU without having to figure out a bit mask. They fix the limitation of the bit mask which is it can only do up to 32-bits - which on large machines (say 120CPUs), you can't selectively trace anything past 32CPUs. The code expands the -c parameter where you can do -c <starting cpu>-<end cpu> or -c <cpu1>,<cpu2> or a combination of them. This along with 'xl vcpu-list' makes it extremely easy to trace a specific guest (if pinned). You can still use the -c 0x<some hex value> option if you prefer. tools/libxc/xc_tbuf.c | 26 ++++-- tools/libxc/xenctrl.h | 7 ++- tools/xentrace/xentrace.8 | 21 ++++- tools/xentrace/xentrace.c | 221 +++++++++++++++++++++++++++++++++++++++++---- 4 files changed, 244 insertions(+), 31 deletions(-) Konrad Rzeszutek Wilk (2): libxc/xentrace: Replace xc_tbuf_set_cpu_mask with CPU mask with xc_cpumap_t instead of uint32_t xentrace: Implement cpu mask range parsing of human values (-c). _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |