similar to: [PATCH]fix a little problem in formats file of xentrace

I am trying to learn some more about the way windows does TPR writes, and tried xentrace for the first time. I did ''xentrace --time-interval=5 xentrace.out'' to capture some data, and then ran it through ''xentrace_format'' using the supplied example defs file. I can see some PF_XEN entries with virt=0xFFFE0080 (address of TPR), but I want to know the value being

Hi, xentrace_format cannot use "0x016x" format as we expect. It show only %(N) as "0x016x" format, not as "%(N+1)08x%(N)08x". So I fixed tools/xentrace/formats by using "%(N+1)08x%(N)08x" format. Also I added some TRC_PV entries. Signed-off-by: Akio Takebe <takebe_akio@jp.fujitsu.com> Best Regards, Akio Takebe

I am having problems with save/restore under 3.3.1 in the GPLPV drivers. I call hvm_shutdown(xpdd, SHUTDOWN_suspend), but as soon as I lower IRQL (enabling interrupts), qemu goes to 100% CPU and the DomU load goes right up too. Xentrace is showing a whole lot of this going on: CPU0 200130258143212 (+ 770) hypercall [ rip = 0x000000008020632a, eax = 0xffffffff ] CPU0 200130258151107 (+

Hi All, I am running xentrace on an idle machine (dom0 has 2 cpus). There are 4 cpus in the system > date xentrace -e0x82000 > idle.out date The sampling interval is 25 seconds. However when I format and look at the output, I see the sample time is 761 seconds or something bizarre Looks like the cpu cycles have gone beserk. Any ideas as to what could be happening thanks Prabha

Hi, I've made some SAP benchmarks on my Xen system and discovered a huge difference in the performance of a "xened" SAP system compared to a native SAP system. Hence, I tried to figure out what might cause this 'overhead' and run a xentrace (listining to all events). Xentrace produced 24gb data and I converted it to 27gb human-readable data. After I gathered the

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-2 Severity: normal # xentrace /usr/lib/xen-3.0.3-1/bin/xentrace: error while loading shared libraries: libxenctrl.so: cannot open shared object file: No such file or directory It seems that we need a /etc/ld.so.conf.d/xen file that includes directory /usr/lib/xen-3.0.3-1/lib . -- System Information: Debian Release: 4.0 APT prefers testing APT

Hello, I''ve been trying to get xenmon.py and xentrace to work, but I consistently get the following (on a couple of different machines/kernels): kibab kibab # xentrace /root/xentrace.log ERROR: Failure to get trace buffer pointer from Xen (22 = Invalid argument) Did I miss an option that has to be turned on or something? Is there some other setting that I need so that everything

Hi, I have read a mail in the mail list about xentrace and xentrace_format. But I am still puzzled on how to use them. Could somebody give me an example about how to use xentrace and xentrace_format. What I have done is that: 1. Root:/# xentrace /var/perftests/xentrace.log Then I use xentrace_format to get what I want 2. cat /var/perftests/xentrace.log | xentrace_format

Hi, I have read a mail in the mail list about xentrace and xentrace_format. But I am still puzzled on how to use them. Could somebody give me an example about how to use xentrace and xentrace_format. What I have done is that: 1. Root:/# xentrace /var/perftests/xentrace.log Then I use xentrace_format to get what I want 2. cat /var/perftests/xentrace.log | xentrace_format

_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

xentrace, setsize and the hypervisor don''t seem to be on the same page. If tracing is not enabled, the hypercall will only allow TBUF_SET_SIZE and TBUF_ENABLE. However, set_size calls TBUF_GET_INFO, and xentrace wants to call TBUF_SET_EVT_MASK and TBUF_SET_CPU_MASK before calling TBUF_ENABLE. I don''t see any reason not to call SET_*_MASK and GET_INFO if tracing is not enabled.

Hi, 20827:fad80160c001 cannot be compiled on ia64: xentrace.c:647: error: ''PAGE_SIZE'' undeclared (first use in this function) This patch fixes it. Signed-off-by: KUWAMURA Shin''ya <kuwa@jp.fujitsu.com> Best regards, -- KUWAMURA Shin''ya _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Hi, I am using xen-unstable and interested to trace the hypervisor. In previous versions, I was able to trace it by: setsize 20 tbctl 1 xentrace /tmp/xentrace.dat And these functions don''t exist in xen-unstable. xentrace --help shows that in more recent versions the buffers'' size could be determined as a parameter for xentrace. But I can not find any replacement for

Hi, Xenmon does not work correctlly after xentrace changes in cs 17000. Attached patch fixes this problem. This patch modifies access to trace buffer same as tools/xentrace. Signed-off-by: Naoki Nishiguchi <nisiguti@jp.fujitsu.com> Regards, Naoki Nishiguchi _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Package: xen-utils-common Version: 3.0.3-0-2 Severity: minor xentrace(8) is missing and it seems there's one around: http://www.die.net/doc/linux/man/man8/xentrace.8.html -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash

_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi, All This is a patch for xentrace.c. This routine checks the trace buffer is initialized or not. If not, the trace buffer is initialized by using this patch. This is avoiding following message. ERROR: Failure to get trace buffer pointer from Xen (22 = Invalid argument) This routine is based on the specification of the trace buffer control function trace.c/tb_control(). The function checks

Hello, I have a question about the way Xentrace takes a trace. In previous versions of Xen, I took a trace by setting the size of buffers, activating them and writing the information into a file (optional). setsize 20 tbctl 1 xentrace /tmp/xentrace.dat Now I''m using xen-unstable and I see that setsize is already integrated in xentrace command. My question is: does start/stop buffer is

Since TRC_MEM is defined as 0x000af000 in xen/include/public/trace.h, TRC_MEM = TRC_SCHED | TRC_VMX. I feel strange about this. I do not think scheduling is a part of memory management. Am I right? If not, please tell me the background TRC_MEM is defined as TRC_SCHED | TRC_VMX. If so, please apply this patch. This patch defines TRC_MEM as an independent event mask. In addition, xentrace