From: Avi Kivity <avi@redhat.com>
To: Zachary Amsden <zamsden@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PATCH v4: kvm 1/4] Code motion. Separate timer intialization into an indepedent function.
Date: Wed, 30 Sep 2009 17:56:02 +0200 [thread overview]
Message-ID: <4AC37F92.2090502@redhat.com> (raw)
In-Reply-To: <4AC37E81.8080104@redhat.com>
On 09/30/2009 05:51 PM, Zachary Amsden wrote:
>> Is anything preventing us from unifying the constant_tsc and !same
>> paths? We could just do a quick check in the notifier, see the tsc
>> frequency hasn't changed, and return.
>
>
> Actually, yes. On constant_tsc processors, the processor frequency
> may still change, however the TSC frequency does not change with it.
>
> I actually have both of these kinds of processors (freq changes with
> constant TSC and freq changes with variable TSC) so I was able to test
> both of these cases.
If the API allows us to query the tsc frequency, it would simply return
the same values in all cases, which we'd ignore.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-09-30 15:56 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 4:04 Hotplug / TSC cleanup and fixing Zachary Amsden
2009-09-29 4:04 ` [PATCH v2: kvm 1/4] Code motion. Separate timer intialization into an indepedent function Zachary Amsden
2009-09-29 4:04 ` [PATCH v2: kvm 2/4] Kill the confusing tsc_ref_khz and ref_freq variables Zachary Amsden
2009-09-29 4:04 ` [PATCH v2: kvm 3/4] Fix printk name error in svm.c Zachary Amsden
2009-09-29 4:04 ` [PATCH v2: kvm 4/4] Fix hotplug of CPUs for KVM Zachary Amsden
2009-09-29 8:30 ` Avi Kivity
2009-09-29 15:51 ` Zachary Amsden
2009-09-29 21:38 ` [PATCH v4: kvm 1/4] Code motion. Separate timer intialization into an indepedent function Zachary Amsden
2009-09-29 21:38 ` [PATCH v4: kvm 2/4] Kill the confusing tsc_ref_khz and ref_freq variables Zachary Amsden
2009-09-29 21:38 ` [PATCH v4: kvm 3/4] Fix printk name error in svm.c Zachary Amsden
2009-09-29 21:38 ` [PATCH v4: kvm 4/4] Fix hotplug of CPUs for KVM Zachary Amsden
2009-09-30 13:35 ` Marcelo Tosatti
2009-10-08 23:18 ` [PATCH v4: kvm 2/4] Kill the confusing tsc_ref_khz and ref_freq variables Jan Kiszka
2009-10-09 20:27 ` Zachary Amsden
2009-10-09 20:36 ` Jan Kiszka
2009-10-09 20:36 ` Zachary Amsden
2009-10-09 20:47 ` Jan Kiszka
2009-10-09 20:47 ` Zachary Amsden
2009-10-09 21:05 ` Jan Kiszka
2009-10-10 2:26 ` [PATCH] cpufreq: Make cpufreq_get always defined Zachary Amsden
2009-10-10 2:26 ` [PATCH] KVM: Harden against cpufreq Zachary Amsden
2009-10-10 2:26 ` [PATCH] kvm-kmod cpufreq_get fix Zachary Amsden
2009-10-12 19:41 ` [PATCH] KVM: Harden against cpufreq Marcelo Tosatti
2009-09-30 8:45 ` [PATCH v4: kvm 1/4] Code motion. Separate timer intialization into an indepedent function Avi Kivity
2009-09-30 15:51 ` Zachary Amsden
2009-09-30 15:56 ` Avi Kivity [this message]
2009-09-30 16:06 ` Zachary Amsden
2009-09-30 16:11 ` Avi Kivity
2009-09-30 16:16 ` Zachary Amsden
2009-09-29 8:29 ` [PATCH v2: kvm 2/4] Kill the confusing tsc_ref_khz and ref_freq variables 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=4AC37F92.2090502@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).