From: Tomasz Chmielewski <mangoo-Nem3ZqsbT/g@public.gmane.org>
To: Anthony Liguori <anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: rtc: lost some interrupts at 1024Hz.
Date: Fri, 13 Apr 2007 17:13:57 +0200 [thread overview]
Message-ID: <461F9E35.5030901@wpkg.org> (raw)
In-Reply-To: <461F9D5F.1090009-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
Anthony Liguori schrieb:
> Tomasz Chmielewski wrote:
>> Whenever I start a guest, I get kernel log filled with "rtc: lost some
>> interrupts at 1024Hz".
>>
>
> Does rebooting the host machine with nolapic on the kernel command line
> help?
It turned out, this option needs to be enabled:
Processor type and features --->
[*] Provide RTC interrupt
(or CONFIG_HPET_EMULATE_RTC=y in .config).
With it enabled, I don't have these messages anymore, and performance is
much much better.
> What sort of system are you using?
# uname -a
Linux syn5 2.6.21-rc6 #3 SMP Fri Apr 13 16:37:31 CEST 2007 x86_64
Intel(R) Xeon(R) CPU 3050 @ 2.13GHz GNU/Linux
KVM-18.
--
Tomasz Chmielewski
http://wpkg.org
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
prev parent reply other threads:[~2007-04-13 15:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-13 12:01 rtc: lost some interrupts at 1024Hz Tomasz Chmielewski
[not found] ` <461F70FF.9010704-Nem3ZqsbT/g@public.gmane.org>
2007-04-13 15:10 ` Anthony Liguori
[not found] ` <461F9D5F.1090009-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-04-13 15:13 ` Tomasz Chmielewski [this message]
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=461F9E35.5030901@wpkg.org \
--to=mangoo-nem3zqsbt/g@public.gmane.org \
--cc=anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.