similar to: Does xentrace write into buffers by default?

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

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

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, 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

Nice time. # make uninstall ... rm -rf //boot/*xen* ... if somebody use "xen" in kernel name (maybe as suffix), so it will be deleted from /boot/ too. Thanks. Denis.

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

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

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

Hello, this patch introduces HVM tracing: one tracing class for both, SVM and VMX. It adds several new trace events. So we can differentiate between them in the xentrace formats file and format each event''s data items appropriately. With this patch the xentrace_format output is much more informative. The previous simple tracing in SVM and VMX is completely replaced. Unfortunately I

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

Hello, I''m using Xen-unstable and the kernel 2.6.18. Doing some particular tests, I need to disable the SMP Support in the kernel configuration and surprisingly I receive this error after compiling the kernel: CC init/version.o LD init/built-in.o LD .tmp_vmlinux1 drivers/built-in.o: In function `take_machine_down'': machine_reboot.c:(.text+0x58a6c):

Hi, All! This is a patch which needs discussion. Currently xc_tbuf_enable assumed tb_init_done = 0. But Sometimes already on For example(xenmon.py(xenbaked) and xentrace). These two programs assues tb_init_done =0 at start time. Currently xenbaked care the problem by setting tb_init_done=0 at exit time. But xentrace does not care the problem. Then error occured!(Cannot see the trace

Hi, I am trying to correlating performance issue in guest VM with the scheduling trace from Xentrace. User-mode application in guest VM periodically dump APIC ID and RDTSC into trace. I also start Xentrace in Dom0 during the same period. However, I notice that range of TSC values report both trace is completely disjointed. TSC values from Xentrace is always greater than what guest VM see, even

Dear r-helpers, Can anyone suggest why lm() doesn't complain here: summary(osss.lm1 <- lm(logOdds ~ c.setSize %in% task, data = osss)) whereas in package:nlme (and in package:lme4) osss.lmL <- lmList(logOdds ~ c.setSize %in% task | subj, data = osss) # Error in `contrasts<-`(`*tmp*`, value = "contr.treatment") : # contrasts can be applied only to factors with 2 or more

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

This patch (attached) fixes a small problem in xentrace_format. Signed-off-by: Yang Xiaowei <xiaowei.yang@intel.com> Zhou Ting <ting.g.zhou@intel.com> --- diff -r 0df3bf8aac1e tools/xentrace/formats --- a/tools/xentrace/formats Mon Jun 16 16:35:17 2008 +0100 +++ b/tools/xentrace/formats Thu Aug 21 17:36:03 2008 +0800 @@ -23,8 +23,8 @@ 0x00081001 CPU%(cpu)d

Once Xen calculates nr_nodes properly, all nr_cpu calculations based on nr_nodes * sockets_per_node * cores_per_socket * threads_per_core are broken. The easy fix is to replace those calculations with a new field, nr_cpus in physinfo which is calculated by num_online_cpus(). This patch does so and attempts to change all users over to nr_cpus field in physinfo. This patch touches

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