All of lore.kernel.org
 help / color / mirror / Atom feed
From: Don Slutz <dslutz@verizon.com>
To: George Dunlap <george.dunlap@eu.citrix.com>,
	Don Slutz <dslutz@verizon.com>,
	xen-devel@lists.xen.org, Jan Beulich <jbeulich@suse.com>,
	Tim Deegan <tim@xen.org>
Cc: Keir Fraser <keir@xen.org>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH v2 0/2] xentrace: Add TRC_HVM_VCHIP (was xentrace: Add TRC_HW_VCHIP).
Date: Tue, 01 Apr 2014 11:18:18 -0400	[thread overview]
Message-ID: <533AD8BA.3050101@terremark.com> (raw)
In-Reply-To: <533AB9C8.309@eu.citrix.com>

On 04/01/14 09:06, George Dunlap wrote:
> On 03/28/2014 04:56 PM, Don Slutz wrote:
>> Changes v1 to v2:
>>    Tim Deegan:
>>      Switch from TRC_HW_VCHIP to TRC_HVM_VCHIP.
>>      Drop get_cycles()
>>      Fix coding style issues.
>>      Drop code that should not have been included.
>>      Use names not numbers.
>>
>> Split in 2 patches for simpler review.
>>
>> Here is a subset of sample output:
>
> Are you aware of xenalyze?  It's got a lot of advantages over xentrace_format; the most basic of which is that it traces vcpus as they run across pcpus.
>

I have noticed that it exists.  Not sure it would help with the issue I was looking into.

I have determined that I would see:

CPU5  841028423232 (+    3900)  hpet create [ tn = 0, irq = 0, delta = 68718266336, period = 1000000 ]

If I had been able to reproduce my issue.

Do I need to make a change there also?

    -Don Slutz

> hg clone http://xenbits.xenproject.org/ext/xenalyze
>
>  -George
>
>>
>> dcs-xen-54:~/xen>grep hpet /home/don/zz-xentrace-3.out
>> CPU5  841028423232 (+    3900)  hpet create [ tn = 0, irq = 0, delta = 848080, period = 1000000 ]
>> CPU1  843516134148 (+   20796)  hpet destroy [ tn = 0 ]
>> CPU7  846913412784 (+   26184)  hpet destroy [ tn = 0 ]
>> CPU7  846913416102 (+    1776)  hpet create [ tn = 0, irq = 0, delta = 4170764048, period = 0 ]
>> CPU4  851697560919 (+   11499)  hpet destroy [ tn = 1 ]
>> CPU4  851697562041 (+    1122)  hpet create [ tn = 1, irq = 8, delta = 15605920, period = 0 ]
>> CPU4  851765523993 (+   12567)  hpet destroy [ tn = 1 ]
>> CPU5  1139751965382 (+   18624)  hpet create [ tn = 1, irq = 8, delta = 15598912, period = 0 ]
>> CPU5  1139789579136 (+   23088)  hpet destroy [ tn = 1 ]
>> CPU5  1139789581410 (+    2274)  hpet create [ tn = 1, irq = 8, delta = 15550992, period = 0 ]
>> CPU5  1139827080720 (+   24174)  hpet destroy [ tn = 1 ]
>> CPU5  1139827082718 (+    1998)  hpet create [ tn = 1, irq = 8, delta = 15550912, period = 0 ]
>> CPU5  1139864572410 (+   21198)  hpet destroy [ tn = 1 ]
>> CPU5  1139864574390 (+    1980)  hpet create [ tn = 1, irq = 8, delta = 15554912, period = 0 ]
>> CPU5  1139902073244 (+   21180)  hpet destroy [ tn = 1 ]
>> CPU5  1139902075296 (+    2052)  hpet create [ tn = 1, irq = 8, delta = 15555056, period = 0 ]
>> CPU5  1139939593674 (+   29112)  hpet destroy [ tn = 1 ]
>> CPU5  1139939595870 (+    2196)  hpet create [ tn = 1, irq = 8, delta = 15546992, period = 0 ]
>> CPU5  1139977075716 (+   21048)  hpet destroy [ tn = 1 ]
>> CPU5  1139977077642 (+    1926)  hpet create [ tn = 1, irq = 8, delta = 15555104, period = 0 ]
>> CPU5  1140014582832 (+   23088)  hpet destroy [ tn = 1 ]
>> CPU5  1140014584950 (+    2118)  hpet create [ tn = 1, irq = 8, delta = 15552576, period = 0 ]
>> CPU5  1140038873628 (+   21150)  hpet destroy [ tn = 1 ]
>> CPU5  1140038875890 (+    2262)  hpet create [ tn = 1, irq = 8, delta = 21056672, period = 0 ]
>> CPU5  1140039140484 (+   18348)  hpet destroy [ tn = 1 ]
>> CPU6  1142224601952 (+   12486)  hpet destroy [ tn = 0 ]
>>
>>
>>
>> Don Slutz (2):
>>    xentrace: Add emacs local variables
>>    xentrace: Add TRC_HVM_VCHIP
>>
>>   tools/xentrace/formats     | 18 ++++++++++++++++++
>>   xen/arch/x86/hvm/hpet.c    | 14 ++++++++++++++
>>   xen/arch/x86/hvm/i8254.c   | 18 ++++++++++++++++++
>>   xen/arch/x86/hvm/rtc.c     | 18 ++++++++++++++++++
>>   xen/arch/x86/hvm/vlapic.c  | 25 +++++++++++++++++++++++++
>>   xen/arch/x86/hvm/vpic.c    | 20 ++++++++++++++++++++
>>   xen/include/public/trace.h | 20 ++++++++++++++++++++
>>   7 files changed, 133 insertions(+)
>>
>

  reply	other threads:[~2014-04-01 15:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-28 16:56 [PATCH v2 0/2] xentrace: Add TRC_HVM_VCHIP (was xentrace: Add TRC_HW_VCHIP) Don Slutz
2014-03-28 16:56 ` [PATCH v2 1/2] xentrace: Add emacs local variables Don Slutz
2014-04-01  9:16   ` George Dunlap
2014-04-01 21:42     ` Don Slutz
2014-03-28 16:56 ` [PATCH v2 2/2] xentrace: Add TRC_HVM_VCHIP Don Slutz
2014-04-01 13:23   ` George Dunlap
2014-04-01 17:42     ` Don Slutz
2014-04-03 10:36   ` Tim Deegan
2014-04-01 13:06 ` [PATCH v2 0/2] xentrace: Add TRC_HVM_VCHIP (was xentrace: Add TRC_HW_VCHIP) George Dunlap
2014-04-01 15:18   ` Don Slutz [this message]
2014-04-01 16:01     ` George Dunlap

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=533AD8BA.3050101@terremark.com \
    --to=dslutz@verizon.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=keir@xen.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.