From: Avi Kivity <avi@redhat.com>
To: "David S. Ahern" <daahern@cisco.com>
Cc: BRUNO CESAR RIBAS <ribas@c3sl.ufpr.br>,
Zachary Amsden <zamsden@redhat.com>,
Brian Jackson <iggy@theiggy.com>, kvm-devel <kvm@vger.kernel.org>
Subject: Re: RHEL5.5, 32-bit VM repeatedly locks up due to kvmclock
Date: Sat, 24 Apr 2010 21:40:42 +0300 [thread overview]
Message-ID: <4BD33B2A.1070207@redhat.com> (raw)
In-Reply-To: <4BD22B67.6030800@cisco.com>
On 04/24/2010 02:21 AM, David S. Ahern wrote:
>
> On 04/23/2010 04:21 PM, BRUNO CESAR RIBAS wrote:
>
>> Could you try hpet? I had similar problem with multicore and multiCPU (per
>> mother board) [even with constant_tsc].
>>
>> Since I changed the guest to hpet i had no more problems.
>>
> It's stable in the sense of no lockups yet, but is a much slower time
> source from a gettimeofday perspective compared to tsc and jiffies
> (based on speed jiffies appears to be tsc-based).
>
Jiffies doesn't sample any hardware; instead, a timer interrupt causes a
counter to be incremented, and that counter is sampled. The downside is
that clock granularity is very low - you can't use it for accurate timing.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
prev parent reply other threads:[~2010-04-24 18:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 17:08 RHEL5.5, 32-bit VM repeatedly locks up due to kvmclock David S. Ahern
2010-04-23 20:39 ` Brian Jackson
2010-04-23 21:39 ` Zachary Amsden
2010-04-23 21:42 ` David S. Ahern
2010-04-23 22:21 ` BRUNO CESAR RIBAS
2010-04-23 23:21 ` David S. Ahern
2010-04-24 18:40 ` Avi Kivity [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=4BD33B2A.1070207@redhat.com \
--to=avi@redhat.com \
--cc=daahern@cisco.com \
--cc=iggy@theiggy.com \
--cc=kvm@vger.kernel.org \
--cc=ribas@c3sl.ufpr.br \
--cc=zamsden@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 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.