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 2/2] xentrace: Add TRC_HVM_VCHIP
Date: Tue, 01 Apr 2014 13:42:24 -0400 [thread overview]
Message-ID: <533AFA80.1070000@terremark.com> (raw)
In-Reply-To: <533ABDBF.80603@eu.citrix.com>
On 04/01/14 09:23, George Dunlap wrote:
> On 03/28/2014 04:56 PM, Don Slutz wrote:
>> This add a set of trace events that track the setup of various
>> virtual chips related to timers in domU.
[snip]
>> @@ -255,6 +257,9 @@ static void hpet_set_timer(HPETState *h, unsigned int tn)
>> * being enabled (now).
>> */
>> oneshot = !timer_is_periodic(h, tn);
>> + TRACE_4D(TRC_HVM_VCHIP_HPET_START_TIMER, tn, irq,
>> + hpet_tick_to_ns(h, diff),
>
> This will only be 32 bits wide; is there ever any risk that this may exceed 4 seconds (4 billion nanoseconds)?
>
Yes. Will change to pass these all as 2 values. I see no reason to set TRC_64_FLAG since these will allways be 64 bit values.
Will also see about using TRC_PAR_LONG(). And switch to hex in formats.
>
>> diff --git a/xen/include/public/trace.h b/xen/include/public/trace.h
>> index e2f60a6..410f0fe 100644
>> --- a/xen/include/public/trace.h
>> +++ b/xen/include/public/trace.h
>> @@ -52,6 +52,7 @@
>> /* trace subclasses for SVM */
>> #define TRC_HVM_ENTRYEXIT 0x00081000 /* VMENTRY and #VMEXIT */
>> #define TRC_HVM_HANDLER 0x00082000 /* various HVM handlers */
>> +#define TRC_HVM_VCHIP 0x00084000 /* virtual chips */
>
> Maybe TRC_HVM_EMUL, for emulated devices?
>
That would be fine with me. Just going to wait to see if any other comments on the name.
-Don Slutz
> -George
>
next prev parent reply other threads:[~2014-04-01 17:42 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 [this message]
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
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=533AFA80.1070000@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).