linux-kernel - Re: [PATCH 4/6] RTC: Ratelimit "lost interrupts" message

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Thu, 24 May 2007 14:15:12 -0700
From:	Roland Dreier <rdreier@...co.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Ben Collins <ben.collins@...ntu.com>, linux-kernel@...r.kernel.org,
	Zachary Amsden <zach@...are.com>
Subject: Re: [PATCH 4/6] RTC: Ratelimit "lost interrupts" message

 > > I got it a lot when using any sort of virtualization on my Core2Duo
 > > (kvm, vmware, qemu). Just a big spew. Honestly, I was getting this with
 > > 2.6.20, and haven't tested again with latest kernel.
 > 
 > OK, a bit of googling finds things like this:
 > http://chxo.com/be2/20060821_3333.html, so I assume that it's some sort of
 > generic problem with the hypervisor's emulation of the RTC.

Actually I saw this "lost interrupts" spew on the host (ie the
non-virtualized kernel) running just plain qemu (no kvm or anything
scary like that).  It seemed to be some long irqs-off latency in the
tun/tap or bridging code (it went away when I stopped using "-net tap"
on the qemu command line), but I never succeeded in getting Ingo's
latency tracer to be able to track it down.

 - R.
-
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/