linux-kernel - Re: doubled idle count

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <48D2AD5E.7040602@goop.org>
Date:	Thu, 18 Sep 2008 12:34:54 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Ferenc Wagner <wferi@...f.hu>
CC:	linux-kernel@...r.kernel.org,
	Xen-devel <xen-devel@...ts.xensource.com>
Subject: Re: doubled idle count

Ferenc Wagner wrote:
> Hi,
>
> 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:
>
> service2:~# yes >/dev/null &
> [1] 32578
> service2:~# grep cpu0 /proc/stat; sleep 1; grep cpu0 /proc/stat
> cpu0 141208 9113 57273 13379659 61012 0 792 2350 0
> cpu0 141310 9113 57274 13379659 61012 0 792 2350 0
> service2:~# fg
> yes > /dev/null
> ^C
> service2:~# grep cpu0 /proc/stat; sleep 1; grep cpu0 /proc/stat
> cpu0 141952 9113 57277 13383481 61012 0 792 2350 0
> cpu0 141953 9113 57278 13383681 61012 0 792 2350 0
>   

Sorry, could you be clearer here?  What are we looking at?

> 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?

That seems unlikely.  The source of that time is from Xen itself, and I
think it should be hardware independent, though I guess its possible
there's something going on at in the Xen-level timekeeping.

That said, I think there's some chance that stolen time may get counted
as idle time.  Does the one machine with a different outcome have
something else running in another virtual machine (including dom0)?

    J

> service2:~# cat /proc/cpuinfo 
> processor	: 0
> vendor_id	: GenuineIntel
> cpu family	: 15
> model		: 2
> model name	: Intel(R) Xeon(TM) CPU 3.06GHz
> stepping	: 5
> cpu MHz		: 3056.482
> cache size	: 1024 KB
> physical id	: 0
> siblings	: 1
> core id		: 0
> cpu cores	: 1
> apicid		: 1
> initial apicid	: 1
> fdiv_bug	: no
> hlt_bug		: no
> f00f_bug	: no
> coma_bug	: no
> fpu		: yes
> fpu_exception	: yes
> cpuid level	: 2
> wp		: yes
> flags		: fpu de tsc msr pae cx8 cmov pat pse36 clflush dts mmx fxsr sse sse2 ss ht pbe up pebs bts cid xtpr
> bogomips	: 6128.11
> clflush size	: 64
> power management:
>
> I don't know what else would be useful, please ask.
>   

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/