search for: xentrace_formats

The xentrace_format script doesn''t work on x86/64. Python pads the input structure because the first field is 32 bits and the next is 64 bits, whereas x86-32 doesn''t pad. The quick fix is to read the cpu id separately as a 32bit value, then read the rest of the trace record. Here is a little patch that does that. Tested on x86/32 SMP and x86/64. Signed-off-by: Rob Gardner

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

Package: xen-utils-4.0 Version: 4.0.1-1 Severity: normal When I invoke me at dev:~# xentrace_format I get exec: 22: /usr/lib/xen-4.0/bin/xentrace_format: not found as result. The missing python script is referenced by the /usr/sbin/xentrace_format script from the xen-utils-common package. Using the python script from another (xen 4.0.0) distribution works fine. So I assume the file is

Hi! Attached patch adds missing entries in xentrace''s formats file to make it recognize all HVM traces. Signed-off-by: Christoph Egger <Christoph.Egger@amd.com> Still missing are entries for PV traces. -- AMD Saxony, Dresden, Germany Operating System Research Center Legal Information: AMD Saxony Limited Liability Company & Co. KG Sitz (Geschäftsanschrift): Wilschdorfer

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

Processing commands for control at bugs.debian.org: > close 609689 4.1.3~rc1+hg-20120614.a9c0a89c08f2-2 Bug #609689 [xen-utils-4.0] xen-utils-4.0: Missing xentrace_format python script in /usr/lib/xen-4.0/bin/ There is no source info for the package 'xen-utils-4.0' at version '4.1.3~rc1+hg-20120614.a9c0a89c08f2-2' with architecture '' Unable to make a source version for

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

Processing commands for control at bugs.debian.org: > #xen (4.4.0-4) UNRELEASED; urgency=medium > # > # * Make library packages multi-arch: same. (closes: #730417) > # * Use debhelper compat level 9. (closes: #692352) > # * Correct contents of /etc/xen/scripts/hotplugpath.sh (Closes: #706283) > # * Drop references cpuperf-xen and cpuperf-perfcntr. (Closes: #733847) > # *

Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.8 Date: Sat, 30 Aug 2014 13:34:04 +0200 Source: xen Binary: libxen-4.4 libxenstore3.0 libxen-dev xenstore-utils xen-utils-common xen-utils-4.4 xen-hypervisor-4.4-amd64 xen-system-amd64 xen-hypervisor-4.4-arm64 xen-system-arm64 xen-hypervisor-4.4-armhf xen-system-armhf Architecture: source all Version: 4.4.0-4 Distribution:

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

tags 407143 +patch thanks On Fri, 2013-08-16 at 14:42 +0100, Ian Campbell wrote: > tags 688308 +patch > thanks > > A lot of /docs/ is pretty low-level and not all that interesting to be > installed by the packages. However some of it is, and in particular some > is referenced from the manpages. I've cherry-picked the bits which I > think are most interesting in that

tags 688308 +patch thanks A lot of /docs/ is pretty low-level and not all that interesting to be installed by the packages. However some of it is, and in particular some is referenced from the manpages. I've cherry-picked the bits which I think are most interesting in that context. Patch below. 8<--------------- commit 7f8ac283e684b7c713d52ed845cab0704a97abab Author: Ian Campbell <ijc

Hi all I was reading through Xen 3 user manual and saw this tap:aio should be used instead of loopback... Then I came to do that, but I can get it working with replacing `file'' URI''s with `tap:aio''. My OS: Debian Lenny 2.6.26-2-xen-amd64 DomU Xen configuration file: kernel = ''/boot/vmlinuz-2.6.26-2-xen-amd64'' ramdisk =

Hi, Is there any documentation on enabling hypervisor support for both C and P-state control? On xen-unstable and linux-2.6.18-xen.hg, if I enable cpuidle=1 on the xen command line and then run xenpm, I will get output for C-states (shown below) but it complains that "Xen cpufreq is not enabled!" cpu id : 0 total C-states : 2 idle time(ms) : 73264 C0