public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ferenc Wagner <wferi@niif.hu>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: linux-kernel@vger.kernel.org, Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: doubled idle count
Date: Fri, 19 Sep 2008 15:20:28 +0200	[thread overview]
Message-ID: <87wsh8nug3.fsf@tac.ki.iif.hu> (raw)
In-Reply-To: <48D2AD5E.7040602@goop.org> (Jeremy Fitzhardinge's message of "Thu, 18 Sep 2008 12:34:54 -0700")

Jeremy Fitzhardinge <jeremy@goop.org> writes:

> Ferenc Wagner wrote:
>
>> After upgrading a Xen virtual machine to Debian's 2.6.26-4 kernel, I
>> noticed that the idle counter doubled its pace on one of the machines:
>> [...]
>> One out of three machines show this effect, with the exact same kernel
>> and Xen versions (3.2.0, dom0 is Debian's stock Etch 2.6.18 kernel).
>> They aren't hosted by the same machine, though: the misbehaving one is
>> on a different installation with very similar hardware (3 vs 2 GHz).
>> All the guest are paravirtual.
>
> So you're saying that they are identical Xen and guest kernel binaries,
> but one of three is showing doubled idle time?

Now I upgraded another domU, and that also shows this doubling effect,
so I've got two domUs (running on xen2-ha) misbehaving, and other two
(running on xen2) behaving correctly.  On the first:

wferi@xen2-ha:~$ sudo xm info
host                   : xen2-ha
release                : 2.6.18-6-xen-686
version                : #1 SMP Mon Aug 18 12:56:50 UTC 2008
machine                : i686
nr_cpus                : 4
nr_nodes               : 1
cores_per_socket       : 1
threads_per_core       : 2
cpu_mhz                : 3056
hw_caps                : bfebfbff:00000000:00000000:00000080:00004400
total_memory           : 3071
free_memory            : 991
node_to_cpu            : node0:0-3
xen_major              : 3
xen_minor              : 2
xen_extra              : -1
xen_caps               : xen-3.0-x86_32p 
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xf5800000
xen_changeset          : unavailable
cc_compiler            : gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)
cc_compile_by          : fs
cc_compile_domain      : debian.org
cc_compile_date        : Mon Mar 10 15:50:27 UTC 2008
xend_config_format     : 4

while on the other the differing lines are:

host                   : xen2
cpu_mhz                : 1993
total_memory           : 4991
free_memory            : 2464

Hope this adds some useful info.
-- 
Regards,
Feri.

  parent reply	other threads:[~2008-09-19 13:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-18 12:26 doubled idle count Ferenc Wagner
2008-09-18 19:34 ` Jeremy Fitzhardinge
2008-09-18 21:24   ` Ferenc Wagner
2008-09-19 13:20   ` Ferenc Wagner [this message]
2008-09-21 12:05   ` Ferenc Wagner
2008-09-21 12:27   ` Ferenc Wagner
2008-11-07 15:20   ` Ferenc Wagner

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=87wsh8nug3.fsf@tac.ki.iif.hu \
    --to=wferi@niif.hu \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox