All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Winchell <dwinchell@virtualiron.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: Dave Winchell <dwinchell@virtualiron.com>,
	"dan.magenheimer@oracle.com" <dan.magenheimer@oracle.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Ian Pratt <Ian.Pratt@eu.citrix.com>,
	"Tian, Kevin" <kevin.tian@intel.com>
Subject: Re: Re: Fix for get_s_time()
Date: Tue, 29 Apr 2008 10:21:54 -0400	[thread overview]
Message-ID: <48172F02.6000600@virtualiron.com> (raw)
In-Reply-To: <C43C8971.17F6A%keir.fraser@eu.citrix.com>

Yes. Its an AMD Warthog. I'll try some other platforms when I get a chance.

-Dave

Keir Fraser wrote:

>So does the below indicate that 92529 of your HPET accesses took between 0
>and 63 cycles? That seems rather short for an access off-chip and to the
>southbridge.
>
> -- Keir
>
>On 28/4/08 19:40, "Dave Winchell" <dwinchell@virtualiron.com> wrote:
>
>  
>
>>read_64_main_counter() On stime:
>>
>>(VMM)  cycles per bucket 64
>>(VMM)
>>(VMM)  0: 0 78795 148271 21173 15902 47704 89195 121962
>>(VMM)  8: 83632 51848 17531 12987 10976 8816 9120 8608
>>(VMM)  16: 5685 3972 3783 2518 1052 710 608 469
>>(VMM)  24: 277 159 83 46 34 23 19 16
>>(VMM)  32: 9 6 7 3 4 8 5 6
>>(VMM)  40: 9 7 14 13 17 25 22 29
>>(VMM)  48: 25 19 35 27 30 26 21 23
>>(VMM)  56: 17 24 12 27 22 18 10 22
>>(VMM)  64: 19 16 16 16 28 18 23 16
>>(VMM)  72: 22 22 12 14 21 19 17 19
>>(VMM)  80: 18 14 10 14 11 12 8 18
>>(VMM)  88: 16 10 17 14 10 8 11 11
>>(VMM)  96: 10 10 0 175
>>
>>read_64_main_counter() Going to the hardware:
>>
>>(VMM)  cycles per bucket 64
>>(VMM)
>>(VMM)  0: 92529 148423 27850 12532 28042 43336 60516 59011
>>(VMM)  8: 36895 14043 8162 6857 7794 7401 5099 2986
>>(VMM)  16: 1636 1066 796 592 459 409 314 248
>>(VMM)  24: 206 195 138 97 71 45 35 34
>>(VMM)  32: 33 36 40 40 25 26 25 26
>>(VMM)  40: 37 23 18 30 27 30 34 44
>>(VMM)  48: 38 19 25 23 23 25 21 27
>>(VMM)  56: 28 24 43 80 220 324 568 599
>>(VMM)  64: 610 565 611 699 690 846 874 788
>>(VMM)  72: 703 542 556 613 605 603 559 500
>>(VMM)  80: 485 493 512 578 561 594 575 614
>>(VMM)  88: 759 851 895 856 807 770 719 958
>>(VMM)  96: 1127 1263 0 18219
>>
>>    
>>
>
>
>  
>

  reply	other threads:[~2008-04-29 14:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <47FFC37A.4060402@virtualiron.com>
2008-04-11 21:20 ` System time monotonicity Keir Fraser
2008-04-11 21:41   ` Keir Fraser
2008-04-11 22:58     ` Dave Winchell
2008-04-12  7:09       ` Keir Fraser
2008-04-21 19:26         ` Dan Magenheimer
2008-04-21 19:31           ` Keir Fraser
2008-04-21 20:32             ` Fix for get_s_time() Dave Winchell
2008-04-21 22:55               ` Keir Fraser
2008-04-21 23:10                 ` Keir Fraser
2008-04-22 14:09                   ` Dave Winchell
2008-04-24 16:04                   ` Dave Winchell
2008-04-24 16:37                     ` Keir Fraser
2008-04-24 18:32                       ` Dave Winchell
2008-04-25 19:48                         ` Dave Winchell
2008-04-25 21:03                           ` Dan Magenheimer
2008-04-26  1:54                             ` Dave Winchell
2008-04-28 17:39                               ` Dan Magenheimer
2008-04-28 18:09                                 ` Dave Winchell
2008-04-28 18:40                                   ` Dave Winchell
2008-04-29  7:14                                     ` Keir Fraser
2008-04-29 14:21                                       ` Dave Winchell [this message]
2008-04-28 20:11                                   ` Dan Magenheimer
2008-04-28 21:29                                     ` Dave Winchell
2008-04-11 22:22   ` System time monotonicity Dan Magenheimer

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=48172F02.6000600@virtualiron.com \
    --to=dwinchell@virtualiron.com \
    --cc=Ian.Pratt@eu.citrix.com \
    --cc=dan.magenheimer@oracle.com \
    --cc=keir.fraser@eu.citrix.com \
    --cc=kevin.tian@intel.com \
    --cc=xen-devel@lists.xensource.com \
    /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.