public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: kvm-devel@lists.sourceforge.net,
	Glauber de Oliveira Costa <gcosta@redhat.com>
Subject: Re: [PATCH 0/4] paravirt clock patches
Date: Mon, 05 May 2008 09:47:59 +0200	[thread overview]
Message-ID: <481EBBAF.8090807@redhat.com> (raw)
In-Reply-To: <20080428192816.GA4596@dmt>

Marcelo Tosatti wrote:
> On Thu, Apr 24, 2008 at 10:37:04AM +0200, Gerd Hoffmann wrote:
>>   Hi folks,
>>
>> My first attempt to send out a patch series with git ...
>>
>> The patches fix the kvm paravirt clocksource code to be compatible with
>> xen and they also factor out some code which can be shared into a
>> separate source files used by both kvm and xen.
> 
> The issue with SMP guests is still present. Booting with "nohz=off" resolves it.
> 
> Same symptoms as before, apic_timer_fn for one of the vcpu's is ticking way slower
> than the remaining ones:
> 
> [root@localhost ~]# cat /proc/timer_stats  | grep apic
>   391,  4125 qemu-system-x86  apic_mmio_write (apic_timer_fn)
>  2103,  4126 qemu-system-x86  apic_mmio_write (apic_timer_fn)
>  1896,  4127 qemu-system-x86  apic_mmio_write (apic_timer_fn)
>  1857,  4128 qemu-system-x86  apic_mmio_write (apic_timer_fn)

What userspace version is this?  With iothread support?  Or older one
where the vcpu0 thread also handles all the I/O?  Is 4x neeed to
reproduce or do you see it with 2x too?  What host?

A quick test with xenner (which has a separate I/O thread) didn't show
anything unusual.  Going investigate ...

cheers,
  Gerd

-- 
http://kraxel.fedorapeople.org/xenner/

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

  reply	other threads:[~2008-05-05  7:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-24  8:37 [PATCH 0/4] paravirt clock patches Gerd Hoffmann
2008-04-24  8:37 ` [PATCH 1/4] Add helper functions for paravirtual clocksources Gerd Hoffmann
2008-04-24  8:37   ` [PATCH 2/4] Make xen use the generic paravirt clocksource code Gerd Hoffmann
2008-04-24  8:37     ` [PATCH 3/4] kvm/host: fix paravirt clocksource to be compatible with xen Gerd Hoffmann
2008-04-24  8:37       ` [PATCH 4/4] kvm/guest: fix paravirt clocksource to be compartible " Gerd Hoffmann
2008-04-24 13:16         ` Glauber Costa
2008-04-24 13:11   ` [PATCH 1/4] Add helper functions for paravirtual clocksources Glauber Costa
2008-04-28  8:54     ` Gerd Hoffmann
2008-04-27 12:58 ` [PATCH 0/4] paravirt clock patches Avi Kivity
2008-04-28 12:09   ` Gerd Hoffmann
2008-04-28 19:28 ` Marcelo Tosatti
2008-05-05  7:47   ` Gerd Hoffmann [this message]
2008-05-05 15:32     ` Marcelo Tosatti
2008-05-06 15:59       ` Gerd Hoffmann
2008-05-06 16:44         ` Gerd Hoffmann
2008-05-07 18:45   ` Gerd Hoffmann
2008-05-08 23:10     ` Marcelo Tosatti
2008-05-09 13:25       ` Glauber Costa
2008-05-13  6:53         ` Gerd Hoffmann

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=481EBBAF.8090807@redhat.com \
    --to=kraxel@redhat.com \
    --cc=gcosta@redhat.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=mtosatti@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox