qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luca <kronos.it@gmail.com>
To: malc <av1474@comtv.ru>
Cc: kvm-devel@lists.sf.net, qemu-devel@nongnu.org
Subject: Re: [kvm-devel] [Qemu-devel] Re: [PATCH 0/4] Rework alarm timer infrastrucure - take2
Date: Tue, 21 Aug 2007 00:49:44 +0200	[thread overview]
Message-ID: <68676e00708201549q3b3ea383r27a8b67a147c3953@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0708210140540.16421@linmac.oyster.ru>

On 8/20/07, malc <av1474@comtv.ru> wrote:
> On Mon, 20 Aug 2007, Luca Tettamanti wrote:
>
> > Il Sun, Aug 19, 2007 at 10:31:26PM +0300, Avi Kivity ha scritto:
> >> Luca wrote:
> >>> On 8/19/07, Luca Tettamanti <kronos.it@gmail.com> wrote:
> >>>
> >>>> +static uint64_t qemu_next_deadline(void) {
> >>>> +    uint64_t nearest_delta_us = ULLONG_MAX;
> >>>> +    uint64_t vmdelta_us;
> >>>>
> >>>
> >>> Hum, I introduced a bug here... those vars should be signed.
> >>>
> >>> On the overhead introduced: how do you measure it?
> >>>
> >>>
> >>
> >> Run a 100Hz guest, measure cpu usage using something accurate like
> >> cyclesoak, with and without dynticks, with and without kvm.
> >
> > Ok, here I've measured the CPU usage on the host when running an idle
> > guest.
> >
[...]
> The upshot is this - if you have used any standard utility (iostat,
> top - basically anything /proc/stat based) the accounting has a fair
> chance of being inaccurate. If cyclesoak is what you have used then
> the results should be better, but still i would be worried about
> them.

Yes, I've used cyclesoak.

Luca

  reply	other threads:[~2007-08-20 22:49 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-17 23:11 [Qemu-devel] [PATCH 0/4] Rework alarm timer infrastrucure - take 2 Luca Tettamanti
2007-08-17 23:11 ` [Qemu-devel] [PATCH 1/4] Rework alarm timer infrastrucure Luca Tettamanti
2007-08-17 23:11 ` [Qemu-devel] [PATCH 2/4] Add -clock option Luca Tettamanti
2007-08-17 23:11 ` [Qemu-devel] [PATCH 3/4] Add support for HPET periodic timer Luca Tettamanti
2007-08-21 19:24   ` Matthew Kent
2007-08-21 19:40     ` Luca
2007-08-21 20:15       ` Matthew Kent
2007-08-22  6:48         ` [kvm-devel] " Dan Kenigsberg
2007-08-22  7:03           ` Avi Kivity
2007-08-22 12:34             ` Andi Kleen
2007-08-22 21:11               ` Dan Kenigsberg
2007-08-22 22:09                 ` Andi Kleen
2007-08-23  7:02                   ` Dan Kenigsberg
2007-08-24 20:18                     ` Luca
2007-08-25  8:24                       ` Dan Kenigsberg
2007-09-03  8:40       ` GUERRAZ Francois
2007-08-17 23:11 ` [Qemu-devel] [PATCH 4/4] Add support for dynamic ticks Luca Tettamanti
2007-08-17 23:48 ` [Qemu-devel] [PATCH 0/4] Rework alarm timer infrastrucure - take 2 Christian MICHON
2007-08-18  0:10   ` [kvm-devel] " Luca
2007-08-18 15:17 ` [Qemu-devel] Re: [kvm-devel] " Anthony Liguori
2007-08-18 16:53   ` [Qemu-devel] RE: [kvm-devel] [PATCH 0/4] Rework alarm timer infrastrucure - take2 Dor Laor
2007-08-18 22:02     ` [Qemu-devel] " Luca Tettamanti
2007-08-18 23:58       ` Anthony Liguori
2007-08-19  7:36         ` [Qemu-devel] RE: [kvm-devel] [PATCH 0/4] Rework alarm timer infrastrucure -take2 Dor Laor
2007-08-19  8:24         ` [Qemu-devel] Re: [kvm-devel] [PATCH 0/4] Rework alarm timer infrastrucure - take2 Avi Kivity
2007-08-19 13:10           ` Jamie Lokier
2007-08-19 13:48             ` [kvm-devel] [Qemu-devel] " Avi Kivity
2007-08-19 13:57               ` Paul Brook
2007-08-19 14:07                 ` Avi Kivity
2007-08-19 14:27                   ` Dor Laor
2007-08-20  9:25                   ` Avi Kivity
2007-08-19 17:15                 ` Jamie Lokier
2007-08-19 19:29                   ` [kvm-devel] [Qemu-devel] Re: [PATCH 0/4] Rework alarmtimer " Dor Laor
2007-08-19 19:30                   ` [kvm-devel] [Qemu-devel] Re: [PATCH 0/4] Rework alarm timer " Avi Kivity
2007-08-19 16:52       ` [Qemu-devel] Re: [kvm-devel] " Luca
2007-08-19 19:31         ` Avi Kivity
2007-08-20 21:20           ` Luca Tettamanti
2007-08-20 21:55             ` malc
2007-08-20 22:49               ` Luca [this message]
2007-08-21 12:09             ` Avi Kivity
2007-08-21 19:38               ` Luca Tettamanti
2007-08-21 19:44                 ` malc
2007-08-22  5:02                 ` Avi Kivity
2007-08-22 16:12                   ` Luca Tettamanti
2007-08-22 16:21                     ` Avi Kivity
2007-08-22 16:38                       ` Luca
2007-08-22 16:45                         ` Avi Kivity
2007-08-22 17:23                           ` Luca
2007-08-22 17:39                             ` Luca
2007-08-22 19:21                             ` Luca
2007-08-22 21:35                               ` [Qemu-devel] " Dor Laor
2007-08-22 22:07                                 ` [Qemu-devel] " Luca
2007-08-22 20:42                         ` Dan Kenigsberg

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=68676e00708201549q3b3ea383r27a8b67a147c3953@mail.gmail.com \
    --to=kronos.it@gmail.com \
    --cc=av1474@comtv.ru \
    --cc=kvm-devel@lists.sf.net \
    --cc=qemu-devel@nongnu.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).