similar to: [PATCH]fix xentrace

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

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

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

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

Attached is the second release of XenMon, which is a unique performance monitoring tool for Xen. Instead of using hypervisor calls to get domain information, we use the xentrace facility to provide fine-grained monitoring of various metrics (see README below). We have written up a small case study that demonstrates the usefulness of the tool and the metrics that it reports. This will be

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

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

I have a similar patch for this, which is generated in linux-2.6.16.33-xen/.config automatically. See attachment defbuild.patch. Pae_new_config is used to build x86_32 with PAE enabled. Ping >-----Original Message----- >From: xen-ia64-devel-bounces@lists.xensource.com [mailto:xen-ia64-devel-bounces@lists.xensource.com] On Behalf Of Atsushi >SAKAI >Sent: 2006年12月4日 12:22 >To:

This patch modifies the physinfo hcall to export NUMA CPU and Memory topology information. The new physinfo hcall is integrated into libxc and xend (xm info specifically). Included in this patch is a minor tweak to xm-test''s xm info testcase. The new fields in xm info are: nr_nodes : 4 mem_chunks : node0:0x0000000000000000-0x0000000190000000

Hi, It adds console_timestamps discription. Signed-off-by: Atsushi SAKAI <sakaia@jp.fujitsu.com> Anyway, Why Users'' manual version keeps Xen v3.0? Is there any reason? Thanks Atsushi SAKAI _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi, This patch intends to accurate vcpu weighting for CPU intensive job. The reason of this problem is that vcpu round-robin queue blocks large weight vcpus by small weight vcpus. For example, we assume following case on 2pcpu environment. (with 4domains (each domain has 2vcpus)) dom1 vcpu0,1 w128 credit 4 dom2 vcpu0,1 w128 credit 4 dom3 vcpu0,1 w256 credit 8 dom4 vcpu0,1 w512 credit 15

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

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

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

This is a patch which intends for default scheduler changed in user''s manual. (from sedf to credit) Signed-off-by: Atsushi SAKAI <sakaia@jp.fujitsu.com> Request: Credit scheduler has no description on glossary of terms (user''s manual appendix C:P67) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com