From: Avi Kivity <avi@qumranet.com>
To: Glauber de Oliveira Costa <glommer@gmail.com>
Cc: Avi Kivity <avi@argo.co.il>, Ingo Molnar <mingo@elte.hu>,
kvm-devel <kvm-devel@lists.sourceforge.net>,
linux-kernel <linux-kernel@vger.kernel.org>,
Chris Wright <chrisw@sous-sol.org>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [kvm-devel] Guest kernel hangs in smp kvm for older kernels prior to tsc sync cleanup
Date: Wed, 19 Dec 2007 17:41:17 +0200 [thread overview]
Message-ID: <47693B9D.7080809@qumranet.com> (raw)
In-Reply-To: <5d6222a80712190732h515a63e6y49c64c0f572f044@mail.gmail.com>
Glauber de Oliveira Costa wrote:
> Changes in rate does not sound good. It's possibly what's screwing up
> my paravirt clock implementation in smp.
>
You should renew the timebase on vcpu migration, and hook cpufreq so
that changes in frequency are reflected in the timebase.
> Since the host updates guest time prior to putting vcpu to run, two
> vcpus that start running at different times will have different system
> values.
>
> Now if the vcpu that started running later probes the time first,
> we'll se the time going backwards. A constant tsc rate is the only way
> around
> my limited mind sees around the problem (besides, obviously, _not_
> making the system time per-vcpu).
>
I tried disabling frequency scaling (rmmod acpi_cpufreq) but that didn't
help my present problems.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2007-12-19 15:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-18 17:20 Guest kernel hangs in smp kvm for older kernels prior to tsc sync cleanup Avi Kivity
[not found] ` <47680173.6060606-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-18 22:19 ` Ingo Molnar
[not found] ` <20071218221930.GA26109-X9Un+BFzKDI@public.gmane.org>
2007-12-19 6:33 ` Avi Kivity
[not found] ` <4768BB43.1000609-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-19 11:19 ` Avi Kivity
2007-12-19 11:39 ` [kvm-devel] " Avi Kivity
[not found] ` <47690304.1090903-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-19 14:06 ` Ingo Molnar
2007-12-19 14:27 ` [kvm-devel] " Avi Kivity
[not found] ` <47692A47.4040803-7k6+44Jx4zn6gbPvEgmw2w@public.gmane.org>
2007-12-19 15:32 ` Glauber de Oliveira Costa
2007-12-19 15:41 ` Avi Kivity [this message]
[not found] ` <47693B9D.7080809-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-20 10:34 ` Glauber de Oliveira Costa
[not found] ` <5d6222a80712190732h515a63e6y49c64c0f572f044-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-12-19 16:55 ` Amit Shah
[not found] ` <200712192225.53748.amit.shah-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-19 17:04 ` Guest kernel hangs in smp kvm for older kernelsprior " Dor Laor
[not found] ` <47694F35.6070401-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-19 17:09 ` Avi Kivity
[not found] ` <20071219140624.GF21282-X9Un+BFzKDI@public.gmane.org>
2007-12-19 14:53 ` Guest kernel hangs in smp kvm for older kernels prior " Avi Kivity
2007-12-19 15:09 ` [kvm-devel] " Ingo Molnar
[not found] ` <20071219150938.GA15267-X9Un+BFzKDI@public.gmane.org>
2007-12-19 15:21 ` Avi Kivity
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=47693B9D.7080809@qumranet.com \
--to=avi@qumranet.com \
--cc=avi@argo.co.il \
--cc=chrisw@sous-sol.org \
--cc=glommer@gmail.com \
--cc=kraxel@redhat.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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