similar to: [PATCH 4/4] xentrace: Add a time parameter

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

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.

flight 8091 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/8091/ Regressions :-( Tests which did not succeed and are blocking: test-amd64-i386-rhel6hvm-intel 12 guest-localmigrate/x10 fail REGR. vs. 8071 Tests which did not succeed, but are not blocking, including regressions (tests previously passed) regarded as allowable: test-amd64-amd64-xl-pcipt-intel 9

This fixes a bug in changeset 22526:7a5ee3800417, where the wrong value is read when deciding whether to flush the VTd tables. The effect is minor: in situations where the p2m entry is changed but the mfn is the same, the VTd tables will be unnecessarily flushed. old_entry is left untouched in the second case, since having a present old_entry will cause the an unnecessary check to be taken at

Add a xen command-line parameter, sched_credit_tslice_ms, to set the timeslice of the credit1 scheduler. Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com> diff -r 4a4882df5649 -r 782284c5b1bc xen/common/sched_credit.c --- a/xen/common/sched_credit.c Wed Aug 31 15:23:49 2011 +0100 +++ b/xen/common/sched_credit.c Thu Sep 01 16:29:50 2011 +0100 @@ -41,15 +41,9 @@ */ #define

Hello, More information and a patch for the bug. -- Pasi ----- Forwarded message from George Dunlap <George.Dunlap at eu.citrix.com> ----- From: George Dunlap <George.Dunlap at eu.citrix.com> To: Jan Beulich <JBeulich at novell.com> Cc: Sander Eikelenboom <linux at eikelenboom.it>, Jeremy Fitzhardinge <jeremy at goop.org>, Yunhong Jiang <yunhong.jiang at

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

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

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

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

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

Only trace 64 bits when in long mode. This trace happens every VMEXIT, and contributes significantly to trace size. Adding this patch reduces trace size for a parallel xen build by 7%. Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com> (Again, hoping this will be counted as a bug-fix, since no new functionality is introduced.) _______________________________________________

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

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

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

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